pack-submit

Packages an existing skill as a public GitHub community pack and submits a registry PR.

714|255|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill pack-submit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pack-submit
Source: https://github.com/aaronjmars/aeon/tree/main/skills/pack-submit
Command: npx skills add https://github.com/aaronjmars/aeon --skill pack-submit

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about pack-submit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish my skill as an Aeon community pack?

Run pack-submit with the skill's slug, for example token-movers. It copies the skill directory into a staged repo with a skills-pack.json manifest, README, and MIT LICENSE, pushes it as a public GitHub repo, and opens a registry PR against aeonfun/aeon.

How do I test a community pack without pushing to GitHub?

Pass the --dry-run flag, for example token-movers --dry-run. The pack is built and validated locally with validate-pack.sh, the manifest fields are reported, and nothing is written to GitHub.

Can I skip the registry PR when publishing a pack?

Yes, pass --no-register to create and push the pack repo without opening the PR against aeonfun/aeon. You can list it manually later using the publishing checklist in docs/community-skill-packs.md.

Why does the registry PR fail CI after submitting a pack?

The CI gate runs validate-skill-packs.mjs, which requires the README table row and the catalog/skill-packs.json entry to match, including skill counts and the community pack counter. The row must sit inside the table's contiguous block, not after the blank line that ends it.

What GitHub permissions does pack-submit need?

It needs a gh authentication token that can create public repos and open cross-repo PRs, typically via GH_GLOBAL. The ambient GITHUB_TOKEN in Actions cannot create repos or cross-repo PRs and fails with PACK_SUBMIT_REPO_FAILED.

Can pack-submit register a pack as trusted?

No. Packs are always registered with trust_level community. Trusted status requires the repo to be listed in skills/security/trusted-sources.txt, and the validator rejects a self-declared trusted entry.