Converts technical work into compelling narratives for demos, blog posts, or presentations. Use when preparing hackathon demos, writing technical blog posts, or creating marketing content. Transforms: PR descriptions, commit histories, feature implementations into structured stories. Formats: demo scripts, blog posts, presentation outlines, marketing copy.
View on GitHub.claude/skills/storytelling-synthesizer/SKILL.md
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/rysweet/amplihack/blob/main/.claude/skills/storytelling-synthesizer/SKILL.md -a claude-code --skill storytelling-synthesizerInstallation paths:
.claude/skills/storytelling-synthesizer/# Storytelling Synthesizer Skill ## Purpose Transform technical work (pull requests, commit histories, feature implementations) into compelling narratives that resonate with different audiences—whether preparing hackathon demos, writing technical blog posts, or creating marketing content. ## When to Use This Skill - **Hackathon Demos**: Convert technical achievements into engaging 5-10 minute presentations - **Technical Blog Posts**: Transform PR descriptions into detailed, narrative-driven articles - **Marketing Content**: Distill complex features into customer-focused value propositions - **Presentation Outlines**: Create structured narratives for conference talks or internal presentations - **Release Notes**: Convert commit histories into user-friendly announcements - **Investor Pitches**: Frame technical work as business value and impact - **Team Communications**: Share accomplishments in compelling, non-technical ways ## Core Philosophy: Story Structure Every technical work has a narrative hidden within it. The synthesizer extracts and amplifies it: **Problem → Solution → Impact → Hook** This mirrors the **Hero's Journey** pattern adapted for technical work: - **Problem**: The challenge that motivated the work (conflict) - **Solution**: How the technical work addresses it (resolution) - **Impact**: What changes because of this work (outcome) - **Hook**: The compelling angle that captures attention (why it matters) ## Narrative Templates Every technical narrative follows one of these proven story structures: ### 1. Demo Script Template **Purpose**: 5-10 minute engaging presentation for live audience **Structure**: ``` Opening Hook (30 seconds) ├─ Grab attention with surprising stat or problem statement ├─ One-sentence problem definition └─ Show what's broken/slow/frustrating Context & Problem (1-2 minutes) ├─ Why this problem matters ├─ Who experiences the pain ├─ Cost of the problem (time, money, frustration) └─ Previous attempts or workarounds