UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
Create a content style guide / voice & tone guide so everyone writes consistently.
Install Content Style Guide
$ npx skills add mohitagw15856/pm-claude-skills --skill content-style-guide -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills content-style-guide --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content-style-guide .claude/skills/content-style-guide && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "content-style-guide" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/content-style-guide into .claude/skills/content-style-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-style-guide", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/content-style-guideType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill content-style-guide -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills content-style-guide --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/content-style-guide .agents/skills/content-style-guide && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-style-guide" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/content-style-guide into .agents/skills/content-style-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-style-guide", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill content-style-guide -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills content-style-guide --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/content-style-guide .cursor/skills/content-style-guide && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "content-style-guide" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/content-style-guide into .cursor/skills/content-style-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-style-guide", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/content-style-guide--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill content-style-guide -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills content-style-guide --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/content-style-guide .gemini/skills/content-style-guide && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "content-style-guide" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/content-style-guide into .gemini/skills/content-style-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-style-guide", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills content-style-guideInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill content-style-guide -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/content-style-guide .github/skills/content-style-guide && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "content-style-guide" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/content-style-guide into .github/skills/content-style-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-style-guide", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill content-style-guide -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills content-style-guide --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/content-style-guide .opencode/skills/content-style-guide && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "content-style-guide" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/content-style-guide into .opencode/skills/content-style-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-style-guide", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
content-style-guide- GitHub stars
- 1.4k
- Token cost
- ~1k tokens
- SKILL.md length
- 498 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create a content style guide / voice & tone guide so everyone writes consistently.
- Asked to write a content style guide
- SKILL.md covers Working from a brief, Required Inputs, Output Format and Quality Checks, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A voice and tone guide
What it does
Content Style Guide is an agent skill from mohitagw15856/pm-claude-skills. Create a content style guide / voice & tone guide so everyone writes consistently. Use when asked to write a content style guide, a voice and tone guide, editorial guidelines, or UX-writing standards. Produces a usable guide — voice principles with do/don't examples, tone-by-context, mechanics (grammar, capitalisation, formatting), terminology/word list, and accessibility/inclusivity rules — that a team can actually apply.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Plain language and style rules, Brand voice and tone and Accessibility. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to write a content style guide
- A voice and tone guide
- Editorial guidelines
- UX-writing standards
Example prompts
- “/content-style-guide”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Content Style Guide loads about 1k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 498 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 498 words, ~1,009 tokens.
Download SKILL.mdSave it as
.claude/skills/content-style-guide/SKILL.md (or your agent's skills folder).- name
- content-style-guide
- description
- Create a content style guide / voice & tone guide so everyone writes consistently. Use when asked to write a content style guide, a voice and tone guide, editorial guidelines, or UX-writing standards. Produces a usable guide — voice principles with do/don't examples, tone-by-context, mechanics (grammar, capitalisation, formatting), terminology/word list, and accessibility/inclusivity rules — that a team can actually apply.
Content Style Guide Skill
A style guide makes a brand sound like one voice no matter who's writing. The useful ones aren't 50 pages of rules — they're voice principles with examples, tone guidance by context, and a word list people reach for daily. This skill produces a guide a team will actually use, grounded in concrete do/don't examples rather than abstract adjectives.
Working from a brief
Given "a style guide for our fintech app", produce the full guide anyway — infer voice principles and terminology from the brand and audience, and mark inferred choices for the team to confirm. Make every principle show an example. Never hand back abstract values with no examples.
Required Inputs
Ask for these only if they aren't already provided (else infer and label):
- The brand & audience — what you do, who you write for, and how you want to come across.
- Existing voice cues — sample copy you like (and dislike), and any current rules.
- Surfaces — where this applies (product UI, marketing, support, docs) — tone may shift by surface.
- Specifics — preferred terms, things to avoid, locale (US/UK spelling), formality.
Output Format
[Brand] Content Style Guide
1. Voice — who we are — 3–4 voice principles, each as "We are X, not Y" with a before/after example.
2. Tone — how we adapt — how the voice flexes by context (e.g. celebratory on success, calm and brief on errors, warm in onboarding), with a small table: situation → tone → example.
3. Mechanics — the rules that come up constantly: capitalisation (sentence vs. title case), punctuation (Oxford comma, exclamation marks), numbers/dates/currency, contractions, US/UK spelling, formatting (headings, lists, links, buttons).
4. Word list — a do/don't terminology table: preferred term, what to avoid, and why (product terms, jargon to drop, words that are on/off-brand).
5. Inclusivity & accessibility — inclusive language, reading level, plain-language rules, and accessibility (link text, alt text, no "click here", no directional-only instructions).
6. Quick reference — a one-screen cheat sheet of the most-used rules.
Mark inferred voice/terminology choices (confirm with the team).
Show full SKILL.md (172 more words)Show less
Quality Checks
- Voice principles are concrete ("X, not Y") and each shows a before/after example
- Tone guidance covers multiple real contexts, not one default
- Mechanics cover the rules that actually recur (caps, punctuation, numbers, spelling)
- The word list gives preferred vs. avoid terms with reasons
- Inclusivity and accessibility rules are included and specific
- There's a one-screen quick reference people will actually use
Anti-Patterns
- Do not list abstract values ("be friendly, be clear") with no examples — examples are the guide
- Do not write an exhaustive rulebook no one will read — prioritise the high-frequency decisions
- Do not ignore tone-by-context — the same voice should sound different in an error vs. a celebration
- Do not omit a terminology/word list — inconsistent product terms are the most visible failure
- Do not skip accessibility/inclusivity — they're style rules too
Based On
Content design practice — example-driven voice principles, context-based tone, editorial mechanics, terminology management, and inclusive/accessible language.
Example Trigger Phrases
- "Write a content style guide."
- "Write a voice and tone guide."
- "Set editorial guidelines for the team."
- "Write our UX-writing standards."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/content-style-guide of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Content Style Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Content Style Guide this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1k | Automated safety check: Pass | MIT | |
| UX Writingcontent-designer/ux-writing-skill | 224 | 1 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Nbj Write Clearlydaniel-p-green/nbj-write-clearly | 117 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Blog PersonaAgriciDaniel/claude-blog | 2.3k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Plain Languagethedaviddias/Front-End-Checklist | 74k | — | ~493 | Automated safety check: Pass | MIT | |
| Writing Style ReviewArmDeveloperEcosystem/arm-learning-paths | 154 | — | ~1.9k | Automated safety check: Pass | Custom licence |
Similar skills
Nbj Write Clearly
daniel-p-green/nbj-write-clearly
Drafts, revises, and audits reader-first technical and product documentation.
Blog Persona
AgriciDaniel/claude-blog
Create and manage writing personas with NNGroup 4-dimension tone framework (Funny-Serious, Formal-Casual, Respectful-Irreverent, Enthusiastic-Matter-of-fact).
Plain Language
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Write in plain language.
Writing Style Review
ArmDeveloperEcosystem/arm-learning-paths
Review and improve writing style, voice, tone, readability, inclusive language, Arm terminology, heading style, word choice, and AI-sounding prose in Arm Learning Paths and install guides.
Readability Guidance
testdouble/han
Surfaces Han's shared Human-Readable Output Standard — the readability rule and the writing-voice profile — into the calling skill's own context, so the caller drafts in voice and runs its…
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Content Style Guide
What does Content Style Guide do?
Create a content style guide / voice & tone guide so everyone writes consistently. Content Style Guide is an agent skill from mohitagw15856/pm-claude-skills. Create a content style guide / voice & tone guide so everyone writes consistently.
When should I use Content Style Guide?
Content Style Guide fits situations like: asked to write a content style guide; A voice and tone guide; editorial guidelines; UX-writing standards.
How do I install Content Style Guide in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill content-style-guide -a claude-code`. Or copy the skill folder (skills/content-style-guide in mohitagw15856/pm-claude-skills) into .claude/skills/content-style-guide in your project. Claude Code loads it when a task matches its description.
How do I install Content Style Guide in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill content-style-guide -a codex`. Or copy the skill folder (skills/content-style-guide in mohitagw15856/pm-claude-skills) into .agents/skills/content-style-guide in your project. Codex loads it when a task matches its description.
Can I use Content Style Guide in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill content-style-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-style-guide, .gemini/skills/content-style-guide, .github/skills/content-style-guide and .opencode/skills/content-style-guide in your project.
What does Content Style Guide need to run?
SKILL.md names no scripts, command-line tools or credentials: Content Style Guide is instructions for the agent only.
Does Content Style Guide access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Content Style Guide safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Content Style Guide use?
Content Style Guide is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Content Style Guide use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Content Style Guide?
Skills that share tags, products or a category with Content Style Guide: UX Writing (content-designer/ux-writing-skill, 224 stars), Nbj Write Clearly (daniel-p-green/nbj-write-clearly, 117 stars), Blog Persona (AgriciDaniel/claude-blog, 2.3k stars) and Plain Language (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Content Style Guide?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.