doc-skills
AGENTS.md2 starsChanged 50 days agoMITView on GitHub
The doc-init / doc-compact / doc-update skills published in this repository.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- x0c/agent-doc-skillsword for word, first seen Sep 23, 2026
Other versions1 project uses a version of this.
Word for word · 1
- x0c/agent-doc-skills★ 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,774 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 repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- doc-compactSkill
- doc-initSkill
- doc-updateSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Identity: all commits must use the anonymous x0c <x0c@users.noreply.github.com> identity for both author and committer.
- Distinctive: line 14
Privacy: never push company names, internal platform names, personal names, phone numbers, or internal hostnames/URLs.
- Very specific: line 15
Verification: after changing any scripts/ file, run the skill's own verification (e.g.
≈ “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
agent-doc-skills
The doc-init / doc-compact / doc-update skills published in this repository.
Repository layout and source of truth
doc-init/,doc-compact/,doc-update/— the three skills. Each directory is a self-contained skill (SKILL.md+references/+scripts/).README.md— bilingual (English + Chinese) introduction and install instructions.- These published copies are not the source of truth. The authoritative source lives in the maintainer's local agentsync skills directory; changes are made there and synced here. Do not maintain divergent edits in this repository.
Hard constraints for contributors
- Identity: all commits must use the anonymous
x0c <x0c@users.noreply.github.com>identity for both author and committer. Never commit with a personal or corporate git identity — the history is public. - Privacy: never push company names, internal platform names, personal names, phone numbers, or internal hostnames/URLs. Keep all content generic.
- Verification: after changing any
scripts/file, run the skill's own verification (e.g.python3 scripts/doc_nav_lint.pysmoke test on a fixture) before pushing. After changingSKILL.md, re-read the full file to confirm structure is intact. - Language: skill bodies are English-only. The README is bilingual.
Documentation map
README.md— what each skill does, how they cooperate, install methods.doc-init/references/— document templates, knowledge-network design, scan report format.doc-compact/references/standard.md— the documentation-governance standard the skill audits against.doc-update/SKILL.md— self-contained; no extra references.
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.

