Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Apply narrative structure and storytelling techniques for brand, business, and communication contexts. Use this skill when the user needs to craft a compelling story, build a brand narrative, structure a presentation around a story arc, or use storytelling to communicate data or strategy — even if they say 'tell a better story', 'make this presentation more engaging', or 'how do we build our brand story'.
.claude/skills/asgard-ai-platform-hum-narrative/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | -50% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -21% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 5% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -18% | 0% |
| case-06 | ✗→✓ | ▲ Improved | 5% | 0% |
Stories are the most natural human communication format. Narrative structure gives information emotional weight, memorability, and meaning. This skill applies storytelling principles to business contexts: brand stories, presentations, pitches, and change communication.
IRON LAW: Every Story Needs Tension
A narrative without conflict or tension is a report, not a story. The tension
can be a problem to solve, a gap between current and desired state, or an
obstacle to overcome. Without tension, there's no reason for the audience
to keep listening.| Element | Question | Example | |---------|---------|---------| | Founding myth | Why does this company exist? | "We started because we couldn't find X..." | | Enemy | What wrong are you fighting? | "The industry treats customers like numbers" | | Quest | What are you trying to achieve? | "We're on a mission to make X accessible to everyone" | | Values | What principles guide you? | "We believe in transparency, simplicity, and..." | | Transformation | What change do you create? | "Our customers go from struggling with X to thriving at Y" |
Presentations: Open with a story (Pathos), then transition to data (Logos). "Let me tell you about one customer..." → "And she's not alone — here's the data."
Pitch decks: Problem (tension) → Solution (your product) → Traction (proof the story is working) → Vision (how the story ends)
Change communication: Current state (familiar) → Why change is needed (tension) → Vision of future state (resolution) → How we get there (plan)
Data storytelling: Don't just show charts. Frame them: "We expected X to happen. Instead, Y happened. Here's why, and here's what it means."
markdown# Narrative Design: {Context} ## Story Arc 1. **Setup**: {status quo} 2. **Trigger**: {what disrupted it} 3. **Struggle**: {challenges faced} 4. **Climax**: {turning point} 5. **Resolution**: {new state} ## Key Elements - Tension: {the core conflict} - Character: {who the audience identifies with} - Stakes: {what happens if the tension isn't resolved} - Transformation: {what changes} ## Application {How to integrate this narrative into the specific communication context}
Scenario: Brand story for a Taiwanese sustainable packaging startup
references/heros-journey.md| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 31,505 | 19,775 | -37% | 1 | 1 | 0% | 4,591 | 4,060 | -12% | 0 | 0 | — |
case-02 | fail→pass | 48,161 | 17,906 | -63% | 1 | 1 | 0% | 7,140 | 3,564 | -50% | 0 | 0 | — |
case-03 | fail→pass | 25,009 | 14,495 | -42% | 1 | 1 | 0% | 3,814 | 3,006 | -21% | 0 | 0 | — |
case-04 | fail→pass | 20,385 | 15,977 | -22% | 1 | 1 | 0% | 3,202 | 3,376 | +5% | 0 | 0 | — |
case-05 | fail→pass | 25,183 | 12,714 | -50% | 1 | 1 | 0% | 3,806 | 3,107 | -18% | 0 | 0 | — |
case-06 | fail→pass | 21,963 | 16,539 | -25% | 1 | 1 | 0% | 3,489 | 3,657 | +5% | 0 | 0 | — |
case-07 | fail→pass | 16,698 | 13,791 | -17% | 1 | 1 | 0% | 2,761 | 3,143 | +14% | 0 | 0 | — |
case-08 | fail→pass | 21,262 | 15,231 | -28% | 1 | 1 | 0% | 3,272 | 3,457 | +6% | 0 | 0 | — |
case-09 | fail→pass | 19,083 | 14,700 | -23% | 1 | 1 | 0% | 2,946 | 3,334 | +13% | 0 | 0 | — |
case-10 | fail→pass | 24,088 | 14,481 | -40% | 1 | 1 | 0% | 3,312 | 3,220 | -3% | 0 | 0 | — |
case-11 | fail→pass | 30,033 | 13,429 | -55% | 1 | 1 | 0% | 4,194 | 3,148 | -25% | 0 | 0 | — |
case-12 | fail→pass | 45,270 | 11,979 | -74% | 1 | 1 | 0% | 3,991 | 2,914 | -27% | 0 | 0 | — |
case-13 | fail→fail | 25,914 | 18,255 | -30% | 1 | 1 | 0% | 3,869 | 3,744 | -3% | 0 | 0 | — |
case-14 | fail→pass | 24,251 | 12,343 | -49% | 1 | 1 | 0% | 3,450 | 3,098 | -10% | 0 | 0 | — |
case-15 | fail→pass | 20,887 | 16,744 | -20% | 1 | 1 | 0% | 3,033 | 3,377 | +11% | 0 | 0 | — |
case-16 | fail→pass | 25,002 | 14,322 | -43% | 1 | 1 | 0% | 3,707 | 3,016 | -19% | 0 | 0 | — |
case-17 | fail→pass | 45,953 | 22,972 | -50% | 1 | 1 | 0% | 5,834 | 4,322 | -26% | 0 | 0 | — |
case-18 | fail→fail | 23,157 | 15,002 | -35% | 1 | 1 | 0% | 3,057 | 3,077 | +1% | 0 | 0 | — |
case-19 | fail→pass | 28,423 | 14,240 | -50% | 1 | 1 | 0% | 4,123 | 3,260 | -21% | 0 | 0 | — |
case-20 | pass→fail | 12,505 | 16,835 | +35% | 1 | 1 | 0% | 2,312 | 3,610 | +56% | 0 | 0 | — |
case-21 | pass→pass | 16,788 | 17,762 | +6% | 1 | 1 | 0% | 3,063 | 4,680 | +53% | 0 | 0 | — |
case-22 | pass→fail | 9,763 | 18,128 | +86% | 1 | 1 | 0% | 1,763 | 3,968 | +125% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +64 percentage points is the difference between those two pass rates over the 22 comparable cases. 3 cases got worse with the skill loaded, and they are included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.