storytelling-synthesizer

Convert technical work into narratives using a Problem to Hook storytelling model.

2|22|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/rysweet/azlin --skill storytelling-synthesizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: storytelling-synthesizer
Source: https://github.com/rysweet/azlin/tree/main/.claude/skills/storytelling-synthesizer
Command: npx skills add https://github.com/rysweet/azlin --skill storytelling-synthesizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns code changes, PRs, or features into persuasive narratives for demos, blogs, presentations, or marketing.

Core Features & Use Cases

  • Demo scripts, blog outlines, presentations, and marketing copy
  • Problem → Solution → Impact → Hook storytelling template
  • Audience adaptations for engineers, PMs, execs, users, and marketers

Quick Start

Claude, turn this PR into a 7-minute demo script: [paste PR description].

Frequently Asked Questions about storytelling-synthesizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a pull request into a compelling demo script?

This Skill converts PR descriptions into structured demo scripts by applying a Problem → Solution → Impact → Hook storytelling model. Paste your PR details and specify the format (demo script, blog outline, presentation, or marketing copy) and target audience—engineers, PMs, execs, users, or marketers—and the Skill adapts the narrative accordingly.

Can I use storytelling techniques to make technical features more persuasive?

Yes. The Skill transforms technical work—code changes, commit histories, and feature implementations—into persuasive narratives by structuring them around problem, solution, impact, and hook. This works across demos, blogs, presentations, and marketing content to engage different audiences.

What's the best way to adapt technical narratives for different audiences?

The Skill enforces audience-specific adaptations for engineers, product managers, executives, end users, and marketers. Submit your technical content and specify the target audience; the Skill reshapes the narrative's focus, language, and emphasis to match what that audience cares about most.

How does the Problem → Solution → Impact → Hook framework improve storytelling?

This framework structures narratives so each section answers a specific question: What problem exists? How does this fix it? What changes as a result? Why should the audience care now? This sequence builds logical flow and emotional resonance, making technical work memorable and actionable.

Can I generate multiple content formats from a single technical implementation?

Yes. The Skill outputs multiple formats—demo scripts, blog outlines, presentation outlines, and marketing copy—from the same source material (PR, commit history, or feature description). Each format reshapes the narrative for its medium while keeping the core story intact.

What input do I need to create a compelling narrative from my work?

Provide PR descriptions, commit histories, or feature implementation details. The Skill works with existing technical documentation; no special preparation is required. Specify your desired output format and target audience to receive a structured narrative ready for demos, blogs, presentations, or marketing.