storytelling-synthesizer by rysweet/amplihack
npx skills add https://github.com/rysweet/amplihack --skill storytelling-synthesizer将技术工作(拉取请求、提交历史、功能实现)转化为引人入胜的叙事,以引起不同受众的共鸣——无论是准备黑客松演示、撰写技术博客文章,还是创建营销内容。
每项技术工作都隐藏着一个叙事。合成器将其提取并放大:
问题 → 解决方案 → 影响 → 钩子
这反映了适用于技术工作的 英雄之旅 模式:
每个技术叙事都遵循以下经过验证的故事结构之一:
目的:面向现场观众的 5-10 分钟引人入胜的演示
结构:
开场钩子(30 秒)
├─ 用令人惊讶的统计数据或问题陈述抓住注意力
├─ 一句话定义问题
└─ 展示什么是坏的/慢的/令人沮丧的
背景与问题(1-2 分钟)
├─ 为什么这个问题重要
├─ 谁感受到了这种痛苦
├─ 问题的代价(时间、金钱、挫败感)
└─ 之前的尝试或变通方法
解决方案(2-3 分钟)
├─ 关键创新或洞察
├─ 带有具体、可衡量结果的现场演示
├─ 展示前后对比
└─ 突出“惊叹时刻”
影响与指标(1 分钟)
├─ 量化的结果(更快、更便宜、更容易)
├─ 实际应用
├─ 未来潜力
└─ 行动号召(下一步是什么)
结尾(30 秒)
├─ 强化核心信息
├─ 令人难忘的最终想法
└─ 邀请提问
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
目的:面向阅读受众的 1,500-3,000 字技术叙事
结构:
标题与钩子
├─ 带有悬念的引人注目的标题
└─ 回答“我为什么要读这个?”的开场段落
问题陈述(400-500 字)
├─ 展示问题的真实场景
├─ 技术细节:具体是什么出了问题
├─ 现状的代价
├─ 为什么现有解决方案不足
└─ 读者自我认同(“这就是我的问题”)
解决方案概述(300-400 字)
├─ 深入技术细节之前的高层次方法
├─ 核心创新或洞察
├─ 与替代方案有何不同
└─ 为什么选择这种方法
技术深度解析(600-800 字)
├─ 架构或实现细节
├─ 关键代码片段或图表
├─ 设计决策和权衡
├─ 性能特征
└─ 如何处理边缘情况
结果与验证(300-400 字)
├─ 证明成功的指标
├─ 前后对比
├─ 真实世界测试用例
├─ 性能基准
└─ 用户反馈或推荐
影响与未来工作(200-300 字)
├─ 这实现了什么
├─ 相关机会
├─ 路线图项目
└─ 对读者的行动号召
代码示例(如适用)
├─ 完整、可运行的示例
├─ 常见用例
├─ 展示错误处理
└─ 性能提示
结论(100-200 字)
├─ 强化主要收获
├─ 读者如何使用这个
├─ 邀请反馈和讨论
└─ 资源链接
目的:用于 20-45 分钟演讲或内部演示的结构化叙事
结构:
幻灯片 1:标题与钩子
├─ 带有悬念的挑衅性标题
├─ 演讲者姓名和资历
└─ 一句话前提
幻灯片 2-3:问题与背景(3-4 分钟)
├─ 相关的问题场景
├─ 当前挑战
├─ 为什么这很重要
└─ 范围和受众影响
幻灯片 4-6:解决方案架构(5-7 分钟)
├─ 可视化系统图
├─ 关键组件及其角色
├─ 技术创新点
└─ 设计理念
幻灯片 7-9:实现细节(5-7 分钟)
├─ 代码架构或工作流
├─ 关键算法或模式
├─ 权衡和做出的决策
└─ 集成点
幻灯片 10-11:演示或案例研究(5-10 分钟)
├─ 解决方案实际运行的现场演示(或视频)
├─ 真实世界结果和指标
├─ 与替代方案的比较
└─ 边缘情况或故障的处理
幻灯片 12-13:影响与指标(3-4 分钟)
├─ 量化的结果
├─ 业务或用户影响
├─ 采用率或使用指标
└─ 客户推荐(如果有)
幻灯片 14-15:未来与路线图(2-3 分钟)
├─ 下一步是什么
├─ 相关机会
├─ 行动号召或开放问题
└─ 听众如何贡献或采用
幻灯片 16:结尾
├─ 关键收获总结
├─ 联系方式和资源
└─ 邀请提问
目的:以客户为中心的描述,强调商业价值
结构:
标题
├─ 以结果为导向:“将处理时间减少 75%”
└─ 避免行话:使用客户语言
问题陈述
├─ 客户今天在挣扎什么
├─ 时间、金钱或挫败感的代价
└─ 为什么他们尝试了其他解决方案
之前场景
├─ 没有解决方案时的典型客户体验
├─ 具体的摩擦点
├─ 情感影响(挫败感、压力)
└─ 量化的痛苦(损失的时间、收入影响)
解决方案概述
├─ 我们的解决方案做什么(用客户语言)
├─ 关键好处(不是功能)
├─ 它如何简化他们的工作
└─ 典型的采用时间线
之后场景
├─ 使用解决方案后的典型体验
├─ 工作流程改进
├─ 时间/成本节省
└─ 情感好处(信心、速度)
社会证明
├─ 客户推荐
├─ 来自真实客户的量化结果
├─ 案例研究或成功故事
└─ 行业认可
行动号召
├─ 下一步(试用、了解更多、联系)
├─ 减少摩擦(免费试用、演示、文档)
└─ 成功承诺
分析技术工作以识别:
对于每项成果:
针对不同受众的不同叙事:
根据媒介选择合适的模板:
每个叙事都需要吸引注意力的元素:
开场钩子(在最初 30 秒内抓住注意力):
过渡(在部分之间保持参与度):
结尾钩子(令人难忘的最终想法):
通过以下方式使叙事具体化:
验证叙事:
输入:缓存优化功能的 PR 描述
输出:7 分钟演示脚本
钩子:“想象一下,如果每次用户交互都快 5 倍。这就是我们刚刚构建的。”
问题:用户在页面加载时经历 3-5 秒的延迟。我们最慢的操作是频繁访问数据的缓存未命中。我们尝试了传统解决方案,但在 10 万用户时遇到了扩展限制。
解决方案:我们实现了具有自动驱逐策略和实时失效的分布式内存缓存。现场演示显示相同操作从 3.2 秒降至 640 毫秒——快 5 倍。
指标:平均响应时间减少 47%,缓存命中率 92%,处理 50 万并发用户。用户报告体验显著加快。
结尾:这不仅仅是一个性能调整——它从根本上改变了我们系统的扩展方式。我们现在可以在不增加额外基础设施的情况下支持当前用户基数的 10 倍。
输入:实现身份验证功能的 15 次提交
输出:2,000 字博客文章大纲
标题:“构建零开销身份验证系统:我们如何将身份验证延迟减少 80%”
问题:每个 API 请求都需要身份验证验证。现有解决方案为每个请求增加 200 毫秒。在规模上,这成为我们的主要瓶颈。我们需要一种轻量级的解决方案,能够扩展到每秒数百万次请求。
解决方案:验证结果的进程内缓存与后台刷新。基于用户生命周期事件的智能失效。结果:每次身份验证检查 25 毫秒,改进 92%。
深度解析:JWT 解析优化、缓存策略、失效机制、安全考虑。
结果:生产指标显示延迟减少 78%,零次身份验证相关中断,无性能回归。
代码示例:[完整工作示例]
未来:事件驱动失效、联合身份验证支持、多租户隔离。
输入:简化 API 设计的技术规格
输出:以客户为中心的价值主张
标题:“更快集成,减少中断:我们的新简化 API”
问题:开发人员花费 40% 的集成时间仅仅是为了理解我们的 API。一个错误的参数会导致神秘的错误。更新需要完全重构。
之前:复杂的 200 参数 API,50 页文档,典型用例集成时间线为 2-3 周。
之后:具有合理默认值的直观设计。10 参数快速入门路径涵盖 90% 的用例。大多数集成在 2-3 小时内完成。
结果:5 个主要客户报告集成速度提高 75%。支持工单减少 60%。新客户入职时间从几天减少到几小时。
行动号召:“免费试用 30 天。无需信用卡。”
输入:新的微服务架构技术设计
输出:30 分钟演示大纲
有效的技术叙事通常遵循经过验证的模式:
问题被认为是不可能或需要大量资源。巧妙的解决方案显示出令人惊讶的简单性和优雅性。
从探索到实现的旅程。听众与讲故事者一起发现洞察。创造参与感和学习。
清晰的前后对比显示戏剧性的改进。强调变化的范围和影响。适用于演示和营销。
从简单开始,逐步增加复杂性。展示解决方案如何从基本扩展到复杂。建立理解信心。
传统智慧建议一种方法。技术工作揭示了更好的方式。创造智力兴趣并展示思想领导力。
令人惊讶的性能提升: “我们将响应时间从 5 秒减少到 50 毫秒——100 倍的改进。”
优雅的简单性: “整个解决方案只有 200 行代码,却能处理每秒数百万次请求。”
新颖的洞察: “我们意识到问题不在于算法——而是我们问错了问题。”
扩展成就: “无需架构更改即可从 1 个用户扩展到 1 亿用户。”
可靠性里程碑: “生产第一周:零事故,尽管流量激增 10 倍,仍保持 99.99% 的正常运行时间。”
优雅成就: “在增加 5 倍功能的同时,将代码库减少了 40%。”
| 来源 | 目标 | 重点 |
|---|---|---|
| PR 描述 | 演示脚本 | 参与度、现场展示 |
| 提交信息 | 博客文章 | 深度解释、学习 |
| 测试用例 | 用例示例 | 实际应用 |
| 指标 | 标题统计数据 | 业务影响 |
| 架构图 | 演示幻灯片 | 视觉解释 |
| 错误日志 | 故障场景故事 | 问题验证 |
| 功能标志 | 推出叙事 | 受控创新 |
| 代码注释 | 博客部分 | 设计原理 |
合成叙事后,验证:
陷阱 1:技术细节过多
陷阱 2:没有清晰的问题陈述
陷阱 3:缺少指标或影响
陷阱 4:错误的受众调整
陷阱 5:结尾薄弱
陷阱 6:节奏问题
此技能将任何技术输出视为原材料:
此技能生成以下即用型叙事:
此技能体现关键原则:
一个合成良好的叙事:
此技能应根据反馈改进:
记录学习并与社区分享。
每周安装量
160
代码仓库
GitHub 星标
39
首次出现
2026 年 1 月 23 日
安全审计
安装于
opencode149
codex141
cursor139
gemini-cli139
github-copilot134
claude-code130
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.
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:
Every technical narrative follows one of these proven story structures:
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
The Solution (2-3 minutes)
├─ Key innovation or insight
├─ Live demo with specific, measurable results
├─ Show before/after comparison
└─ Highlight the "wow moment"
Impact & Metrics (1 minute)
├─ Quantified results (faster, cheaper, easier)
├─ Real-world application
├─ Future potential
└─ Call to action (what's next)
Closing (30 seconds)
├─ Reinforce core message
├─ Memorable final thought
└─ Invite questions
Purpose : 1,500-3,000 word technical narrative for written audience
Structure :
Title & Hook
├─ Compelling headline with intrigue
└─ Opening paragraph that answers "why should I read this?"
Problem Statement (400-500 words)
├─ Real-world scenario showing the problem
├─ Technical detail: what specifically breaks
├─ Cost of the status quo
├─ Why existing solutions fall short
└─ Reader self-recognition ("this is my problem")
Solution Overview (300-400 words)
├─ High-level approach before technical dive
├─ Core innovation or insight
├─ How it differs from alternatives
└─ Why this approach was chosen
Technical Deep Dive (600-800 words)
├─ Architecture or implementation details
├─ Key code snippets or diagrams
├─ Design decisions and tradeoffs
├─ Performance characteristics
└─ How it handles edge cases
Results & Validation (300-400 words)
├─ Metrics demonstrating success
├─ Before/after comparison
├─ Real-world test cases
├─ Performance benchmarks
└─ User feedback or testimonials
Implications & Future Work (200-300 words)
├─ What this enables
├─ Related opportunities
├─ Roadmap items
└─ Call to action for readers
Code Example (if applicable)
├─ Complete, runnable example
├─ Common use cases
├─ Error handling shown
└─ Performance tips
Conclusion (100-200 words)
├─ Reinforce main takeaway
├─ How readers can use this
├─ Invite feedback and discussion
└─ Links to resources
Purpose : Structured narrative for 20-45 minute talk or internal presentation
Structure :
Slide 1: Title & Hook
├─ Provocative title with intrigue
├─ Speaker name and credentials
└─ One-sentence premise
Slides 2-3: Problem & Context (3-4 minutes)
├─ Relatable problem scenario
├─ Current challenges
├─ Why this matters
└─ Scope and audience impact
Slides 4-6: Solution Architecture (5-7 minutes)
├─ Visual system diagram
├─ Key components and their roles
├─ Technical innovation points
└─ Design philosophy
Slides 7-9: Implementation Details (5-7 minutes)
├─ Code architecture or workflows
├─ Key algorithms or patterns
├─ Tradeoffs and decisions made
└─ Integration points
Slides 10-11: Demo or Case Study (5-10 minutes)
├─ Live demonstration (or video) of solution in action
├─ Real-world results and metrics
├─ Comparison to alternatives
└─ Handling of edge cases or failures
Slides 12-13: Impact & Metrics (3-4 minutes)
├─ Quantified results
├─ Business or user impact
├─ Adoption or usage metrics
└─ Customer testimonials (if available)
Slides 14-15: Future & Roadmap (2-3 minutes)
├─ What's next
├─ Related opportunities
├─ Call to action or open problems
└─ How audience can contribute or adopt
Slide 16: Closing
├─ Key takeaway summary
├─ Contact and resources
└─ Invite questions
Purpose : Customer-focused description emphasizing business value
Structure :
Headline
├─ Outcome-focused: "Reduce Processing Time by 75%"
└─ Avoid jargon: use customer language
Problem Statement
├─ What customers struggle with TODAY
├─ Cost in time, money, or frustration
└─ Why they tried other solutions
Before Scenario
├─ Typical customer experience without solution
├─ Specific friction points
├─ Emotional impact (frustration, stress)
└─ Quantified pain (hours lost, revenue impact)
Solution Overview
├─ What our solution does (in customer language)
├─ Key benefits (not features)
├─ How it simplifies their work
└─ Typical adoption timeline
After Scenario
├─ Typical experience with solution
├─ Workflow improvements
├─ Time/cost savings
└─ Emotional benefits (confidence, speed)
Social Proof
├─ Customer testimonials
├─ Quantified results from real customers
├─ Case studies or success stories
└─ Industry recognition
Call to Action
├─ Next step (try it, learn more, contact)
├─ Reduce friction (free trial, demo, docs)
└─ Success promise
Analyze the technical work to identify:
For each achievement:
Different narratives for different audiences:
Choose the appropriate template based on medium:
Every narrative needs attention-grabbing elements:
Opening Hooks (grab attention in first 30 seconds):
Transitions (maintain engagement between sections):
Closing Hooks (memorable final thought):
Make narratives tangible with:
Verify the narrative:
Input : PR description for caching optimization feature
Output : 7-minute demo script
Hook: "Imagine if every user interaction was 5x faster. That's what we just built."
Problem: Users experience 3-5 second delays on page loads. Our slowest operations
are cache misses on frequently accessed data. We've tried traditional solutions
but hit scaling limits at 100k users.
Solution: We implemented a distributed memory cache with automatic eviction policies
and real-time invalidation. Live demo shows the same operation dropping from 3.2s
to 640ms—5x faster.
Metrics: 47% reduction in average response time, 92% cache hit rate, handles 500k
concurrent users. Users report significantly faster experience.
Closing: This isn't just a performance tweak—it fundamentally changes how our
system scales. We can now support 10x our current user base without additional
infrastructure.
Input : 15 commits implementing authentication feature
Output : 2,000-word blog post outline
Title: "Building a Zero-Overhead Authentication System: How We Reduced Auth
Latency by 80%"
Problem: Every API request requires auth validation. Existing solutions add 200ms
per request. At scale, this becomes our primary bottleneck. We needed something
lightweight that scales to millions of requests/second.
Solution: In-process caching of validation results with background refresh. Smart
invalidation based on user lifecycle events. Result: 25ms per auth check, 92%
improvement.
Deep Dive: JWT parsing optimizations, caching strategy, invalidation mechanics,
security considerations.
Results: Production metrics show 78% latency reduction, zero auth-related outages,
no performance regression.
Code Example: [Complete working example]
Future: Event-driven invalidation, federated auth support, multi-tenant isolation.
Input : Technical specs for simplified API design
Output : Customer-focused value proposition
Headline: "Integrate Faster, Break Less: Our New Simplified API"
Problem: Developers spend 40% of integration time just understanding our API.
One wrong parameter causes cryptic errors. Updates require full refactoring.
Before: Complex 200-parameter API, 50-page documentation, integration timeline
of 2-3 weeks for typical use case.
After: Intuitive design with sensible defaults. 10-parameter quick-start path
covers 90% of use cases. Most integrations complete in 2-3 hours.
Results: 5 major customers report 75% faster integration. Support tickets
cut by 60%. New customer onboarding time reduced from days to hours.
CTA: "Try it free for 30 days. No credit card required."
Input : New microservices architecture technical design
Output : 30-minute presentation outline
Slides 1-2: The problem with our monolithic system (scaling limits, deployment friction)
Slides 3-4: System architecture overview (visual diagram, service boundaries)
Slides 5-7: Key innovations (async messaging, service discovery, circuit breakers)
Slides 8-10: Live demo of deployment, scaling, monitoring
Slides 11-12: Results (10x scaling capacity, 60% faster deployments, zero incidents)
Slides 13-14: Roadmap (service mesh, tracing, multi-region)
Slide 15: Closing (technical excellence enables business velocity)
Effective technical narratives often follow proven patterns:
Problem is perceived as impossible or requiring massive resources. Clever solution shows surprising simplicity and elegance.
Journey from exploration to realization. Audience discovers insight alongside the storyteller. Creates engagement and learning.
Clear before/after showing dramatic improvement. Emphasizes scope of change and impact. Works well for demos and marketing.
Start simple, progressively add complexity. Shows how solution scales from basic to sophisticated. Builds confidence in understanding.
Conventional wisdom suggests one approach. Technical work reveals better way. Creates intellectual interest and demonstrates thought leadership.
Surprising Performance Gains: "We cut response time from 5 seconds to 50 milliseconds—a 100x improvement."
Weekly Installs
160
Repository
GitHub Stars
39
First Seen
Jan 23, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode149
codex141
cursor139
gemini-cli139
github-copilot134
claude-code130
Python PDF处理教程:合并拆分、提取文本表格、创建PDF文件
65,000 周安装
Elegant Simplicity: "The entire solution is 200 lines of code, yet handles millions of requests/sec."
Novel Insight: "We realized the problem wasn't the algorithm—it was that we were asking the wrong question."
Scaling Achievement: "Scales from 1 user to 100 million users without architectural change."
Reliability Milestone: "First week in production: zero incidents, 99.99% uptime despite 10x traffic spike."
Elegance Achievement: "Reduced codebase by 40% while adding 5x more functionality."
| Source | Target | Focus |
|---|---|---|
| PR description | Demo script | Engagement, live showing |
| Commit messages | Blog post | Deep explanation, learning |
| Test cases | Use case examples | Practical application |
| Metrics | Headline statistics | Business impact |
| Architectural diagram | Presentation slide | Visual explanation |
| Error logs | Failure scenario story | Problem validation |
| Feature flags | Rollout narrative | Controlled innovation |
| Code comments | Blog section | Design rationale |
After synthesizing a narrative, verify:
Pitfall 1: Too Much Technical Detail
Pitfall 2: No Clear Problem Statement
Pitfall 3: Missing Metrics or Impact
Pitfall 4: Wrong Audience Adaptation
Pitfall 5: Weak Closing
Pitfall 6: Pacing Issues
This skill treats any technical output as raw material:
The skill produces ready-to-use narratives in:
This skill embodies key principles:
A well-synthesized narrative:
This skill should improve based on feedback:
Document learnings and share with the community.