writing-style
Skill8 starsChanged 7 months agoNo licenceView on GitHub
Load writing style guidance before creating or editing any written content. Invoke this skill before writing or editing text content.
33 other projects use a version of this.
Adopted by
Most recently taken up by
- apetrov/skillstheir own version, first seen Nov 16, 2026
- bjoern621/claude-skillstheir own version, first seen Nov 16, 2026
- micooz/skillstheir own version, first seen Nov 15, 2026
- timmo001/skillstheir own version, first seen Nov 15, 2026
- modaal-agent/skillstheir own version, first seen Nov 15, 2026
- timmo001/notestheir own version, first seen Nov 11, 2026
Used with
Projects with it also use changeset-scope, skill-prefixes and 5 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
timmo001Skillskill-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
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 4 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 versions33 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 33
- pydantic/monty★ 8.9ksame name
- OpenLAIR/dr-claw★ 1.2ksame name
- javierbrea/eslint-plugin-boundaries★ 1ksame name
- astashov/liftosaur★ 780same name
- open-thoughts/OpenThoughts-Agent★ 309same name
- anotb/management-consulting-plugin★ 62same name
- kaustubhhiware/agent-skills-fullstack-development★ 16same name
- micooz/skills★ 12same name
- lout33/writing-style-skill★ 10same name
- chnlich/charlie-bot★ 9same name
23 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 repository22 other files it gives its agents.
- blog-scheduleSkill
- content-blogSkill
- content-carousel-renderSkill
- content-gdocsSkill
- content-imageSkill
- content-initSkill
- content-screenshotSkill
- content-socialSkill
- content-statusSkill
- content-transcribeSkill
- content-videoSkill
- content-youtubeSkill
- gemini-3Skill
- image-uploadSkill
- openai-52Skill
- publishSkill
- video-annotationsSkill
- video-chaptersSkill
- video-descriptionSkill
- video-editorSkill
- video-overlaysSkill
- video-resolveSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 31 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 31 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.
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.

