data-storytelling
Narrative generation skill for transforming analytical insights into compelling business stories
What this skill does
# Data Storytelling
## Overview
The Data Storytelling skill transforms analytical insights into compelling, actionable business narratives. It bridges the gap between complex analysis and executive decision-making by generating clear, contextual, and persuasive communications tailored to different audiences.
## Capabilities
- Insight prioritization and selection
- Narrative structure generation
- Chart annotation automation
- Key takeaway extraction
- Executive summary generation
- Recommendation framing
- Action item identification
- Audience-appropriate language adaptation
## Used By Processes
- Insight-to-Action Process
- Executive Dashboard Development
- Decision Documentation and Learning
## Usage
### Insight Input
```python
# Analytical insights to narrate
insights = {
"context": {
"analysis_type": "quarterly_performance",
"period": "Q3 2024",
"audience": "executive_leadership",
"objective": "investment_decision"
},
"key_findings": [
{
"metric": "Revenue",
"value": 12500000,
"change": 0.15,
"benchmark": "above_target",
"significance": "high",
"drivers": ["new_product_launch", "market_expansion"]
},
{
"metric": "Customer Acquisition Cost",
"value": 185,
"change": 0.22,
"benchmark": "above_target",
"significance": "medium",
"drivers": ["increased_competition", "channel_mix_shift"]
}
],
"supporting_data": {
"visualizations": ["revenue_trend.png", "cac_breakdown.png"],
"tables": ["segment_performance.csv"]
}
}
```
### Narrative Configuration
```python
# Narrative structure configuration
narrative_config = {
"structure": "situation_complication_resolution",
"tone": "professional",
"length": "executive_summary", # or "detailed_report"
"format": "markdown",
"sections": [
"headline",
"key_takeaways",
"context",
"analysis",
"recommendations",
"next_steps"
],
"emphasis": "actionable_recommendations"
}
```
### Audience Adaptation
```python
# Audience-specific settings
audience_profiles = {
"executive_leadership": {
"detail_level": "high_level",
"jargon": "minimal",
"focus": "strategic_implications",
"format_preference": "bullet_points",
"time_available": "2_minutes"
},
"technical_team": {
"detail_level": "detailed",
"jargon": "acceptable",
"focus": "methodology_and_data",
"format_preference": "full_narrative",
"time_available": "15_minutes"
},
"board_of_directors": {
"detail_level": "summary",
"jargon": "none",
"focus": "business_impact",
"format_preference": "visual_heavy",
"time_available": "5_minutes"
}
}
```
## Narrative Structures
| Structure | Best For | Flow |
|-----------|----------|------|
| SCR (Situation-Complication-Resolution) | Problem-solving | Context -> Challenge -> Solution |
| Pyramid | Executive updates | Conclusion -> Supporting points -> Details |
| Before-After-Bridge | Change proposals | Current state -> Future state -> How to get there |
| STAR | Case studies | Situation -> Task -> Action -> Result |
| What-So What-Now What | Quick insights | Finding -> Implication -> Action |
## Input Schema
```json
{
"insights": {
"context": "object",
"key_findings": ["object"],
"supporting_data": "object"
},
"narrative_config": {
"structure": "string",
"tone": "string",
"length": "string",
"sections": ["string"]
},
"audience": {
"profile": "string",
"detail_level": "string",
"time_available": "string"
}
}
```
## Output Schema
```json
{
"narrative": {
"headline": "string",
"executive_summary": "string",
"sections": {
"section_name": "string (markdown)"
},
"key_takeaways": ["string"],
"recommendations": ["string"],
"next_steps": [
{
"action": "string",
"owner": "string",
"timeline": "string"
}
]
},
"annotations": {
"visualization_id": "string annotation"
},
"metadata": {
"word_count": "number",
"reading_time": "string",
"complexity_score": "number"
}
}
```
## Best Practices
1. Lead with the most important insight (inverted pyramid)
2. Use specific numbers, not vague descriptors
3. Connect data to business outcomes
4. Include clear calls to action
5. Acknowledge limitations and uncertainties
6. Use active voice and strong verbs
7. Test narrative with representative audience member
## Annotation Guidelines
For chart annotations:
- Highlight the key insight, not just describe the data
- Use arrows and callouts sparingly
- Provide context (comparisons, benchmarks)
- Include "so what" implications
## Integration Points
- Receives insights from all analysis skills
- Connects with Decision Visualization for annotated charts
- Feeds into Decision Journal for documentation
- Supports Insight Translator agent for communication
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.