360 Secure SkillHub
360 安全技能中心

data-storytelling

提供数据叙事的结构化方法:故事结构(背景—冲突—结论)、叙事弧线、数据/叙事/视觉三支柱,以及面向高管的呈现要点与常见误区清单;更详细的模式与示例放在参考文件中按需查阅。适用于数据报告、季度业务回顾和投资者演示的内容策划与组织。

wshobson
热度 82.94
最近更新 2026-10-18 15:57:01
分类:数据依赖:纯提示词应用场景:故事创作 / 报告撰写

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add wshobson/agents/data-storytelling
Metadata
name
data-storytelling
description
Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive presentations.

Data Storytelling

Transform raw data into compelling narratives that drive decisions and inspire action.

When to Use This Skill

  • Presenting analytics to executives
  • Creating quarterly business reviews
  • Building investor presentations
  • Writing data-driven reports
  • Communicating insights to non-technical audiences
  • Making recommendations based on data

Core Concepts

1. Story Structure

Setup → Conflict → Resolution

Setup: Context and baseline
Conflict: The problem or opportunity
Resolution: Insights and recommendations

2. Narrative Arc

1. Hook: Grab attention with surprising insight
2. Context: Establish the baseline
3. Rising Action: Build through data points
4. Climax: The key insight
5. Resolution: Recommendations
6. Call to Action: Next steps

3. Three Pillars

Pillar Purpose Components
Data Evidence Numbers, trends, comparisons
Narrative Meaning Context, causation, implications
Visuals Clarity Charts, diagrams, highlights

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

Do's

  • Start with the "so what" - Lead with insight
  • Use the rule of three - Three points, three comparisons
  • Show, don't tell - Let data speak
  • Make it personal - Connect to audience goals
  • End with action - Clear next steps

Don'ts

  • Don't data dump - Curate ruthlessly
  • Don't bury the insight - Front-load key findings
  • Don't use jargon - Match audience vocabulary
  • Don't show methodology first - Context, then method
  • Don't forget the narrative - Numbers need meaning