chore
Skill4 starsChanged 25 days agoMITView on GitHub
Grant Claude a one-off pass to make a small change without a decision (typo, rename, dependency bump). Ends when Claude finishes its reply.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- arleypadua/PKHeX.Everywheretheir own version, first seen Nov 8, 2026
- callmeradical/skillstheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- arleypadua/PKHeX.Everywhere★ 304same name
- callmeradical/skills★ 0same name
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.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Only the user can start this, by running the command.
- Distinctive: line 16
If the user didn't say what the chore is, ask in one line and wait.
- Very specific: line 17
If the change involves a design choice (new storage, a new dependency that shapes the app, changing how parts talk to each other), say so …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Reazon chore pass
Only the user can start this, by running the command. Never run it on your own initiative, and never suggest a chore for something that involves a design choice.
The helper is node "${CLAUDE_PLUGIN_ROOT}/bin/reazon.mjs" <command> --cwd "<absolute project folder>",
written below as reazon <command>. Quote paths. It prints JSON; on "ok": false,
explain the error and stop. Don't edit Reazon files by hand as a fallback.
- If the user didn't say what the chore is, ask in one line and wait.
- If the change involves a design choice (new storage, a new dependency that
shapes the app, changing how parts talk to each other), say so in one line
and suggest
/reazon:decideinstead. Grant the pass only if they still want it. - Run
reazon chore --reason "<what the chore is, in a few words>". - Make only that change in this reply. The pass ends automatically when your reply ends.
- Finish with a two-line summary: what changed, and that the pass has ended.
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.

