Content Writer
Overview
Modular content creation system with pluggable writing personas. Select a persona to define voice, tone, and style — the skill handles structure, SEO, and quality gates. Personas live in personas/ and can be added without modifying this skill.
When to Use
- Writing blog posts, articles, or editorial content
- Creating news pieces or opinion articles
- Any long-form content that needs a distinct voice
- When the user requests a specific writing style or persona
Related: to authenticate human voice / remove AI-typical patterns in any draft, see human-voice-writing; it authenticates voice, it does not override an explicit persona.
Architecture
content-writer/
SKILL.md # This file — orchestrator
personas/
jeremy-clarkson.md # Bold, dramatic, dry humor
# Add new personas here as .md files
Adding a persona: Create a new .md file in personas/ following the persona template structure. No changes needed to this file.
Content Creation Process
digraph content_flow {
"Select persona" [shape=box];
"Define angle + audience" [shape=box];
"Create outline" [shape=box];
"Write draft in persona voice" [shape=box];
"SEO check" [shape=box];
"Persona compliance check" [shape=diamond];
"Revise voice" [shape=box];
"Final content" [shape=doublecircle];
"Select persona" -> "Define angle + audience";
"Define angle + audience" -> "Create outline";
"Create outline" -> "Write draft in persona voice";
"Write draft in persona voice" -> "SEO check";
"SEO check" -> "Persona compliance check";
"Persona compliance check" -> "Revise voice" [label="fails"];
"Persona compliance check" -> "Final content" [label="passes"];
"Revise voice" -> "Persona compliance check";
}
Step 1: Select Persona
Load the requested persona file from personas/. If no persona specified, ask the user. Read the full persona file — it defines voice, patterns, red flags, and self-check criteria.
Step 2: Define Angle + Audience
Before writing a single word, establish:
| Element |
Question |
| Angle |
What's the hook? Why should anyone care RIGHT NOW? |
| Audience |
Who reads this? What do they already know? |
| Goal |
Inform? Persuade? Entertain? Drive action? |
| CTA |
What should the reader do after reading? |
| Key facts |
What data/research supports the piece? |
Step 3: Create Outline
Structure the piece with the persona's natural rhythm. Every persona file includes structural preferences. General rules:
- Opening: Hook within first 2 sentences. No throat-clearing.
- Body: 3-5 major sections with clear progression
- Closing: Strong ending that echoes the opening or delivers a punchline
- Length: Blog posts 800-1500 words. Features 1500-2500 words.
Step 4: Write in Persona Voice
Follow the persona file exactly. Key rules:
- Read the persona's "Voice DNA" section — these are the non-negotiable style markers
- Use the persona's sentence patterns — rhythm matters more than vocabulary
- Apply rhetorical devices from the persona's toolkit
- Check against "Never Do" list — every persona defines anti-patterns
Step 5: SEO Integration
Content must serve both readers AND search engines:
| Element |
Requirement |
| Title tag |
Include primary keyword, compelling, <60 chars |
| Meta description |
Summarise with hook, include keyword, <155 chars |
| H1 |
One per page, includes primary keyword naturally |
| H2/H3 |
Logical hierarchy, keyword variations where natural |
| Internal links |
Link to relevant products/pages on site (2-5 per post) |
| Image alt text |
Descriptive, include keyword where relevant |
| URL slug |
Short, keyword-rich, hyphenated |
SEO must not break voice. If an SEO requirement makes the writing sound robotic, find a way to hit the keyword naturally within the persona's style. Never stuff keywords.
Localisation: UK English
All content defaults to British English unless explicitly overridden:
| Rule |
Example |
| Spelling |
colour, centre, optimise, defence, catalogue, licence (noun) |
| Currency |
£ (GBP) first, with USD in parentheses if needed for context |
| Units |
Metric primary. Use miles only for driving distances. |
| Date format |
DD Month YYYY (e.g., 17 March 2026) — never MM/DD/YYYY |
| Vocabulary |
boot (not trunk), bonnet (not hood), pavement (not sidewalk), mobile (not cell phone), post (not mail), quid/pounds (not dollars) |
| Cultural references |
British — Premier League, Nando's, M&S, B&Q, Argos, Currys. Not Walmart, Home Depot, Target. |
| Tone markers |
"brilliant", "rubbish", "dodgy", "sorted", "mate", "bloke", "proper" |
| Retail/pricing |
Reference UK retailers (Scan, CCL, Overclockers UK, Currys, Argos, Amazon UK) not US ones (Newegg, Best Buy, Micro Center) |
| Geography |
UK cities, counties, regions. Reference local context where relevant. |
| Legal/regulatory |
GDPR, Consumer Rights Act 2015, Distance Selling Regulations — not FTC, FCC. |
Persona files can override specific localisation rules (e.g., an American persona would use US English). The persona's localisation takes precedence over these defaults.
Step 6: Persona Compliance Check
Before finalising, run through the persona's self-check questions. Every persona file includes a "Compliance Checklist" section. The content must pass ALL items.
Output Format
Deliver content as:
## Meta
- **Title tag**: [optimised title]
- **Meta description**: [155 chars max]
- **URL slug**: /blog/[slug]
- **Persona used**: [name]
- **Word count**: [X]
- **Target keyword**: [primary]
- **Secondary keywords**: [list]
## Content
[Full article in HTML-ready format with H2/H3 structure]
## Internal Links Used
- [Link text](URL) — context
Available Personas
| Persona |
Style |
Best For |
jeremy-clarkson |
Bold, dramatic, dry British humor, opinionated |
Opinion pieces, market commentary, "state of things" articles, rants about pricing/industry |
Persona File Template
When creating new personas, follow this structure:
---
name: persona-name
description: One-line description of voice and best use cases
---
# [Persona Name] Voice
## Voice DNA (Non-Negotiable)
[3-5 core characteristics that MUST be present]
## Sentence Patterns
[How sentences are structured — rhythm, length variation, punctuation]
## Rhetorical Devices
[Specific techniques this persona uses — metaphors, callbacks, rule of three, etc.]
## Vocabulary & Phrasing
[Words/phrases to USE and words/phrases to AVOID]
## Opening Patterns
[How this persona starts articles — with examples]
## Closing Patterns
[How this persona ends articles — with examples]
## Never Do
[Anti-patterns that break the voice]
## Compliance Checklist
[Questions to verify the content sounds like this persona]
## Example Passages
[2-3 short examples showing the voice in action on tech topics]
See also
business-writing — internal and stakeholder writing (email, message, one-pager, proposal,
status update). This skill is editorial and marketing content for an audience that chose to read.
1---2name: content-writer3description: Use when creating blog posts, articles, editorial content, or any long-form written content for websites. Orchestrates content creation with selectable writing personas for voice and style. Trigger on requests to write blog posts, articles, news pieces, opinion pieces, or editorial content.4---56# Content Writer78## Overview910Modular content creation system with **pluggable writing personas**. Select a persona to define voice, tone, and style — the skill handles structure, SEO, and quality gates. Personas live in `personas/` and can be added without modifying this skill.1112## When to Use1314- Writing blog posts, articles, or editorial content15- Creating news pieces or opinion articles16- Any long-form content that needs a distinct voice17- When the user requests a specific writing style or persona1819> **Related:** to authenticate human voice / remove AI-typical patterns in any draft, see `human-voice-writing`; it authenticates voice, it does not override an explicit persona.2021## Architecture2223```24content-writer/25 SKILL.md # This file — orchestrator26 personas/27 jeremy-clarkson.md # Bold, dramatic, dry humor28 # Add new personas here as .md files29```3031**Adding a persona:** Create a new `.md` file in `personas/` following the persona template structure. No changes needed to this file.3233## Content Creation Process3435```dot36digraph content_flow {37 "Select persona" [shape=box];38 "Define angle + audience" [shape=box];39 "Create outline" [shape=box];40 "Write draft in persona voice" [shape=box];41 "SEO check" [shape=box];42 "Persona compliance check" [shape=diamond];43 "Revise voice" [shape=box];44 "Final content" [shape=doublecircle];4546 "Select persona" -> "Define angle + audience";47 "Define angle + audience" -> "Create outline";48 "Create outline" -> "Write draft in persona voice";49 "Write draft in persona voice" -> "SEO check";50 "SEO check" -> "Persona compliance check";51 "Persona compliance check" -> "Revise voice" [label="fails"];52 "Persona compliance check" -> "Final content" [label="passes"];53 "Revise voice" -> "Persona compliance check";54}55```5657### Step 1: Select Persona5859Load the requested persona file from `personas/`. If no persona specified, ask the user. Read the full persona file — it defines voice, patterns, red flags, and self-check criteria.6061### Step 2: Define Angle + Audience6263Before writing a single word, establish:6465| Element | Question |66|---------|----------|67| **Angle** | What's the hook? Why should anyone care RIGHT NOW? |68| **Audience** | Who reads this? What do they already know? |69| **Goal** | Inform? Persuade? Entertain? Drive action? |70| **CTA** | What should the reader do after reading? |71| **Key facts** | What data/research supports the piece? |7273### Step 3: Create Outline7475Structure the piece with the persona's natural rhythm. Every persona file includes structural preferences. General rules:7677- **Opening**: Hook within first 2 sentences. No throat-clearing.78- **Body**: 3-5 major sections with clear progression79- **Closing**: Strong ending that echoes the opening or delivers a punchline80- **Length**: Blog posts 800-1500 words. Features 1500-2500 words.8182### Step 4: Write in Persona Voice8384Follow the persona file exactly. Key rules:85861. **Read the persona's "Voice DNA" section** — these are the non-negotiable style markers872. **Use the persona's sentence patterns** — rhythm matters more than vocabulary883. **Apply rhetorical devices** from the persona's toolkit894. **Check against "Never Do" list** — every persona defines anti-patterns9091### Step 5: SEO Integration9293Content must serve both readers AND search engines:9495| Element | Requirement |96|---------|-------------|97| **Title tag** | Include primary keyword, compelling, <60 chars |98| **Meta description** | Summarise with hook, include keyword, <155 chars |99| **H1** | One per page, includes primary keyword naturally |100| **H2/H3** | Logical hierarchy, keyword variations where natural |101| **Internal links** | Link to relevant products/pages on site (2-5 per post) |102| **Image alt text** | Descriptive, include keyword where relevant |103| **URL slug** | Short, keyword-rich, hyphenated |104105**SEO must not break voice.** If an SEO requirement makes the writing sound robotic, find a way to hit the keyword naturally within the persona's style. Never stuff keywords.106107### Localisation: UK English108109All content defaults to **British English** unless explicitly overridden:110111| Rule | Example |112|------|---------|113| **Spelling** | colour, centre, optimise, defence, catalogue, licence (noun) |114| **Currency** | £ (GBP) first, with USD in parentheses if needed for context |115| **Units** | Metric primary. Use miles only for driving distances. |116| **Date format** | DD Month YYYY (e.g., 17 March 2026) — never MM/DD/YYYY |117| **Vocabulary** | boot (not trunk), bonnet (not hood), pavement (not sidewalk), mobile (not cell phone), post (not mail), quid/pounds (not dollars) |118| **Cultural references** | British — Premier League, Nando's, M&S, B&Q, Argos, Currys. Not Walmart, Home Depot, Target. |119| **Tone markers** | "brilliant", "rubbish", "dodgy", "sorted", "mate", "bloke", "proper" |120| **Retail/pricing** | Reference UK retailers (Scan, CCL, Overclockers UK, Currys, Argos, Amazon UK) not US ones (Newegg, Best Buy, Micro Center) |121| **Geography** | UK cities, counties, regions. Reference local context where relevant. |122| **Legal/regulatory** | GDPR, Consumer Rights Act 2015, Distance Selling Regulations — not FTC, FCC. |123124**Persona files can override** specific localisation rules (e.g., an American persona would use US English). The persona's localisation takes precedence over these defaults.125126### Step 6: Persona Compliance Check127128Before finalising, run through the persona's self-check questions. Every persona file includes a "Compliance Checklist" section. The content must pass ALL items.129130## Output Format131132Deliver content as:133134```135## Meta136- **Title tag**: [optimised title]137- **Meta description**: [155 chars max]138- **URL slug**: /blog/[slug]139- **Persona used**: [name]140- **Word count**: [X]141- **Target keyword**: [primary]142- **Secondary keywords**: [list]143144## Content145146[Full article in HTML-ready format with H2/H3 structure]147148## Internal Links Used149- [Link text](URL) — context150```151152## Available Personas153154| Persona | Style | Best For |155|---------|-------|----------|156| `jeremy-clarkson` | Bold, dramatic, dry British humor, opinionated | Opinion pieces, market commentary, "state of things" articles, rants about pricing/industry |157158## Persona File Template159160When creating new personas, follow this structure:161162```markdown163---164name: persona-name165description: One-line description of voice and best use cases166---167168# [Persona Name] Voice169170## Voice DNA (Non-Negotiable)171[3-5 core characteristics that MUST be present]172173## Sentence Patterns174[How sentences are structured — rhythm, length variation, punctuation]175176## Rhetorical Devices177[Specific techniques this persona uses — metaphors, callbacks, rule of three, etc.]178179## Vocabulary & Phrasing180[Words/phrases to USE and words/phrases to AVOID]181182## Opening Patterns183[How this persona starts articles — with examples]184185## Closing Patterns186[How this persona ends articles — with examples]187188## Never Do189[Anti-patterns that break the voice]190191## Compliance Checklist192[Questions to verify the content sounds like this persona]193194## Example Passages195[2-3 short examples showing the voice in action on tech topics]196```197198## See also199200- `business-writing` — internal and stakeholder writing (email, message, one-pager, proposal,201 status update). This skill is editorial and marketing content for an audience that chose to read.