mcpField
S
storytelling

storytelling

github.com/gtmagentsMarketing & growth431118 installsUpdated 30w ago
Repository

About storytelling

A storytelling skill for marketers and sales teams creating campaign, launch, and pitch narratives. It uses an audience-centered arc, concrete details, and calls to action to connect customer challenges with product value.

Key features

  1. 01Audience and conflict framing
  2. 02SCAR story arc
  3. 03Persona characterization
  4. 04Narrative and pitch templates
  5. 05Customer story inventory

Use cases

  1. 01Developing product launch narratives
  2. 02Turning technical features into customer stories
  3. 03Preparing spokespeople or SDRs for pitches

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill storytelling

After installing, type/storytellingin Claude Code to confirm it loaded.

Details

From the project README

Storytelling Skill

When to Use

  • Need cohesive narrative for campaigns, product launches, or decks.
  • Translating technical capabilities into relatable customer stories.
  • Coaching spokespeople or SDRs on better pitch storytelling.

Framework

  1. Audience & Conflict – identify who the hero is (customer persona) and what obstacle they face.
  2. Story Arc (SCAR) – Situation → Complication → Action → Resolution.
  3. Characterization – give personas motives, stakes, and quotes.
  4. Sensory Detail – use vivid language, specific metrics, and concrete examples.
  5. Moral/CTA – tie resolution back to product value and explicit next step.

Templates

  • Narrative outline (hook, scene, rising tension, turn, resolution, CTA).
  • Pitch script template:
"Most {persona}s today face {pain}. When {trigger}, {impact}. We worked with {customer} to {action}, leading to {result}."
  • Story inventory tracker to log customer, industry, proof points.

Tips

  • Record customer interviews to capture natural phrasing for quotes.
  • Swap metaphors/analogies per persona so stories feel tailored.
  • Reinforce numbers with vivid imagery (e.g., "saved hours = extra sprints delivered").
  • Align every story with the current positioning doc to avoid mixed messages.

Comments

Markdown supported