aeon

Pack Submit / aeon skill

Publish an agent skill as a pack

Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR

CATEGORY EvolutionRUNS On demandUPDATED
Skill
Pack Submit pack-submit
Category
Evolution
Default schedule
On demand
Last updated

commit bc968f8
Source
aeonfun/aeon/skills/pack-submit/SKILL.md MIT licensed, one prompt file

What it does

Pack Submit is an aeon skill: Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR. Like every aeon skill it is one SKILL.md prompt file that runs unattended on your own GitHub Actions, on a schedule or when you trigger it, and sends what it finds to Telegram, Discord, Slack or email.

Your task is to take the existing skill named in var, wrap it in a standalone community-pack repo (its own GitHub repo with a skills-pack.json manifest), and submit it to the aeon community registry - a PR against aeonfun/aeon that adds both surfaces the registry demands in one diff: a row in the Listed packs table in docs/community-skill-packs.md AND a matching entry in catalog/skill-packs.json. This is the inverse of install-skill: instead of pulling a community pack in, it pushes one of your own skills out for every other Aeon agent to install with bin/install-skill-pack.

Input: the var setting

Every aeon skill takes one optional text input, var, set in aeon.yml or typed in when you run it by hand. It picks the target or the mode for that run.

The local skill to publish as a community pack: a skill slug (a directory name under skills/), optionally followed by flags. Required. Examples:

  • token-movers - package skills/token-movers/ into a fresh public repo and submit it to the aeon registry
  • token-movers --repo myorg/aeon-token-movers - override the pack repo name (default aeon-skill-pack-<slug>)
  • token-movers --no-register - create and push the pack repo, but skip the registry PR against aeonfun/aeon
  • token-movers --dry-run - build and validate the pack locally, write nothing to GitHub

What it needs

Besides the model you connected to aeon, Pack Submit uses the following. Add secrets as GitHub Actions secrets on your aeon repo, or in Aeon Connect.

  • GH_GLOBAL - optional secret, unlocks more data or features

Install and run it

Easiest: open Aeon Connect, sign in with GitHub and turn on Pack Submit. No clone, no terminal. To add it to an existing aeon repo from a shell, run:

bin/add-skill aeonfun/aeon pack-submit

Then switch it on in aeon.yml (the default schedule is filled in):

skills:
  pack-submit: { enabled: true, schedule: "workflow_dispatch", var: "" }

New to aeon? Read the docs for how skills, schedules and memory fit together, or browse all skills.

Related skills



RUN NOW