What do I need to use Content Style Guide?

The brand & audience; Existing voice cues; Surfaces; Specifics.

Is Content Style Guide free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Content Style Guide

Q: How do I know the Content Style Guide output is good?

The skill verifies itself against its own 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.

🔵 Stable🕐 updated 2026-06-30 🔷 SkillSpec L3 pm-uxwriting

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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸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.

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓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

⚠️ What it refuses to do

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

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="content-style-guide"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Content Style Guide is one of 625 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog