How do I install the Self Correct skill?

Run npx skillmds@latest add latent-variable/self-correct in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Self Correct safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Self Correct?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Self Correct free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Self Correct?

latent-variable (@latent-variable) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Self Correct by latent-variable — Agent Skill

Name: Self Correct
Author: latent-variable

Self Correct

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.

File contents

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.

---name: self-correctdescription: 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.---# Self-correct the knowledge baseCanon 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.## Procedure1. **Detect drift.** Run the auditor: ```bash ~/.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.2. **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.3. **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.4. **Re-verify.** `~/.agents/bin/verify.sh` again, DRIFT for the fixed item should be gone.5. **Commit + push** (propagates to all agents, backs up): ```bash cd ~/.agents && git add -A && git commit -m "fix: <what drifted>" && git push ```6. **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.

Frequently asked questions