blog-persona

Solid

Create and manage writing personas with NNGroup 4-dimension tone framework (Funny-Serious, Formal-Casual, Respectful-Irreverent, Enthusiastic-Matter-of-fact). Personas define readability targets, sentence length distribution, vocabulary tier, contraction frequency, and summary box label. Used by blog-write and blog-rewrite to enforce consistent voice. Use when user says "persona", "voice", "tone", "writing style", "brand voice", "create persona", "use persona".

AI & Automation 923 stars 190 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
99
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Blog Persona - Writing Voice Management Create, store, and enforce writing personas based on the NNGroup 4-dimension tone framework and CMI Brand Voice Chart. Personas ensure consistent voice across all blog content produced by blog-write and blog-rewrite. ## Commands | Command | Purpose | |---------|---------| | `/blog persona create` | Interactive interview to build a new persona | | `/blog persona list` | Show all saved personas | | `/blog persona use <name>` | Set active persona for current session | | `/blog persona show <name>` | Display full persona profile | ## Create Workflow Run the 6-step interactive interview. Ask each step, wait for response, then proceed. ### Step 1: Brand Basics Ask the user for: - **Brand name** - company or personal brand - **Industry** - primary sector (e.g., SaaS, health, finance, education) - **Target audience** - who reads the blog (role, experience level, goals) - **One-sentence brand mission** - what the brand helps people do ### Step 2: Tone Dimensions (NNGroup Framework) Present each dimension as a 0.0 to 1.0 slider. Explain both ends with examples. | Dimension | 0.0 End | 1.0 End | Example at 0.0 | Example at 1.0 | |-----------|---------|---------|-----------------|-----------------| | funny_serious | Funny | Serious | "Let's be real, nobody reads Terms of Service" | "Understanding legal agreements protects your business" | | formal_casual | Formal | Casual | "We are pleased to announce" | "Guess what - we shipped it!" | ...

Details

Author
AgriciDaniel
Repository
AgriciDaniel/claude-blog
Created
3 months ago
Last Updated
3 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

persona-guide

Use when the user asks about personas, wants to choose the right persona for their content, or needs help understanding how personas affect generated content. Covers both system personas and custom personas.

1 Updated today
ninnettesudanese653
Code & Development Solid

blog-brand

Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".

923 Updated 3 days ago
AgriciDaniel
AI & Automation Listed

persona-write

Scaffold a user persona document with required fields — demographics, goals, frustrations, behaviors, JTBD, devices, accessibility considerations

2 Updated today
bakw00ds
AI & Automation Listed

recipe-persona

Create or update personas with demographic, contextual, JTBD, and behavioral data

0 Updated today
Florellaoccipital551
AI & Automation Listed

persona-definition

Create individual user personas and customer archetypes — with demographics, goals, pain points, behaviors, and empathy maps — to represent the humans a product or system is built for. Use when the user asks to define personas, create user archetypes, describe target users, build empathy maps, or characterize the audience for a product or design decision. NOT for mapping stakeholders across an organization, RACI charts, or influence analysis (use persona-mapping). NOT for designing research interview flows (use elicitation).

9 Updated 2 days ago
viktorbezdek