CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

storybrand-messaging

Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "messaging isnt resonating", "brand script", "StoryBrand framework", or "customer as hero". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.

Quality

86%

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

75%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-structured instructional skill with excellent concrete patterns, tables, and a working diagnostic/scoring loop, supported by a clean one-level-deep reference bundle. Its main cost is token weight: expository "Why it works" sections, an author bio, and an affiliate reading link inflate the body without improving execution.

Suggestions

Trim or remove the seven "Why it works" paragraphs, the "About the Author" section, and the affiliate-linked "Further Reading" section — they re-explain concepts Claude already knows and consume roughly 20% of the body without improving execution.

Consolidate the one-liner material: keep only the formula and a single example in SKILL.md and defer the rest to references/one-liners.md, removing the duplication between the body section and the reference file.

Replace the four repeated "See: references/brand-script.md" pointers with a single clearly-signaled link (e.g., in the Reference Files index) and add one explicit end-to-end sequence for creating messaging (e.g., 1. Define hero and desire → 2. Fill brand script worksheet → 3. Run Quick Diagnostic → 4. Score to 10/10) to make the workflow fully explicit.

DimensionReasoningScore

Conciseness

The Key insights, copy patterns, and application tables earn their tokens, but roughly a fifth of the body is unnecessary: seven "Why it works" paragraphs re-explain psychology Claude already knows (e.g., "Humans are loss-averse"), and the promotional "About the Author" and affiliate-linked "Further Reading" sections add no execution value. Not 2 because the bulk is dense, actionable framework content rather than generic padding.

3 / 5

Actionability

Highly concrete guidance for an instruction-only skill: copy-pattern templates ("You want [specific desire]..."), a one-liner formula with two worked examples, context/application/example tables for every element, a mistakes table with fixes, and a 7-question diagnostic. These are copy-paste-ready patterns covering the common cases, matching the top anchor.

5 / 5

Workflow Clarity

The SB7 elements are sequenced 1–7, the Scoring section defines an explicit feedback loop ("rate it 0-10... Always provide the current score and specific improvements needed to reach 10/10"), and the Quick Diagnostic provides a checklist. Not 5 because the creation workflow's step order is implicit in section arrangement and delegates to references rather than stating one explicit validated sequence.

4 / 5

Progressive Disclosure

All six referenced files exist, are one level deep, and are clearly signaled with a descriptive "Reference Files" index — matching good bundle structure. Minor gaps keep it from 5: the same brand-script.md pointer is repeated in four element sections, and the one-liner formula and examples are inlined in the body while also living in one-liners.md.

4 / 5

Total

16

/

20

Passed

Description

91%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: explicit what-and-when structure with unusually thorough natural trigger phrases and proactive disambiguation from sibling skills. The only weaknesses are a slightly umbrella-style capability statement and some overlap risk on generic copywriting terms.

DimensionReasoningScore

Specificity

Names the domain and several specific actions — "Clarify brand messaging using narrative structure that positions the customer as hero", "rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral" — with minor coverage gaps. It falls short of 5 because the core 'what' is a single umbrella action rather than a comprehensive list of concrete capabilities.

4 / 5

Completeness

Clearly answers both 'what' ("Clarify brand messaging using narrative structure that positions the customer as hero") and 'when' with an explicit "Use when the user mentions..." clause listing concrete trigger phrases, mirroring the anchor example's pattern exactly. Not 4 because the 'when' is fully explicit with concrete triggers rather than merely present.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms and colloquial variants: "brand message", "website copy", "elevator pitch", "one-liner", "messaging isnt resonating", "brand script", "StoryBrand framework", "customer as hero". This matches the comprehensive-coverage anchor; only marginal terms like "tagline" or "slogan" are absent, which does not drop it to 4.

5 / 5

Distinctiveness Conflict Risk

Explicit deferral pointers ("For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome") reduce sibling-skill conflict and the StoryBrand-specific triggers carve a clear niche. However, "website copy" and "landing page copy" retain moderate overlap risk with general copywriting skills, keeping it below 5.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

valeriibeck-star/claude-skills

Path

skills/storybrand-messaging/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.