CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 loads these files, fenced as untrusted data, for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when the user says "blog brand", "create brand context", "BRAND.md", "VOICE.md", "establish editorial brand". Not for learning a voice from existing posts (blog-style) or managing persona JSON (blog-persona).

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A well-executed instruction-type skill body: fully specified interview flow, copy-paste output templates, explicit confirmation/backup validation before overwriting files, and a dedicated error-handling section. The two weaker spots are minor: some rationale padding (Why this exists, persona comparison table) and a nested indirection for resolving the untrusted-load helper path. No dimension falls below 4.

DimensionReasoningScore

Conciseness

The body is dominated by directly actionable material (exact interview questions, full output templates, numbered workflows, error handling), but the "Why this exists" section and the blog-persona comparison table provide rationale/background that could be trimmed. It is not 3 because only minor instances of over-explanation exist, and not 5 because that background padding does not fully earn its tokens.

4 / 5

Actionability

Complete copy-paste-ready markdown templates for both output files (BRAND.md and VOICE.md), a command table, exact per-step interview questions, and concrete error-handling directives ("prompt for at least 2 audience bullets and 3 editorial rules; refuse to write skeletons"). As an instruction-only skill its guidance is fully executable across the common cases; not 4 because there are no meaningful gaps.

5 / 5

Workflow Clarity

The init interview is explicitly sequenced ("Ask each step, wait for response, then proceed"), show is a numbered 3-step procedure, and the update workflow includes explicit validation for the destructive overwrite case: "show a diff of each file against the current contents and ask for confirmation before overwriting" plus .bak backup. Error Handling adds recovery paths for edge cases. Not 4 because checkpoints for the risky operation are explicit, not implicit.

5 / 5

Progressive Disclosure

Sections are well-organized (Commands, Init Workflow, Output Files, Show, Update, Integration, Error Handling) and the main reference is clearly signaled ("Read the main reference orchestration-details.md before loading project context"). It is not 5 because ~100 lines of output templates are inlined and the helper path requires a second-level indirection ("resolved as documented in the blog skill section 'Auto-loaded Project-Root Context'"); not 3 because structure is good and references are clearly signaled, not buried.

4 / 5

Total

18

/

20

Passed

Description

92%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.

A strong description: third-person voice, concrete deliverables enumerated, explicit use-when triggers in the user's own vocabulary, and explicit negative boundaries against the two adjacent skills (blog-style, blog-persona). The only gap is a few missing natural synonyms in the trigger list. All weighted dimensions land at or near the top anchors.

DimensionReasoningScore

Specificity

"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" lists multiple specific concrete actions with the deliverables' contents enumerated. It is not 4 because coverage of the skill's function is comprehensive rather than having minor gaps.

5 / 5

Completeness

The description explicitly answers both what ("Generates BRAND.md ... and VOICE.md ... written to the project root", including how the orchestrator consumes them) and when ("Use when the user says \"blog brand\" ... \"establish editorial brand\"") with concrete trigger phrases. This matches the top anchor exactly; the when-clause is explicit, not merely present.

5 / 5

Trigger Term Quality

The quoted triggers — "blog brand", "create brand context", "BRAND.md", "VOICE.md", "establish editorial brand" — are natural phrases a user would say. It is not 5 because a few natural synonyms (e.g. "brand voice", "editorial guidelines") are missing; not 3 because multiple natural, user-sayable trigger phrases are explicitly present.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche and explicitly disambiguates sibling skills: "Pairs with blog-persona, which manages the structured persona JSON" and "Not for learning a voice from existing posts (blog-style) or managing persona JSON (blog-persona)". Conflict risk is minimal; not 4 because the boundary is explicitly stated rather than merely implied.

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.

Validation — 15 / 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

Path

skills/blog-brand/SKILL.md

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.