communication-storytelling by lyndonkl/claude
npx skills add https://github.com/lyndonkl/claude --skill communication-storytelling将复杂的信息、分析或数据转化为针对特定受众的清晰、有说服力的叙述。此技巧帮助您构建引人入胜的故事,包含强有力的标题、关键支持论点和具体证据,以推动理解和行动。
在以下情况下使用此技巧:
受众翻译:
高风险沟通:
叙事构建:
当用户说:
沟通叙事使用结构化方法来创建能够告知、说服和激励行动的叙述。核心框架包括:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
快速示例:
糟糕的(数据堆砌): "我们第二季度收入为 230 万美元,高于第一季度的 180 万美元。客户数量从 450 增加到 520。流失率从 5% 降至 3.2%。NPS 从 42 提高到 58。我们推出了 3 个新功能..."
良好的(叙事): "我们已经达到了产品市场契合度。三个信号证明了这一点:(1) 收入增长了 28%,而销售能力保持不变——客户在主动拉取我们的产品,而不是相反。(2) 流失率下降了 36%,因为我们专注于高级用户,我们顶级细分市场的月流失率现在为 1%。(3) NPS 跃升了 16 点至 58,客户特别赞扬了我们押注的三个功能。建议:通过高级层级加倍投入高级用户细分市场。"
复制此清单并跟踪您的进度:
Communication Storytelling Progress:
- [ ] Step 1: Gather inputs and clarify audience
- [ ] Step 2: Choose appropriate narrative structure
- [ ] Step 3: Craft the narrative
- [ ] Step 4: Validate quality and clarity
- [ ] Step 5: Deliver and adapt
步骤 1:收集输入并明确受众
向用户询问信息(要传达的分析、数据、信息)、受众(谁会接收此信息)、目的(告知、说服、激励、建立信任)、背景(情况、风险、限制)和语气(正式、随意、紧急、庆祝)。深入了解受众至关重要——他们的专业水平、关注点、决策权限和时间限制决定了所有方面。有关输入问题,请参见 resources/template.md。
步骤 2:选择合适的叙事结构
对于标准沟通(公告、更新、演示)→ 使用 resources/template.md 快速模板。 对于需要不同版本的复杂多利益相关者沟通 → 学习 resources/methodology.md 中的受众细分和叙事改编技巧。 想了解优秀示例 → 查看 resources/examples/。
步骤 3:构建叙事
创建 communication-storytelling.md,包含:(1) 用一句话抓住本质的引人注目的标题,(2) 按逻辑流程(时间顺序、问题-解决方案、重要性排序)排列的 3-5 个关键点,(3) 每个论点的具体证据(数据、示例、引述、故事),(4) 明确说明受众下一步应做什么的行动号召。使用叙事技巧:具体性优于概括性,展示而非告知,人类故事优于抽象概念,紧张/解决弧线。有关叙事模式,请参见故事结构。
步骤 4:验证质量和清晰度
使用 resources/evaluators/rubric_communication_storytelling.json 进行自我评估。检查:标题是否清晰有力,关键点是否明确且得到充分支持,证据是否具体且相关,流程是否合乎逻辑,语气是否与受众匹配,行话是否适合专业水平,行动号召是否清晰可实现,长度是否符合时间限制。大声朗读以测试清晰度。用"那又怎样?"问题测试——每个论点是否回答了受众为何要在乎?最低标准:交付前平均得分 ≥ 3.5。
步骤 5:交付并调整
展示完成的 communication-storytelling.md 文件。强调叙事如何解决受众的关键关切。注意所使用的叙事技巧(数据人性化、紧张-解决、具体性)。如果用户有反馈或需要为不同受众进行调整,请使用 resources/methodology.md 中的多版本策略。
使用时机: 重大变革、战略转向、克服挑战
结构:
示例: "我们年增长率为 20%,但月流失率为 10%——不可持续。数据显示我们为错误的用户解决了错误的问题。我们在 3 个月内测试了 5 个假设,失败了 4 个。唯一奏效的是:专注于愿意支付 5 倍费用的高级用户。流失率降至 2%,年增长率达到 40%。现在我们正将所有赌注押在高级层级上。"
使用时机: 建议、提案、项目更新
结构:
示例: "我们在结账环节流失了 30% 的注册用户——每年 200 万美元的经常性收入被搁置。根本原因:我们在用户看到价值之前就要求提供信用卡。建议:14 天免费试用,无需信用卡,并通过引导邮件展示投资回报率。类似公司实现了 60% 的转化率提升。预期影响:+120 万美元年经常性收入,实施周期 4 周。"
使用时机: 产品发布、功能公告、流程改进
结构:
示例: "之前:销售团队每周花费 10 小时手动导出数据,在电子表格中清理,然后复制粘贴到幻灯片中——容易出错且令人沮丧。之后:一键生成包含实时数据的报告,自动刷新仪表板,每周 30 分钟。桥梁:我们构建了销售分析 v2.0,周一发布并提供培训课程。"
使用时机: 高管沟通、董事会更新、投资者关系
结构:
示例: "情境:我们为 2024 年客户获取预算了 500 万美元。复杂化:iOS 17 隐私变更扼杀了我们的主要广告渠道——转化率一夜之间下降了 50%。解决方案:将 200 万美元转向内容营销(3 个月投资回报率),100 万美元用于合作伙伴关系(即时分发),保留 200 万美元用于测试新渠道的广告。风险:内容需要时间来扩展,但合作伙伴关系降低了时间线风险。"
数据密集型沟通:
技术 → 非技术:
变革管理:
危机沟通:
应做:
不应做:
危险信号:
资源:
何时使用哪个资源:
每周安装次数
75
代码仓库
GitHub 星标数
45
首次出现
2026年1月24日
安全审计
安装于
opencode69
gemini-cli65
codex65
github-copilot63
cursor60
kimi-cli57
Transform complex information, analysis, or data into clear, persuasive narratives tailored to specific audiences. This skill helps you craft compelling stories with a strong headline, key supporting points, and concrete evidence that drives understanding and action.
Use this skill when you need to:
Audience Translation:
High-Stakes Communication:
Narrative Crafting:
When user says:
Communication storytelling uses a structured approach to create narratives that inform, persuade, and inspire action. The core framework includes:
Quick example:
Bad (data dump): "Our Q2 revenue was $2.3M, up from $1.8M in Q1. Customer count went from 450 to 520. Churn decreased from 5% to 3.2%. NPS improved from 42 to 58. We launched 3 new features..."
Good (storytelling): "We've reached product-market fit. Three signals prove it: (1) Revenue grew 28% while sales capacity stayed flat—customers are pulling product from us, not the other way around. (2) Churn dropped 36% as we focused on power users, with our top segment now at 1% monthly churn. (3) NPS jumped 16 points to 58, with customers specifically praising the three features we bet on. Recommendation: Double down on power user segment with premium tier."
Copy this checklist and track your progress:
Communication Storytelling Progress:
- [ ] Step 1: Gather inputs and clarify audience
- [ ] Step 2: Choose appropriate narrative structure
- [ ] Step 3: Craft the narrative
- [ ] Step 4: Validate quality and clarity
- [ ] Step 5: Deliver and adapt
Step 1: Gather inputs and clarify audience
Ask user for the message (analysis, data, information to communicate), audience (who will receive this), purpose (inform, persuade, inspire, build trust), context (situation, stakes, constraints), and tone (formal, casual, urgent, celebratory). Understanding audience deeply is critical—their expertise level, concerns, decision authority, and time constraints shape everything. See resources/template.md for input questions.
Step 2: Choose appropriate narrative structure
For standard communications (announcements, updates, presentations) → Use resources/template.md quick template. For complex multi-stakeholder communications requiring different versions → Study resources/methodology.md for audience segmentation and narrative adaptation techniques. To see what good looks like → Review resources/examples/.
Step 3: Craft the narrative
Create communication-storytelling.md with: (1) Compelling headline that captures essence in one sentence, (2) 3-5 key points arranged in logical flow (chronological, problem-solution, importance-ranked), (3) Concrete proof for each point (data, examples, quotes, stories), (4) Clear call-to-action stating what audience should do next. Use storytelling techniques: specificity over generality, show don't tell, human stories over abstract concepts, tension/resolution arcs. See Story Structure for narrative patterns.
Step 4: Validate quality and clarity
Self-assess using resources/evaluators/rubric_communication_storytelling.json. Check: headline is clear and compelling, key points are distinct and well-supported, proof is concrete and relevant, flow is logical, tone matches audience, jargon is appropriate for expertise level, call-to-action is clear and achievable, length matches time constraints. Read aloud to test clarity. Test with "so what?" question—does each point answer why audience should care? Minimum standard: Average score ≥ 3.5 before delivering.
Step 5: Deliver and adapt
Present the completed communication-storytelling.md file. Highlight how narrative addresses audience's key concerns. Note storytelling techniques used (data humanized, tension-resolution, specificity). If user has feedback or needs adaptations for different audiences, use resources/methodology.md for multi-version strategy.
When to use: Major changes, pivots, overcoming challenges
Structure:
Example: "We were growing 20% YoY, but churning 10% monthly—unsustainable. Data showed we were solving the wrong problem for the wrong users. We tested 5 hypotheses over 3 months, failing at 4. The one that worked: focusing on power users willing to pay 5x more. Churn dropped to 2%, growth hit 40% YoY. Now we're betting everything on premium tier."
When to use: Recommendations, proposals, project updates
Structure:
Example: "We lose 30% of signups at checkout—$2M ARR left on table. Root cause: we ask for credit card before users see value. Proposal: 14-day trial, no card required, with onboarding emails showing ROI. Comparable companies saw 60% conversion lift. Expected impact: +$1.2M ARR with 4-week implementation."
When to use: Product launches, feature announcements, process improvements
Structure:
Example: "Before: Sales team spends 10 hours/week manually exporting data, cleaning it in spreadsheets, and copy-pasting into slide decks—error-prone and soul-crushing. After: One-click report generation with live data, auto-refreshing dashboards, 30 minutes per week. Bridge: We built sales analytics v2.0, launching Monday with training sessions."
When to use: Executive communications, board updates, investor relations
Structure:
Example: "Situation: We budgeted $5M for customer acquisition in 2024. Complication: iOS 17 privacy changes killed our primary ad channel—50% drop in conversion overnight. Resolution: Shifting $2M to content marketing (3-month ROI), $1M to partnerships (immediate distribution), keeping $2M in ads for testing new channels. Risk: content takes time to scale, but partnerships derisk timeline."
Data-Heavy Communications:
Technical → Non-Technical:
Change Management:
Crisis Communications:
Do:
Don't:
Red Flags:
Resources:
When to use which resource:
Weekly Installs
75
Repository
GitHub Stars
45
First Seen
Jan 24, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode69
gemini-cli65
codex65
github-copilot63
cursor60
kimi-cli57
站立会议模板:敏捷开发每日站会指南与工具(含远程团队异步模板)
10,500 周安装