Generate project-root BRAND.md and VOICE.md files from interactive interview inputs.
npx skills add https://github.com/shenxingy/Clade --skill blog-brand
Please help me install this Agent Skill. Skill: blog-brand Source: https://github.com/shenxingy/Clade/tree/main/configs/skills/blog-brand Command: npx skills add https://github.com/shenxingy/Clade --skill blog-brand
The blog-brand skill solves the problem of inconsistent messaging by establishing a single, persistent editorial source of truth for audience, positioning, voice, taboo phrases, and disclosure rules across multiple blog sub-skills.
BRAND.md and VOICE.md so downstream blog writing/reviewing commands share consistent guidelines./blog brand init, /blog brand show, and /blog brand update, with optional pre-fill from blog-persona.Run /blog brand init to answer a short interactive interview and automatically write BRAND.md and VOICE.md to your project root.
High-intent search queries and answers about installing and using this skill.
To maintain consistent editorial voice across multiple blog posts, you establish durable brand context files at the project root. This creates a persistent source of truth for audience and positioning that auto-loads into downstream writing commands across sessions.
The best way to set up cross-skill brand guidelines is to run an interactive interview that captures audience, positioning, and editorial rules. This generates project-root markdown documents that automatically apply brand context to all downstream blog operations.
You create and update markdown brand guidelines by running initialization, viewing, and update commands. These commands let you answer interactive interview questions to write or modify project-root files containing your editorial rules, voice constraints, and headline preferences.
Yes, you can use persona integration to pre-fill your blog's editorial voice constraints. The initialization command supports optional pre-fill from persona data before you answer the interactive interview covering audience, positioning, and taboo language.
Your blog content strategy loses context between sessions because it lacks a persistent editorial source of truth. Generating project-root brand and voice markdown files ensures your guidelines automatically load and survive across runs and commands.
jmaglySynthesize audience data into unified personas and behavioral segments.
LerianStudioStructure functional documentation with editorial guidelines and formatting patterns.
NammDevPlan content strategy workflows with pillar mapping and editorial calendars.
ValorVieInitialize knowledge bases and cross-skill memory for task dialogues.