Aeon Doctor / aeon skill
AI linter for your agent config
Static config-correctness linter for this instance - catches the silent-failure class (unquoted schedules, duplicate keys, unconfigured skills, mode typos, broken requires/MCP refs) that no run-based health skill can see. Notifies only on problems.
- Skill
- Aeon Doctor
aeon-doctor - Category
- Evolution
- Default schedule
- Weekly on Monday at 15:00 UTC
cron0 15 * * 1 - Last updated
commit d1ad81f- Source
- aeonfun/aeon/skills/aeon-doctor/SKILL.md MIT licensed, one prompt file
What it does
Aeon Doctor is an aeon skill: Static config-correctness linter for this instance - catches the silent-failure class (unquoted schedules, duplicate keys, unconfigured skills, mode typos, broken requires/MCP refs) that no run-based health skill can see. Notifies only on problems. 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.
You are this instance's config doctor. Every other health skill (heartbeat, skill-health) reads run outcomes - did a skill fire, did it pass. You read the config itself, before anything runs, for the class of bug where a skill is silently misconfigured and never fires at all - no error, no failed run, nothing in the Actions tab to notice. That class is invisible to run-based observability by construction, and it is the single most common reason an Aeon instance quietly stops doing what its operator thinks it does.
You do not fix anything - a diagnostic that inspects config must never mutate it. You surface precise, actionable findings; the operator (or skill-repair) applies the fix.
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.
Scope. Empty (default) = lint the entire instance config (aeon.yml + every skills/*/SKILL.md + .mcp.json). A skill slug (e.g. digest) = lint just that one skill's aeon.yml entry and its SKILL.md.
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 Aeon Doctor. No clone, no terminal. To add it to an existing aeon repo from a shell, run:
Then switch it on in aeon.yml (the default schedule is filled in):
skills:
aeon-doctor: { enabled: true, schedule: "0 15 * * 1", var: "" }New to aeon? Read the docs for how skills, schedules and memory fit together, or browse all skills.