writing-agents
Skill0 starsChanged 6 days agoMITView on GitHub
Use when writing, editing, or reviewing AGENTS.md files.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- techmefr/mentistheir own version, first seen Sep 11, 2026
- tunahanaliozturk/ateliertheir own version, first seen Jun 20, 2026
- pjordanandrsn/claude-desktop-asahitheir own version, first seen May 24, 2026
- aaddrick/claude-pipelinetheir own version, first seen Feb 25, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- aaddrick/claude-pipeline★ 128same name
- pjordanandrsn/claude-desktop-asahi★ 1same name
- tunahanaliozturk/atelier★ 1same name
- techmefr/mentis★ 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.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
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 6
Read and apply the writing-text skill to the target document.
- Distinctive: line 12
When the project has a glossary, point to it and say to read it before naming a concept.
- Distinctive: line 14
Keep repository-wide guidance in the root AGENTS.md and directory-specific guidance near the work it governs.
- Distinctive: line 16
Keep each instruction in one authoritative place.
“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
Read and apply the writing-text skill to the target document.
Capture project conventions, constraints, and non-obvious context that affect the agent's work. Prefer information the agent cannot easily discover from the repository over descriptions of files, commands, or configuration it can inspect.
When the project has checks, state which ones each kind of change requires, such as documentation only, configuration, code, and before a merge. When a new worktree's build directory can be seeded from an existing checkout to avoid a full build, say how and what makes a copy unsafe.
When the project has a glossary, point to it and say to read it before naming a concept.
Keep repository-wide guidance in the root AGENTS.md and directory-specific guidance near the work it governs. Check applicable parent instructions before adding local guidance.
Keep each instruction in one authoritative place. Reference existing guidance instead of repeating it, and state when linked material should be read. Add detail only when it changes how the agent should work.
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.