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, the blog orchestrator auto-loads these files for write, rewrite, brief, outline, calendar, and strategy workflows. 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".

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and clearly sequenced with appropriate validation, organized into clean self-contained sections. Its only weakness is conciseness: motivational prose and repeated auto-loading statements could be trimmed without losing clarity.

Suggestions

Trim or remove the 'Why this exists' section; the problem statement is largely inferable and the description already conveys the skill's purpose, so the body can start with the Commands/Init workflow.

State the orchestrator auto-loading behavior once (in the Integration section) and drop the restatement from the intro and the 'When neither file exists' paragraph to remove redundancy.

Consider condensing the blog-persona relationship table to the rows that actually drive behavior (voice fingerprint mirror, taboo/scope ownership), since several rows restate the same audience/positioning split.

Dimension	Reasoning	Score
Conciseness	The templates and interview questions earn their place, but the 'Why this exists' motivation prose restates context Claude could infer, and the auto-loading behavior is repeated across the intro, description, and Integration section, so it could be tightened rather than being lean throughout.	2 / 3
Actionability	It gives a concrete 5-step interview with specific questions, two complete copy-paste-ready markdown templates with bracketed placeholders, and explicit show/update/error-handling procedures — fully actionable guidance for an instruction-only skill.	3 / 3
Workflow Clarity	The init flow is a clear sequenced 5-step interview with 'wait for response, then proceed' gates, plus explicit validation checkpoints (refusing skeleton answers, confirming before overwrite) that cover the destructive overwrite case.	3 / 3
Progressive Disclosure	With no bundle files, the self-contained SKILL.md is organized into clear headed sections (Commands, Init Workflow, Output Files, Show/Update, Integration, Error Handling) with easy navigation and no nested references, matching the well-organized-sections allowance for reference-free skills.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that names concrete actions, provides explicit natural-language triggers, answers both 'what' and 'when', and clearly distinguishes itself from the related blog-persona skill. It earns the top score on every dimension.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions in third person — generating BRAND.md and VOICE.md with enumerated contents (audience, positioning, editorial rules, taboo phrases, competitor differentiation) and auto-loading them for six named workflows — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It explicitly answers both what (generates two named project-root files that the orchestrator auto-loads) and when (an explicit 'Use when user says...' trigger clause), satisfying the top anchor rather than capping at 2.	3 / 3
Trigger Term Quality	The 'Use when user says' clause covers seven natural phrases a user would actually say ('blog brand', 'create brand context', 'brand voice doc', 'BRAND.md', 'VOICE.md', 'establish editorial brand', 'brand guidelines for blog'), matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	It carves a clear niche (durable brand/voice context files) with distinct triggers and explicitly disambiguates from its sibling ('Pairs with blog-persona, which manages the structured persona JSON'), making conflict unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-blog
Path: brain/.raw/sources/claude-blog-skill/skills/blog-brand/SKILL.md
Commit: aec971a

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.