Conciseness

The core sections (What It Is / When to Use / When Not to Use) are tight, but "Domain Context" ("a proven product management framework... combines best practices from industry leaders") and "Input Requirements" are generic boilerplate that adds no actionable information. Not score 4 because those two sections are pure padding; not score 2 because the substance of the skill is efficiently written.

Actionability

The body explains the concept and the reframing shift ("Move from 'Here's your problem, here's our solution' to 'The world has changed...'") but gives no steps, template, or worked example for actually constructing a narrative. Not score 1 because the reframe instruction and the old-game/new-game framing are concrete direction; not score 3 because there is no process a user could follow to produce a deck or pitch from this skill.

Workflow Clarity

There is no sequenced process at all — no steps for moving from product context to finished narrative, and no checkpoints. Not score 1 because the When to Use / When Not to Use sections give coherent decision guidance for where the skill applies; not score 3 because even a rough sequence for crafting the narrative (e.g. name the change → winners/losers → promised land → gift → proof) is missing.

Progressive Disclosure

The body is short (~54 lines) with clean, well-labeled sections and no bundle files, so no external-reference structure is needed. Not score 5 because it slightly exceeds the under-50-line simple-skill threshold and the depth needed to make this actionable (framework steps, example narratives) is absent rather than split into a reference file.

Specificity

The description names the domain and 1-2 actions ("Helps craft compelling narratives", "transforms pitches from feature lists into stories about change") but the actions are high-level; it never lists concrete deliverables like building sales decks or rewriting positioning. Not score 4 because several specific actions are absent; not score 2 because the pitch-transformation action is concrete and domain-specific.

Completeness

Both parts are present: an explicit "Use when asked to..." clause with concrete trigger phrases (when) and a "what" statement ("Helps craft compelling narratives that define movements rather than just selling products"). Not score 5 because the "what" leans abstract — "compelling narratives" gestures at capability without naming the concrete outputs it produces.

Trigger Term Quality

Trigger phrases are natural and varied ("strategic narrative", "Andy Raskin", "tell our company story", "write a pitch deck", "explain why customers should care", "movement narrative"). Not score 5 because common variations like "sales deck", "positioning", "company pitch", or "elevator pitch" are missing.

Distinctiveness Conflict Risk

Triggers like "Andy Raskin", "strategic narrative", and "movement narrative" carve a clear niche with minimal conflict. Not score 5 because "write a pitch deck" and "tell our company story" would also naturally trigger generic presentation or storytelling skills.