writer
Skill216 starsChanged 17 days agoApache-2.0View on GitHub
Authoritative reference for writing the project's prose. Use before writing, editing, or translating any document, command text, comment, or user-facing message.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- krishagel/geoffreytheir own version, first seen Nov 15, 2026
- flaqai/backlink_skillstheir own version, first seen Nov 12, 2026
- lumpcode/lumpcodetheir own version, first seen Nov 8, 2026
- David-Florian2013/write-then-checktheir own version, first seen Nov 1, 2026
- danielgefen/soustheir own version, first seen Aug 25, 2026
- xjsongphy/skillstheir own version, first seen Aug 17, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- flaqai/backlink_skills★ 895same name
- microsoft/aspnetcore-ja-handbook★ 33same name
- Mikefluff/skills★ 26same name
- lumpcode/lumpcode★ 12same name
- botlearn-ai/botlearn-skills★ 9same name
- krishagel/geoffrey★ 9same name
- xjsongphy/skills★ 7same name
- zdyya/writer-skill★ 4same name
- Notryag/north-agent★ 1same name
- vinitjhawar/opencouncil★ 1same name
3 more not listed
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 repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- architectureSkill
- blind-reviewSkill
- calibrateSkill
- cdpSkill
- dashboardSkill
- engineeringSkill
- ingestSkill
- mcp-catalogSkill
- playgroundSkill
- refineSkill
- simulateSkill
- specializeSkill
- testingSkill
- uiSkill
- lagune-charterSkill
- lagune-detectSkill
- lagune-hardenSkill
- lagune-planSkill
- lagune-proveSkill
- lagune-repairSkill
- laguneSkill
- lagune-specializeSkill
- lagune-verifySkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
7
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
- Distinctive: line 17
Avoid em dashes or semicolons where they are not grammatically necessary.
- Distinctive: line 19
When the document already exists, read it and study its existing style before you edit, then write in that same voice.
- Distinctive: line 20
Avoid writing a file path or pasting a code snippet into a document.
- Distinctive: line 26
Remove before you add: before editing existing text, first remove everything that is no longer valid, then adapt and update what changed, …
- Very specific: line 30
Use straight quotes and apostrophes (' and "), never their curly forms, and avoid any character a standard keyboard lacks.
- Distinctive: line 35
When the source is in another language, translate it into natural American English that reads as though written in English from the start, …
- Distinctive: line 37
Avoid literal or stiff translations.
- Distinctive: line 43
After writing, run this checklist:
“Common” is measured: kept by at least 6 in 10 of the 11 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
Text writing
This skill is the specialized, authoritative description of how the project's prose is written: the language and style conventions, the plain-language rule, and the reconcile discipline that keeps documents living. Consult it before writing or editing any document, command text, comment, or user-facing message.
Language and style
- Avoid em dashes or semicolons where they are not grammatically necessary. Where one would go, for example, use the mark the sentence actually calls for, usually a comma, colon, or parentheses.
- Write in complete sentences, each with a beginning, middle, and end, instead of chopping one thought into fragments. A semicolon, an em dash, or a period used to cut a sentence short is the same habit wearing different punctuation, so the fix is to compose the sentence, not to swap the mark that split it.
- When the document already exists, read it and study its existing style before you edit, then write in that same voice. When it is entirely new, read a similar or equivalent file to learn the pattern first.
- Avoid writing a file path or pasting a code snippet into a document. A flat document does not track the source, so a moved file or a changed snippet leaves a stale, broken reference.
Rules
- All project content is written in English (docs, code, comments, command text, user messages), regardless of the language used in chat.
- Less is more: cut anything that adds words without meaning: throat-clearing openers that delay the point, reinforcement triads where one word does the job, framing sentences that announce content instead of being it, and padding that stretches a thought to look thorough. Stop once the point lands.
- Remove before you add: before editing existing text, first remove everything that is no longer valid, then adapt and update what changed, and add new text only when it is genuinely needed.
- Redundancy is forbidden: judged across the whole document, not one sentence at a time. A sentence clean on its own still counts as redundant when its meaning already lives elsewhere. Say each thing once, in the one place it belongs.
- Describe intent, not implementation: do not restate logic, cite specific variable or method names, or re-explain how something is built. A rename or a refactor silently turns that prose false, so say what it does and why, and let the code stay the single source of how.
- Never break lines by hand in the middle of the prose: line width, wrapping, and formatting are Prettier's job, not yours.
- Use straight quotes and apostrophes (
'and"), never their curly forms, and avoid any character a standard keyboard lacks. - Reconcile, never append. When updating existing text, reconcile it against the current truth instead of layering new content on top of the old. Re-check each existing statement: keep what still holds, rewrite what changed, and remove what no longer applies. Write genuinely new content only for what is actually new. The result must read as a clean statement of the present, not a record of how it got there. The past does not matter for its own sake. Never let a document grow by accumulation alone.
Translation
When the source is in another language, translate it into natural American English that reads as though written in English from the start, as fluent as the original.
- Avoid literal or stiff translations. ❌ "The name of the project of the organization" is a calque, ✅ "The project name in the organization" is English.
- Grasp the original's tone, idiom, and intent before you translate, then reproduce those in English.
- Where the source is unclear or ambiguous, ask for more context before translating instead of guessing.
Review
After writing, run this checklist:
- Remove every redundancy, across the whole document.
- Where the writing runs long-winded or roundabout, tighten it to be direct, without sacrificing clarity.
- Confirm every rule and recommendation in this skill is followed.
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.

