Individual skill

content-style-guide

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.

skills/content-style-guide/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top