CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

The skill body is highly actionable and clearly structured, with concrete commands, a sequenced interview workflow, and complete output templates plus robust error handling. Its main gaps are mild verbosity in the rationale/comparison sections and the absence of a true validate-fix-retry feedback loop on the destructive write path.

Suggestions

Add an explicit validation checkpoint after writing BRAND.md/VOICE.md (e.g., re-read the files, confirm required sections are non-empty, and only then report success) to turn the overwrite confirmation into a true validate->fix->retry loop.

Trim the 'Why this exists' section and the blog-persona comparison table to the essentials, or move the comparison table into a short reference file, to improve token efficiency.

Consider splitting the full BRAND.md and VOICE.md templates into a references/ file and linking to it from SKILL.md, leaving the body as an overview, to strengthen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-organized sections, concrete commands, and templates that earn their place rather than padding. A few sections — 'Why this exists' and the blog-persona comparison table — are mildly elaborative and could be trimmed, which keeps it just below the lean anchor-5.

4 / 5

Actionability

Fully actionable: exact commands ('/blog brand init|show|update'), a sequenced 5-step interview with specific prompts per step, complete copy-paste-ready BRAND.md and VOICE.md templates, and concrete error-handling rules ('refuse to write skeletons', 'prompt for at least 2 audience bullets and 3 editorial rules'). Matches the anchor-5 'fully executable, copy-paste ready'.

5 / 5

Workflow Clarity

Clear multi-step sequence (5-step interview) with distinct show/update workflows and an explicit error-handling section that includes overwrite confirmation and minimal-answer validation. Falls below 5 because the destructive init/write path uses advisory confirmations rather than a true validate->fix->retry feedback loop with explicit checkpoints.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so all content is inline, but it is well-organized into clear, navigable sections with templates appropriately placed. Minor gaps (the two full templates could arguably be split into reference files) keep it just below the anchor-5 'clear overview with one-level-deep references'.

4 / 5

Total

17

/

20

Passed

Description

95%Weight 40%Scale 1-5

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

The description is strong: it explicitly states both what the skill produces and when to use it, with a rich set of natural trigger phrases and clear disambiguation from the related blog-persona skill. Its only weakness is mild verbosity in how the capabilities are phrased.

Suggestions

Tighten the capability statement into a crisper action list (e.g., 'Generates BRAND.md (audience, positioning, editorial rules, taboo phrases, competitor differentiation) and VOICE.md (persona JSON as readable prose)') to reach the lean, comprehensive form of the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and outputs — '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)' — giving comprehensive coverage of what each file contains. Falls just below a 5 because the actions are wrapped in long descriptive prose rather than the crisp action-list form of the anchor-5 example.

4 / 5

Completeness

Explicitly answers both what ('Generates BRAND.md ... and VOICE.md ... both written to the project root') and when ('Use when user says ...') with concrete trigger phrases, matching the anchor-5 example precisely.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases plus exact file names: 'Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog"'. Covers synonyms and file-extension-style tokens users would naturally say, matching the anchor-5 example.

5 / 5

Distinctiveness Conflict Risk

Clear niche tied to BRAND.md/VOICE.md and the blog-brand command, with explicit disambiguation ('Pairs with blog-persona, which manages the structured persona JSON') minimizing conflict risk. Matches the anchor-5 'clear niche with distinct triggers'.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
AgriciDaniel/claude-blog
Reviewed

Table of Contents

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.