audit-plugin
Skill36 starsChanged 4 months agoMITView on GitHub
Audit Whetstone skills, agents, and commands when asked for a plugin quality or consistency audit.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- analyze-misfiresSkill
- announceSkill
- diagnose-negativesSkill
- eval-skillsSkill
- evolve-skillSkill
- prune-sync-logSkill
- releaseSkill
- skilloptSkill
- sync-from-reposSkill
- triage-prsSkill
- write-skillSkill
- skill-distillerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Read the Codex adaptation, then read the complete maintained workflow before acting.
- Very specific: line 10
Use the text following $audit-plugin as the workflow's $ARGUMENTS.
≈ “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
audit-plugin
Read the Codex adaptation, then read the complete maintained workflow before acting. Apply that workflow to the current request with its scope and approval boundaries intact.
Use the text following $audit-plugin as the workflow's $ARGUMENTS. When selected from a natural-language request, derive arguments only from the user's stated scope; apply the workflow's missing-argument behavior for anything unspecified.
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.

