What problem does it solve?
Skills in an Aeon instance can be silently misconfigured — unquoted cron schedules, duplicate YAML keys, mode typos, or broken requires entries — so they never fire at all, with no error and no failed run visible anywhere. Run-based health checks cannot see this class of bug because nothing ever executes.
Core Features & Use Cases
- Static config linting: Runs 12 read-only checks over
aeon.yml, every skills/*/SKILL.md, and .mcp.json using grep, awk, and local validation scripts.
- Severity-ranked findings: Classifies issues as critical (an enabled skill that will never fire or runs with wrong privilege) or warn (latent traps), each with the exact file, line, and a copy-pasteable fix.
- Scoped or fleet-wide audits: Lint the whole instance by default, or pass a skill slug to inspect just one skill's config entry and SKILL.md.
- Use Case: An operator notices a daily digest skill has not posted in a week. Running this linter reveals the schedule value in
aeon.yml is unquoted, so the scheduler regex never matches it — a one-character fix.
Quick Start
Ask the agent to run aeon-doctor to lint the entire instance configuration and report any silent misconfigurations with their exact fixes.