skills
CLAUDE.md1 starsChanged 3 days agoMITView on GitHub
Skills of the user for Claude Code (skills/<category>/<skill>/SKILL.md), the routers (skills/routers/), the tools built by setup.sh (tools/<tool>/tool.txt, ex: tools/claude-cluster) and the claude.ai packaging (claude-ai/). The global context (~/.claude/CLAUDE.md, RTK.md, hooks) lives in context/ (./setup.sh context ...). Reports of audits on this repository go in audit/ at the root; repository scripts (README tables, checks) in scripts/.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- TsukiNi22/ai-utilsword for word, first seen Oct 9, 2026
Other versions1 project uses a version of this.
Word for word · 1
- TsukiNi22/ai-utils★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository70 other files it gives its agents.
- ask-at-endSkill
- clarifySkill
- continue-workSkill
- exportSkill
- full-permissionSkill
- ideationSkill
- interactive-questionsSkill
- onboardSkill
- pauseSkill
- presentationSkill
- rtkSkill
- setup-contextSkill
- write-like-meSkill
- audit-bugsSkill
- audit-depsSkill
- audit-qualitySkill
- audit-securitySkill
- benchmarkSkill
- cmake-styleSkill
- cpp-classSkill
- cpp-commentsSkill
- cpp-projectSkill
- cpp-styleSkill
- better-explain-docSkill
- better-html-docSkill
- better-html-styleSkill
- better-protocol-docSkill
- docs-updateSkill
- explain-docSkill
- html-docSkill
- html-styleSkill
- protocol-docSkill
- readme-styleSkill
- reportSkill
- wiki-styleSkill
- ci-cdSkill
- git-commitSkill
- git-conventionsSkill
- pre-commitSkill
- legal-checkSkill
- legal-setupSkill
- licenseSkill
- libutils-exceptionSkill
- libutils-installSkill
- libutils-setupSkill
- libutilsSkill
- python-classSkill
- python-commentsSkill
- python-projectSkill
- python-styleSkill
- auditSkill
- cppSkill
- devSkill
- docSkill
- gitSkill
- legalSkill
- pythonSkill
- setup-projectSkill
- styleSkill
- setup-studioSkill
- The first 60 shown.
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 9
Check / fix the style with xstyle, always with --rtk (compact output made for the assistant, ~5x fewer tokens): xstyle --rtk <paths>, …
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md 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
ai-utils repository
Skills of the user for Claude Code (skills/<category>/<skill>/SKILL.md), the routers (skills/routers/), the tools
built by setup.sh (tools/<tool>/tool.txt, ex: tools/claude-cluster) and the claude.ai packaging (claude-ai/).
The global context (~/.claude/CLAUDE.md, RTK.md, hooks) lives in context/ (./setup.sh context ...).
Reports of audits on this repository go in audit/ at the root; repository scripts (README tables, checks) in scripts/.
Checking with xstyle
- Check / fix the style with
xstyle, always with--rtk(compact output made for the assistant, ~5x fewer tokens):xstyle --rtk <paths>,xstyle --rtk --fix [CODES] <paths>,xstyle --rtk --diff(changed lines only). The human output (colors, tables, source lines) is for the user's terminal only. - xstyle itself lives in its own repository (TsukiNi22/xstyle,
~/personal_delivery/other/xstyle). - Local build of the tools (
tools/claude-cluster:cmake -S tools/claude-cluster -B /tmp/cc-build, thenxstyle --rtk -r tools/claude-cluster); test claude-cluster isolated withCLAUDE_CLUSTER_CONFIG_DIR,CLAUDE_CLUSTER_DATA_DIRandCLAUDE_CLUSTER_SOCKET(claude-cluster serve+ the headless commands).
Writing skills
- English, the user's style skills for the code of the scripts (
python-style,coding-stylefor shell,cpp-style). - A new skill:
skills/<category>/<skill>/SKILL.mdwithname/descriptionfrontmatter and itsrequires.txt, the routers that should load it, the marketplace (.claude-plugin/marketplace.json, one plugin per category folder), thenpython3 scripts/readme.py(writes the tables ofskills/README.mdandskills/<category>/README.mdfrom the frontmatter, never edited by hand between their markers) andpython3 scripts/check.py(the CI runs it too). - Scripts tested for real before committing (generated files, outputs), placeholders
{{NAME}}in the templates.
Versions
- The tools (claude-cluster...) follow major.minor.patch by the size of the change: a real feature (a new mode, view, subsystem: the supervisor) -> minor (1.5.0); fixes, look changes, a few settings -> patch (1.5.1); a breaking change (config / data format, a command removed) -> major. Several features in one release: one minor bump.
Git
- Commits allowed in this repository (the user granted it), format of
git-conventions(type(scope): message), ending with theCo-Authored-Bytrailer of the current model; never force-push or rewrite pushed history without asking.
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.

