correct
Find the mistakes agents keep repeating in this repo and make each one impossible.
Skill by olibyte
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/olibyte-correct
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: testing, writing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions: not checked yet.
What's inside
- Skill name
correct- Description
- Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.
- License
- MIT
- Instructions
- 30 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
Codex `$correct`. Claude Code, Cursor, and Antigravity `/correct`. # Correct The operator keeps correcting agents in this repo for the same mistakes. Change the repo so the next agent can't make them. Assume every contributor is an agent that sees only the files it opened, copies the nearest example, and takes the shortest path that compiles. Design the repo so a change that looks right from one file is right for the whole repo. ## Find the mistake classes First, read recent commits, reverts, review comments, the agent instruction file (`AGENTS.md`), and comments that explain workarounds. Group the mistakes into classes. A class counts once it has happened twice. ## Fix each class at the highest level that works 1. **Eliminate it with architecture.** Give each piece of state one owner and each task one supported way. Hide internals so the wrong import fails. Replace hand-synced lists with one source of truth. Delete old ways and dead code an agent would copy. 2. **Enforce it with types so the bad state can't be written.** If bad code still compiles, add a lint or CI check whose error names the file, type, or function to use instead. If the pattern is already common, fail only when a change adds more. 3. **Test the behavior.** Fix or delete any test that would still pass if every function it calls returned nothing. 4. **Write docs or agent rules last, only for judgment calls.** Nothing fails when an agent skips them. ## Fix and prove Then fix the most frequent classes now, one commit each. Prove each new check fails on a real past mistake. Run the same command locally and in CI. Exceptions go on the offending line with a reason, an expiry date, and a human's approval. ## Keep the rule table Last, keep a table in the agent instruction file that pairs each rule with what enforces it. When the operator corrects you, fix the mistake and add the rule. If the rule was already there and nothing enforces it, that's a repeat, so fix it at the highest level in the same change. Drop a rule once its mistake can't happen. **Reply:** each class with its evidence, the level you picked, and why a higher level didn't work.
From olibyte/agent-toolkit, MIT.
More from olibyte/agent-toolkit
- 0.603score
principles
olibyte
Apply named engineering principles such as laziness, prove-it-works, and model-the-domain.
SkillAFreshness: A★ 2Claude Code +9 - 0.596score
poteto-help
olibyte
Guides users through this catalog, /poteto-mode, and picking the skill, playbook, or principle for a task.
SkillAFreshness: A★ 2Claude Code +9 - 0.575score
poteto-mode
olibyte
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work.
SkillAFreshness: A★ 2Claude Code +9 - 0.575score
architect
olibyte
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
SkillAFreshness: A★ 2Claude Code +9 - 0.575score
how
olibyte
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which…
SkillAFreshness: A★ 2Claude Code +9 - 0.575score
interrogate
olibyte
Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart".
SkillAFreshness: A★ 2Claude Code +9 - 0.573score
benchmark-checklist
olibyte
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it.
SkillAFreshness: A★ 2Claude Code +9 - 0.570score
automate-me
olibyte
Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how…
SkillAFreshness: A★ 2Claude Code +9 - 0.570score
arena
olibyte
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it.
SkillAFreshness: A★ 2Claude Code +9 - 0.557score
handoff
olibyte
Reconstructs or writes a coding-agent handoff from git and `.agents/handoff.md`.
SkillBFreshness: B★ 2Claude Code +9 - 0.534score
create-verification-skill
olibyte
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform.
SkillBFreshness: B★ 2Claude Code +9 - 0.531score
no-comments
olibyte
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
SkillBFreshness: B★ 2Claude Code +9
Signals
- Stars
- 2
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Oct 11, 2026 (18 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/olibyte/agent-toolkit
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from olibyte
- 0.603score
principles
olibyte
Apply named engineering principles such as laziness, prove-it-works, and model-the-domain.
SkillAFreshness: A★ 2Claude Code +9 - 0.596score
poteto-help
olibyte
Guides users through this catalog, /poteto-mode, and picking the skill, playbook, or principle for a task.
SkillAFreshness: A★ 2Claude Code +9 - 0.575score
interrogate
olibyte
Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart".
SkillAFreshness: A★ 2Claude Code +9 - 0.575score
architect
olibyte
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
SkillAFreshness: A★ 2Claude Code +9 - 0.575score
how
olibyte
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which…
SkillAFreshness: A★ 2Claude Code +9 - 0.575score
poteto-mode
olibyte
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work.
SkillAFreshness: A★ 2Claude Code +9
Cite this page
correct skill. Agent Mart. https://agentmart.dev/skills/olibyte-correct (last updated 2026-10-24)