writing-style
Skill0 starsChanged 22 days agoMITView on GitHub
How written documents should look and read. Use before writing or revising a report, brief, plan, README, handoff or write-up that a person will read. Not for chat replies or agent-to-agent notes.
29 other projects use a version of this.
Adopted by
Most recently taken up by
- timmo001/notestheir own version, first seen Nov 8, 2026
- timmo001/contexttheir own version, first seen Nov 8, 2026
- OpenLAIR/dr-clawtheir own version, first seen Nov 8, 2026
- timmo001/skillstheir own version, first seen Nov 7, 2026
- javierbrea/eslint-plugin-boundariestheir own version, first seen Nov 2, 2026
- anotb/management-consulting-plugintheir own version, first seen Nov 1, 2026
Used with
Projects with it also use changeset-scope, skill-prefixes and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
timmo001Skillchangeset-scope
Keep all scoped code work contained to the user-defined changeset. Use for implementation, fixes, diagnosis, refactoring, cleanup, and review when explicit instructions, named files, diffs, branches, pull requests, or injected work scopes define the boundary.
Also in 3 projects that use this
- timmo001Skill
skill-prefixes
Name skills with an owner prefix so they do not collide with shared, imported or other repositories' skills. Use when creating, renaming, importing or reviewing a skill name, especially for repository-local or tool-owned skills.
Also in 3 projects that use this
NVIDIASkilltesting
Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.
Also in 3 projects that use this
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 3 projects that use this
- +2 more from timmo001
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 29
- pydantic/monty★ 8.9ksame name
- OpenLAIR/dr-claw★ 1.2ksame name
- javierbrea/eslint-plugin-boundaries★ 1ksame name
- astashov/liftosaur★ 775same name
- open-thoughts/OpenThoughts-Agent★ 309same name
- anotb/management-consulting-plugin★ 62same name
- kaustubhhiware/agent-skills-fullstack-development★ 16same name
- lout33/writing-style-skill★ 10same name
- chnlich/charlie-bot★ 9same name
- Isaac-Flath/agent-starter-skills★ 8same name
19 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 repository4 other files it gives its agents.
- profile/AGENTS.mdAGENTS.md
- profile/CLAUDE.mdCLAUDE.md
- code-reviewSkill
- my-skillSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 28 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Proportionate length: If it runs past a few pages, distil it or move detail into an appendix.
“Common” is measured: kept by at least 6 in 10 of the 28 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
Writing style
An example skill. Edit it to match how you want documents to read.
Rules
- Summary first. Open with 3 to 5 plain lines: the outcome and what it means for the reader.
- Every word earns its place. Cut restated context, hedging and discarded options.
- Dot points over paragraphs. One idea per line. Headings are fine.
- Written for its reader. Name the audience, then drop what they do not need. Explain jargon.
- Proportionate length. If it runs past a few pages, distil it or move detail into an appendix.
- Dates at the end of file names:
plan-2026-10-14.md.
Check before delivering
- Can the reader get the point from the first five lines?
- Is anything there only because it was easy to include?
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.