blog-brand

Generate BRAND.md and VOICE.md editorial context files for blog writing workflows.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/captaindevv/SEO-ajaypipes --skill blog-brand-captaindevv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blog-brand
Source: https://github.com/captaindevv/SEO-ajaypipes/tree/main/skills/blog-brand
Command: npx skills add https://github.com/captaindevv/SEO-ajaypipes --skill blog-brand-captaindevv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Blog content teams lack a single canonical source for brand voice, audience, and editorial rules, so every writing command re-derives brand context inconsistently. This Skill creates persistent BRAND.md and VOICE.md files at the project root that all blog sub-skills auto-load before writing or reviewing. ## Core Features & Use Cases - Interactive brand interview: A 5-step guided workflow captures audience, positioning, editorial rules, topic boundaries, and voice preferences, then writes structured BRAND.md and VOICE.md files. - Persona integration: Pre-fills voice answers from existing blog-persona JSON and mirrors tone sliders into readable prose, keeping persona JSON as the source of truth. - Show and update commands: Display current brand context or re-run the interview with existing values as defaults for iterative refinement. - Use Case: A content lead runs the init command once to define audience, taboo phrases, and competitor differentiators; every subsequent blog write, brief, or review command automatically applies those rules. ## Quick Start Ask the assistant to run the blog brand init command and answer the interview questions to create BRAND.md and VOICE.md in your project root.

Frequently Asked Questions about blog-brand

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create brand voice guidelines for blog content?▼

Run the blog brand init command to start a 5-step interactive interview covering audience, positioning, editorial rules, topic scope, and voice. It writes BRAND.md and VOICE.md to your project root, which all blog sub-skills auto-load.

What is the difference between blog-brand and blog-persona?▼

blog-persona manages structured persona JSON for programmatic tone enforcement, while blog-brand produces readable BRAND.md and VOICE.md files for cross-skill prompts. blog-brand consumes persona JSON as a pre-fill source but does not replace it.

Does blog-brand work without an existing persona file?▼

Yes, the voice interview questions still produce a complete VOICE.md without persona JSON. You can run blog persona create afterward if you want programmatic tone enforcement.

What happens if BRAND.md and VOICE.md are missing?▼

Blog commands behave exactly as before with no brand context injected. The files are opt-in; the orchestrator never prompts you to create them, and the show command reports which files are missing.

How do I update existing brand guidelines without starting over?▼

Run the blog brand update command, which re-runs the interview with your current values pre-filled as defaults. Press enter to keep a value or type a new one, and both files are overwritten with an updated date.