What problem does it solve?
Publishing one of your own skills so other Aeon agents can install it requires several manual steps: creating a standalone public repo with a skills-pack.json manifest, validating it, and opening a registry PR that updates both the README Community Packs table and catalog/skill-packs.json. This Skill automates that entire publishing pipeline.
Core Features & Use Cases
- Pack Repo Creation: Copies the full skill directory into a staged repo with a skills-pack.json manifest, README, and MIT LICENSE, then pushes it as a public GitHub repo via gh.
- Registry PR Submission: Forks aeonfun/aeon, appends a catalog entry and a README table row, bumps the community pack counter, and opens a PR against the canonical registry.
- Fail-Closed Validation: Runs validate-pack.sh and validate-skill-packs.mjs before any outward write, with a --dry-run mode that builds and validates locally without touching GitHub.
- Use Case: You built a token-movers skill and want every other Aeon agent to install it with bin/install-skill-pack — run pack-submit with the slug to publish the pack and file the registry PR in one pass.
Quick Start
Run pack-submit with the slug token-movers to package that skill into a public community pack repo and open the registry PR.