aeon

GitHub Filing Registry / aeon skill

Track every issue and PR filed across

Track every issue and PR filed across upstream repositories - status, evidence, next_action, and history. Replaces standalone Python scripts with a pure shell + gh CLI interface.

CATEGORY Dev & CodeRUNS On demand
Skill
GitHub Filing Registry github-filing-registry
Category
Dev & Code
Default schedule
On demand
Last updated
See the source
Source
aeonfun/aeon/skills/github-filing-registry/SKILL.md MIT licensed, one prompt file

What it does

GitHub Filing Registry is an aeon skill: Track every issue and PR filed across upstream repositories - status, evidence, next_action, and history. Replaces standalone Python scripts with a pure shell + gh CLI interface. 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.

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.

Optional. Accepts owner/repo#N for single-item ops, or a subcommand (add, status, triage, sync, log). Empty = run triage.

What it needs

No extra API keys or MCP servers. It runs on the model you connected to aeon (a Claude subscription token, an API key, or another login).

Install and run it

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

bin/add-skill aeonfun/aeon github-filing-registry

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

skills:
  github-filing-registry: { enabled: true, schedule: "workflow_dispatch", var: "" }

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



RUN NOW