chara-toolkit / skills
AGENTS.md2 starsChanged 11 days agoMITView on GitHub
Applies to skills/.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cmdr-chara/codex-toolkitword for word, first seen Oct 31, 2026
Other versions1 project uses a version of this.
Word for word · 1
- cmdr-chara/codex-toolkit★ 2100% 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.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,843 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bin/AGENTS.mdAGENTS.md
- evaluations/AGENTS.mdAGENTS.md
- orchestration/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- skills/llms.txtllms.txt
- bug-finderSkill
- codebase-evolution-controllerSkill
- codebase-improvement-plannerSkill
- completion-proofSkill
- content-provenance-hygieneSkill
- cpp-engineeringSkill
- debugging-investigatorSkill
- delegate-with-mission-cardsSkill
- documentation-synchronizerSkill
- expo-react-native-builderSkill
- flutter-production-builderSkill
- go-engineeringSkill
- kotlin-engineeringSkill
- mobile-architecture-directorSkill
- multi-agent-work-coordinatorSkill
- optimize-codebase-performanceSkill
- product-design-directorSkill
- production-web-builderSkill
- python-engineeringSkill
- repository-intelligenceSkill
- review-and-refactor-codeSkill
- rust-engineeringSkill
- screenshot-to-interfaceSkill
- security-reviewSkill
- swift-engineeringSkill
- toolchain-preflightSkill
- typescript-quality-enforcerSkill
- verification-and-releaseSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Prefer a short SKILL.md router plus task-specific references/scripts over a monolithic instruction file.
- Distinctive: line 9
Keep examples representative rather than exhaustive.
- Very specific: line 10
Treat roughly 180 root lines / 1400 body words as a review signal, not a target or hard limit.
- Distinctive: line 12
When behavior changes, update the matching validator/evaluation and any catalog text that users rely on.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
Skill authoring instructions
Applies to skills/.
- Each skill must have one clear decision domain and a trigger narrow enough to avoid irrelevant loading.
- Prefer a short
SKILL.mdrouter plus task-specific references/scripts over a monolithic instruction file. Keep discovery descriptions to the smallest wording that reliably distinguishes activation. - State durable constraints, required evidence, permissions, and completion conditions; avoid rigid step ordering unless the order is semantically required.
- Reuse existing specialists before creating a new overlapping skill.
- Keep examples representative rather than exhaustive. Do not make every historical edge case part of the default context.
- Treat roughly 180 root lines / 1400 body words as a review signal, not a target or hard limit. Extract conditional checklists, rare failure cases, ecosystem guidance, and specialist playbooks behind explicit
references/routing. - Preserve explicit safety, approval, migration, and stop conditions when simplifying instructions.
- When behavior changes, update the matching validator/evaluation and any catalog text that users rely on.
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.