aeon-skill-repair
Skill17 starsChanged 5 months agoMITView on GitHub
Auto-diagnose and fix a failing or degraded installed skill. Reads the SKILL.md plus recent error output, classifies the failure (api-change / rate-limit / timeout / sandbox-limitation / prompt-bug / output-format / missing-secret / config), applies the smallest fix that addresses the root cause, and attaches a verification recipe. Minimum-edit principle, never auto-applies high-risk changes. Triggers: "fix this skill", "skill X is broken", "diagnose this failure", "the output of X looks wrong".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- BankrBot/openclaw-skillsword for word, first seen Oct 8, 2026
- BankrBot/skillsword for word, first seen Apr 28, 2026
Other versions2 projects use a version of this.
Word for word · 2
- BankrBot/openclaw-skills★ 1.2k100% same
- BankrBot/skills★ 1.2k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository84 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- .cursor/rules/codegraph.mdcCursor rule
- 0xworkSkill
- aeon-autoresearchSkill
- aeon-deal-flowSkill
- aeon-deep-researchSkill
- aeon-defi-monitorSkill
- aeon-defi-overviewSkill
- aeon-distribute-tokensSkill
- aeon-hacker-news-digestSkill
- aeon-huggingface-trendingSkill
- aeon-last30Skill
- aeon-monitor-kalshiSkill
- aeon-monitor-polymarketSkill
- aeon-monitor-runnersSkill
- aeon-narrative-trackerSkill
- aeon-on-chain-monitorSkill
- aeon-paper-pickSkill
- aeon-reg-monitorSkill
- aeon-rss-digestSkill
- aeon-skill-evalsSkill
- aeon-skill-security-scanSkill
- aeon-token-moversSkill
- aeon-token-pickSkill
- aeon-unlock-monitorSkill
- aeon-vuln-scannerSkill
- agenticbetsSkill
- agent-wormholeSkill
- alchemySkill
- bankr-shopifySkill
- bankrSkill
- token-scam-analysisSkill
- twitter-agentSkill
- baseSkill
- blueagent-x402Skill
- botchanSkill
- botcoin-minerSkill
- capacitrSkill
- cattownSkill
- checkrSkill
- clankerSkill
- codegridSkill
- darksol-random-oracleSkill
- endaomentSkill
- ens-primary-nameSkill
- erc-8004Skill
- gem-minerSkill
- get-api-docsSkill
- gitlawbSkill
- helixaSkill
- hydrexSkill
- litcoin-minerSkill
- megapotSkill
- moltycashSkill
- nexusSkill
- neynarSkill
- nookplotSkill
- onchainkitSkill
- opensea-apiSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 68
Never modify env-var configuration.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
aeon-skill-repair
Targeted repair for one failing skill. Build a diagnostic dossier, classify the failure, apply the matching playbook, attach a verification recipe.
Inputs
| Param | Description |
target | Skill name or SKILL.md path. Required. |
error_output | Recent failed output (paste from run log). Required if not auto-detectable. |
mode | repair (default) or dry-run (diagnose only). |
Diagnosis sources
- The skill file (frontmatter, declared sources, env-var references).
- Error output signature (HTTP codes, common API errors, rate-limit hits, refusal markers).
- Source liveness — WebFetch on referenced URLs to detect 404s, redirects, schema changes.
- Frontmatter integrity (valid YAML).
Failure categories and fix scope
| Category | Detection | Fix scope |
api-change | 404/410, schema mismatch | Update endpoints/payload/headers per live spec. Cite the spec URL. |
rate-limit | 429, "too many requests" | Add backoff or fallback endpoint. Never raise the limit. |
timeout | Killed mid-run, partial output | Stage the work, add early-return on partial success. |
sandbox-limitation | Auth-bearing curl fails | Convert to prefetch / postprocess pattern. |
prompt-bug | Hallucination, refusal, missing required section | Minimum-edit specificity insertion. < 30 lines diff. |
output-format | Output passes execution but fails downstream parser | Edit until next run satisfies the failing assertion. |
missing-secret | "API key missing", env var unset | No code change. Name the missing var for the operator. Exit REPAIR_DIAGNOSED_NO_FIX. |
config | Bad input config (watchlist, list file) | Fix obvious shape errors. Never invent entries. |
unknown | None of the above | Don't edit blindly. Append dossier to repair-notes, exit REPAIR_DIAGNOSED_NO_FIX. |
Risk classes
- LOW — fallback added, comment-only, < 30 lines. Auto-applied.
- MED — data source change, output format edit. Auto-applied with verification recipe.
- HIGH — touches behavior fundamentally, changes defaults. Operator review required, not auto-applied.
Verification recipe (every repair)
1. Re-run the skill: <one-line invocation>
2. Expected: <category-specific signal — "no rate-limit in trace" / "≥ 200 words" / "matches pattern X">
3. If still failing: <fallback path>Cooldown
24h cooldown per skill — prevents repair loops on fixes that didn't stick. State in local repair-history.json.
Rules
- One target per run. Never bundle unrelated repairs.
- Minimum-edit principle. Small diffs.
- Never modify env-var configuration. Missing secrets are flagged for the operator.
- Inside a git repo: branch + diff, never directly to main.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.