Self correct

Skill latent-variable/agentscope/skills/self-correct

One user-scope brain every agent CLI reads: Claude Code, Codex, Antigravity/Gemini, Pi. Clone to ~/.agents, let your agent onboard you.

Install

npx -y skills add latent-variable/agentscope --skill self-correct

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Audit and repair the shared agent knowledge base (~/.agents) when it drifts from reality: removed/renamed dirs or repos, changed paths/flags/commands, superseded facts. Keeps instructions, memory, and skills true for every agent on the machine. Use on demand, on a schedule, or whenever you notice canon is stale mid-task.

SKILL.md

2.5 KB, as published. Nobody here has run it

Self-correct the knowledge base

Canon at ~/.agents/ is read by every agent (Claude, Codex, Gemini, Pi). One stale fact misleads all of them. Fix the source, don't patch around it.

When to run

Reactively (default): the moment you discover, during any task, that a canon fact is wrong, a path moved, a repo was deleted, a tool was renamed, a flag changed. Fix it then.
Proactively: on demand or scheduled.

Procedure

Detect drift. Run the auditor:
```
~/.agents/bin/verify.sh
```
It checks: symlink integrity (for installed tools), every filesystem path referenced in canon (AGENTS.md, memory/*.md, skills/**/SKILL.md), any GitHub repo referenced under your handle, and git sync state. It prints DRIFT: lines for anything broken.
Verify before editing. Confirm each DRIFT is real (the dir/repo truly moved or is gone), not a transient (unmounted volume, network blip, a <placeholder> or {{template}}). Never "correct" something you haven't confirmed changed.
Repair the source. Edit the stale file to match reality:
- Renamed dir/repo → update the name everywhere it appears (grep first: grep -rn 'OLD_NAME' ~/.agents).
- Removed thing → delete the line/file; drop its pointer in memory/MEMORY.md.
- Changed flag/command/path → update the exact string.
- Superseded fact → replace; keep one source of truth, no stale duplicate.
Re-verify. ~/.agents/bin/verify.sh again, DRIFT for the fixed item should be gone.

Commit + push (propagates to all agents, backs up):

cd ~/.agents && git add -A && git commit -m "fix: <what drifted>" && git push

Report one line: what you corrected and why.

Guardrails

Minimal edits. Correct the fact; don't rewrite the file.
Recoverable deletes only (trash, never rm -rf) per global rules.
Don't auto-correct subjective preferences or anything ambiguous, surface those to the user instead.
If a referenced GitHub repo 404s, confirm it isn't just private/renamed (gh repo view) before deleting the reference.