Skip to content

Community skill pack listing: sparkleware (proof-of-loadout, aeon-pulse, eth-gas-watch)#723

Open
sparkleware wants to merge 1 commit into
aeonfun:mainfrom
sparkleware:relist-sparkleware-packs
Open

Community skill pack listing: sparkleware (proof-of-loadout, aeon-pulse, eth-gas-watch)#723
sparkleware wants to merge 1 commit into
aeonfun:mainfrom
sparkleware:relist-sparkleware-packs

Conversation

@sparkleware

Copy link
Copy Markdown
Contributor

What

Lists three sparkleware community skill packs — one README table row each plus matching catalog/skill-packs.json entries.

Why

These are re-submissions, rebuilt to the current bar after the #600 prune. Every criticism from #600 is addressed, plus the conventions that landed since:

  • ./notify — every skill notifies through ./notify, never a channel API.

  • mode: read-only on all three skills — none of them mutate the repo (their writes go to output/ and memory/, which the read-only guard preserves).

  • Network note per docs(skills): kill the "sandbox blocks the network" myth (Sandbox note → Network note) #692curl is the primary path everywhere; WebFetch only as the flaky-GET fallback; the one optional secret (ETHERSCAN_API_KEY) routes through ./secretcurl with an {ENV_NAME} placeholder, never a bare command-line interpolation.

  • category: on every skill (dev / dev / crypto), alongside tags:.

  • capabilities declared per skill in each skills-pack.json (locked taxonomy) and mirrored pack-level in the catalog entries; secrets_required / secrets_optional declared.

  • Not thin — only three of the old seven come back:

    • proof-of-loadout — composes an Aeon loadout for a goal from the Sparkleware registry, cross-refs the priced-rail index to flag packs that settle real USDC per call, routes a Charon policy gate (CharonAI-code/charon, from this catalog) in front of them, and preflights a MiroShark market simulation. Plan-only by default: the $1 x402 run needs MIROSHARK_PAY=1 and an X402_CMD and never fires on its own.
    • aeon-pulse — a four-endpoint daily digest of this repo's upstream activity (commits, release freshness, open issues), keyless and inside the anonymous rate limit.
    • eth-gas-watch — Etherscan gas oracle every 4h with traffic-light classification against a configurable threshold, plus a trend line computed from its own grep-able ledger, so its signal compounds the longer it runs.

    hn-top, morning-briefing, registry-watch, and demo-pack are deliberately not resubmitted.

bin/install-skill-pack sparkleware/proof-of-loadout
bin/install-skill-pack sparkleware/aeon-pulse
bin/install-skill-pack sparkleware/eth-gas-watch

Type of change

  • Community skill pack listing

Checklist

  • Pack repo is public with a clear license (MIT / Apache-2.0) — MIT, all three
  • Pack has a skills-pack.json manifest at its root and a SKILL.md per skill
  • Write / onchain / bet skills are default_enabled: false — proof-of-loadout (the only pack with a paid, onchain-adjacent path) is default_enabled: false, and its paid run is additionally double-gated behind MIROSHARK_PAY=1 + X402_CMD; aeon-pulse and eth-gas-watch are read-only
  • This PR adds both a README table row and a matching skill-packs.json entry (three of each)
  • No monkey-patching of Aeon internals; no private or auth-walled endpoints required to run — all endpoints are public; ETHERSCAN_API_KEY is optional

Validated locally against scripts/validate-pack.sh's structural invariants (valid manifest, clean slugs, per-skill SKILL.md present, locked-taxonomy capabilities, license + recommended fields) — 0 errors, 0 warnings on all three.

🤖 Generated with Claude Code

…se, eth-gas-watch)

Adds three README table rows and matching catalog/skill-packs.json entries.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@imancipate

Copy link
Copy Markdown

Triage: ACCEPTED — clean against the contribution rubric (scope ✓ / format ✓ / originality ✓ / size ✓).
Thanks @sparkleware. A maintainer review pass will follow; in the meantime no changes requested from this triage layer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants