enhance
Skill1 starsChanged 8 days agoMITView on GitHub
Run the AIPG enhance workflow, which audits a working system read-only through lenses and returns verified proposals scored by impact for the user to triage. Nothing is applied. Use only when the user explicitly asks for the AIPG enhance workflow.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- thunkaboutit/koleslaw-claude-codetheir own version, first seen Oct 20, 2026
- Marvellbrazil/my-agentic-skillstheir own version, first seen Oct 17, 2026
- VoTruongDanh/Skills-Agenttheir own version, first seen Oct 13, 2026
- jatinmayekar/claude-code-enhancetheir own version, first seen Mar 22, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- Marvellbrazil/my-agentic-skills★ 4same name
- VoTruongDanh/Skills-Agent★ 4same name
- jatinmayekar/claude-code-enhance★ 2same name
- thunkaboutit/koleslaw-claude-code★ 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.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- tools/CLAUDE.mdCLAUDE.md
- brainstormSkill
- debugSkill
- decideSkill
- developSkill
- docsSkill
- investigateSkill
- refineSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
When plugin-access.mjs exits 1, show the user its message, which names the cause, and run it again once the cause is fixed.
- Very specific: line 17
Read ${CLAUDE_PLUGIN_ROOT}/workflows/audit/CLAUDE.md and follow it exactly, through its scope section and its enhancements kind section.
- Distinctive: line 20
Use these paths wherever the guide says "this checkout" or "the tool's own directory":
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
The user wants to run the enhance dynamic workflow on the system below. It is the audit workflow's enhancements kind.
First run node "${CLAUDE_PLUGIN_ROOT}/tools/plugin-access.mjs" check. The Workflow tool launches only
engines the session can read. On missing, unless the working directory is ${CLAUDE_PLUGIN_ROOT} or a
folder above it, ask the user once whether to add the printed Read rule to their user settings. On yes,
run the command again with grant (settings reload live, no restart). On no, the user can run
/add-dir ${CLAUDE_PLUGIN_ROOT} for this session only.
When plugin-access.mjs exits 1, show the user its message, which names the cause, and run it again
once the cause is fixed.
Read ${CLAUDE_PLUGIN_ROOT}/workflows/audit/CLAUDE.md and follow it exactly, through its scope section
and its enhancements kind section.
Work the checklist's enhancements lists top to bottom.
Use these paths wherever the guide says "this checkout" or "the tool's own directory":
- Engine
scriptPath:${CLAUDE_PLUGIN_ROOT}/workflows/audit/audit.mjs, launched withkind: enhancements rootarg:${CLAUDE_PLUGIN_DATA}. Runs land in itsruns/<runId>/. Never the plugin install dir, which is version-swapped on update.
$ARGUMENTS
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.