Crafts product narratives using Andy Raskin's strategic narrative structure and Nancy Duarte's presentation frameworks. Use when writing pitches, creating presentations, framing features as stories, or building compelling product narratives.
npx skills add https://github.com/menkesu/awesome-pm-skills --skill strategic-storytelling
Claude uses this skill when:
Five-Act Structure:
Example:
# Pitch: [Product]
## Act 1: Old World
"For years, teams coordinated through email..."
## Act 2: Insight
"But remote work changed everything. What worked in office doesn't work distributed."
## Act 3: New World
"Now, the best teams coordinate in real-time, asynchronously..."
## Act 4: Stakes
"Companies that figure this out will attract best talent and move faster. Those that don't will lose to competitors."
## Act 5: Your Role
"That's where [Product] comes in. We help teams..."
# [Product Name]: [Tagline]
## The Old World (Problem)
[How things used to work, pain points]
## The Insight (Why Now)
[What changed that makes this possible/necessary now]
## The New World (Vision)
[What's now possible, the opportunity]
## The Stakes (Urgency)
[Win big or lose - why this matters]
## Our Solution (Product)
[How we help you win in the new world]
## Proof
- [Metric/testimonial]
- [Metric/testimonial]
## Next Steps
[Clear call to action]
Structure:
Delivery:
Andy Raskin:
> "The best product stories make the customer the hero, not your product."
Nancy Duarte:
> "The audience doesn't need to tune themselves to you—you need to tune your message to them."
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take menkesu/strategic-storytelling from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.