CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

made-to-stick

Craft messages that are understood, remembered, and drive action using the SUCCESs checklist (Simple, Unexpected, Concrete, Credible, Emotional, Stories). Use when the user mentions "make it memorable", "sticky messaging", "tagline", "value proposition", "why the message isnt landing", "knowledge curse", "surprise gap", or "concrete language". Also trigger when writing pitch decks, simplifying complex product explanations, or making presentations more compelling and memorable. For narrative brand frameworks, see storybrand-messaging. For viral sharing, see contagious.

Quality

82%

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

61%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-organized, example-rich body with genuinely useful operational tools (audit table, diagnostic, scoring bands) and a real, properly linked one-level-deep reference bundle. Its weaknesses are verbosity — it re-teaches the well-known SUCCESs framework and duplicates reference content — and an ambiguous evaluation workflow built around two unreconciled scoring systems.

Suggestions

Trim each of the six principle sections to a brief summary (core concept plus one or two examples) and push the detailed techniques and tables into the existing reference files — Claude already knows the Made to Stick framework, so the body only needs the operational application.

Reconcile the two scoring systems into one explicit numbered workflow (audit each principle → compute score → identify gaps → provide improvements to reach 10/10), since the current 0-10 overall score and the 50-60 audit sum are presented without explanation of how they relate.

Remove the duplicated "Applying SUCCESs to Product" and "The Curse of Knowledge" sections in favor of short pointers to applications.md and curse-of-knowledge.md, keeping the body focused on the audit-and-improve procedure.

DimensionReasoningScore

Conciseness

The style is dense and table-driven with no padded prose, but it re-explains at length a framework Claude already knows well (Commander's Intent, Velcro theory, Sinatra Test, the Mother Teresa principle are all from a famous bestselling book) and duplicates material that also lives in the reference files (each principle section, "Applying SUCCESs to Product" vs applications.md, "The Curse of Knowledge" vs curse-of-knowledge.md). Mostly efficient but could be tightened considerably.

3 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: a scoring directive ("rate 0-10... Always provide current score and improvements to reach 10/10"), before/after transformation tables, a per-principle audit table with scoring bands, and an if-no→action diagnostic. Falls short of a 5 only because the pieces are never assembled into one worked example of the audit applied to a real message.

4 / 5

Workflow Clarity

The evaluation procedure exists (audit table → score → band; diagnostic with corrective actions), but the sequence is implicit and scattered across sections, and two competing scoring systems appear without reconciliation — a 0-10 overall score in the Scoring section vs a six-principle 1-10 audit summing to 60. Checkpoints are missing or implicit rather than explicit.

3 / 5

Progressive Disclosure

All nine referenced files exist, are one level deep, clearly listed with descriptions in a Reference Files section, and linked from each principle section — good structure and easy navigation. Not a 5 because the split is not clean: the body inlines substantial detail that is also expanded in the references (principle sections, applications, curse of knowledge).

4 / 5

Total

14

/

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.

A strong description: third-person voice, explicit what-and-when structure, rich natural trigger phrases, and proactive boundary guidance against neighboring messaging skills. The only slack is that the capability statement compresses into one verb plus outcomes rather than enumerating several distinct concrete actions.

DimensionReasoningScore

Specificity

Names the domain, the outcome goals ("understood, remembered, and drive action"), and the full six-part SUCCESs framework by name. It rests on a single action verb ("craft") plus outcomes rather than the multiple distinct concrete actions of the top anchor, so it sits just below a 5.

4 / 5

Completeness

Explicitly answers both questions: the "what" ("Craft messages that are understood, remembered, and drive action using the SUCCESs checklist") and the "when" ("Use when the user mentions..." and "Also trigger when...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-language triggers users would actually say ("make it memorable", "sticky messaging", "why the message isnt landing", "tagline", "knowledge curse") plus task contexts (pitch decks, simplifying product explanations, presentations), covering synonyms and colloquial phrasing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (SUCCESs sticky-messaging) with explicit disambiguation of the two nearest sibling skills ("For narrative brand frameworks, see storybrand-messaging. For viral sharing, see contagious."), leaving only minor overlap through broad terms like "value proposition".

5 / 5

Total

19

/

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/made-to-stick/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.