cosmicstack-labs/storytelling-advisor
A narrative architecture coach that guides you through proven story frameworks — Hero's Journey, Pixar Storytelling Formula, Freytag's Pyramid, and more — to shape compelling narratives for pitches, brand stories, content, and presentations.
npx skills add https://github.com/cosmicstack-labs/mercury-agent-skills --skill storytelling-advisor
Transforms raw ideas, experiences, or messages into structured narratives using proven storytelling frameworks. Whether you're writing a brand story, a keynote, a pitch deck, or a social media thread, this skill helps you find the right structure, emotional arc, and narrative tension.
Best for: Brand origin stories, founder journeys, case studies, transformation narratives
| Stage | Description | Prompting Question |
|-------|-------------|-------------------|
| Ordinary World | The hero's normal life before the adventure | What was life like before the problem was solved? |
| Call to Adventure | An event disrupts the status quo | What changed? What forced action? |
| Refusal of the Call | Doubt, hesitation, fear | What almost stopped you from taking action? |
| Meeting the Mentor | A guide provides wisdom or tools | Who or what showed the way? |
| Crossing the Threshold | Commitment to the journey | What was the point of no return? |
| Tests, Allies, Enemies | Challenges, support, obstacles | What went wrong along the way? Who helped? |
| Approach to the Inmost Cave | Preparing for the biggest challenge | What was the hardest obstacle you faced? |
| Ordeal | The central crisis | What was make-or-break moment? |
| Reward | The prize for surviving the ordeal | What did you gain? |
| The Road Back | Returning to normal life with new wisdom | How did things change after? |
| Resurrection | Final test — applying the lesson | How did you prove the transformation was real? |
| Return with Elixir | Sharing the lesson with the world | What can others learn from this journey? |
Best for: Short-form narratives, social media stories, email sequences, product launches
> Structure: Once upon a time there was \_\_\_. Every day, \_\_\_. One day \_\_\_. Because of that, \_\_\_. Because of that, \_\_\_. Until finally \_\_\_.
| Element | Role | Example (Brand Story) |
|---------|------|----------------------|
| Once upon a time... | Setup — who, where, when | "Once upon a time, a designer couldn't find a simple prototyping tool." |
| Every day... | Status quo — the routine struggle | "Every day, she wasted hours on complex software that kept crashing." |
| One day... | Inciting incident | "One day, she decided to build her own tool." |
| Because of that... | Consequence 1 | "Because of that, her friends asked to use it too." |
| Because of that... | Consequence 2 | "Because of that, she realized others had the same problem." |
| Until finally... | Resolution | "Until finally, Figma was born." |
Best for: Speeches, presentations, campaign narratives
| Element | Purpose |
|---------|---------|
| Exposition | Context — what's the situation? |
| Rising Action | Tension builds — what's at stake? |
| Climax | The turning point — the big reveal or decision |
| Falling Action | Consequences unfold |
| Denouement | Resolution and takeaway |
Best for: Team storytelling, collaborative narrative building
> Once upon a time... And every day... But one day... And because of that... And because of that... And because of that... Until finally... And ever since that day... The moral of the story is...
Best for: Newsletters, blog posts, executive summaries
| Layer | Content |
|-------|---------|
| Lead | The most critical information (who, what, when, where, why) |
| Body | Supporting details, context, evidence |
| Tail | Background, nuance, optional reading |
| Phrase | Action |
|--------|--------|
| "Help me tell a story about..." | Guides you through selecting the best framework |
| "Turn this into a narrative..." | Structures raw info into a story arc |
| "Make this more compelling..." | Suggests adding stakes, tension, or emotional beats |
| "Tell my brand story..." | Applies Hero's Journey to brand/founder narrative |
| "Pixar this for me..." | Forces content into the Pixar formula |
| "What framework should I use for..." | Recommends the best framework for your context |
| "Pitch this as a story..." | Converts a pitch into narrative form |
Ask: What do you want the audience to feel, think, and do after hearing this story?
Collect:
Match the story type to the right structure:
| If you're telling... | Use... |
|---------------------|--------|
| A founder origin story | Hero's Journey |
| A product value prop | Pixar Formula |
| A keynote or speech | Freytag's Pyramid |
| A social media thread | Story Spine |
| A newsletter or article | Inverted Pyramid |
Fill each framework slot with your raw material. Identify gaps and missing beats.
The last line should be memorable — a lesson learned, a question posed, an invitation extended.
> Input: "I built a project management tool because Trello was too simple and Jira was too complex."
>
> Output (condensed):
> "As a designer at a 50-person agency, Sarah lived in spreadsheet chaos — every day, tasks slipped through the cracks (Ordinary World). When a client threatened to leave over a missed deadline, she knew something had to change (Call to Adventure). She almost bought another tool, but none fit (Refusal). Her partner suggested building something just for their team (Mentor). So she spent three weekends coding a prototype (Crossing the Threshold). Early users hated the first version — too many bugs (Tests)... until finally, she stripped it down to one feature: a clean Kanban board that *actually* worked. That became Trello 2.0. The client stayed. And 10,000 teams later, the lesson is clear: simple beats feature-rich when execution matters. (The Elixir)."
> Input: "Launching a new habit tracking app"
>
> Output:
> "Once upon a time, there was a developer who wanted to build better habits. Every day, he downloaded habit trackers, used them for three days, and abandoned them. One day, he realized the problem: they all punished you for missing a day. Because of that, he designed an app that celebrates streaks without shaming gaps. Because of that, his own habits stuck for the first time. Until finally — after 18 months of building — Streakful was ready for the world. The first 500 beta users are in. Want to join them?"
Take cosmicstack-labs/storytelling-advisor from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.