Skip to content
cccskills
FreePublished on GitHub

storytelling-advisor

Turn ideas, experiences, and messages into structured stories for pitches, brand narratives, speeches, and creative writing. Choose a narrative framework, identify missing story beats, and refine tension and pacing while keeping factual claims separate from invention.

OriginalShow the original description

Shape pitches, brand stories, presentations, and creative writing with narrative frameworks such as the Hero's Journey, Story Spine, and Freytag's Pyramid. Use when a user wants to structure, critique, or strengthen a story.

See how to install

Good for

  • Structuring a founder or brand origin story
  • Turning a product pitch into a story
  • Refining the dramatic flow of a speech
  • Building a narrative for a social media thread

Files included (3)

  • SKILL.md8.9 KB
  • LICENSE.txt1.0 KB
  • NOTICE.md763 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Storytelling Advisor

What It Does

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.

Fact and Fiction Boundary

  • For case studies, pitches, testimonials, biographies, and other factual narratives, use only facts the user supplied or explicitly confirmed.
  • Never silently invent names, quotations, dates, durations, metrics, customers, outcomes, motives, or events to make a factual story more compelling.
  • Mark missing material as a question, a placeholder such as [customer outcome needed], or an explicitly labeled illustrative option.
  • Invent details only when the user requests fiction or explicitly authorizes creative fabrication. Keep fictional additions distinguishable from factual claims.

Frameworks Available

1. The Hero's Journey (Monomyth)

Best for: Brand origin stories, founder journeys, case studies, transformation narratives

StageDescriptionPrompting Question
Ordinary WorldThe hero's normal life before the adventureWhat was life like before the problem was solved?
Call to AdventureAn event disrupts the status quoWhat changed? What forced action?
Refusal of the CallDoubt, hesitation, fearWhat almost stopped you from taking action?
Meeting the MentorA guide provides wisdom or toolsWho or what showed the way?
Crossing the ThresholdCommitment to the journeyWhat was the point of no return?
Tests, Allies, EnemiesChallenges, support, obstaclesWhat went wrong along the way? Who helped?
Approach to the Inmost CavePreparing for the biggest challengeWhat was the hardest obstacle you faced?
OrdealThe central crisisWhat was make-or-break moment?
RewardThe prize for surviving the ordealWhat did you gain?
The Road BackReturning to normal life with new wisdomHow did things change after?
ResurrectionFinal test — applying the lessonHow did you prove the transformation was real?
Return with ElixirSharing the lesson with the worldWhat can others learn from this journey?

2. Pixar Storytelling Formula

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 ___.

ElementRoleFictional product-story example
Once upon a time...Setup — who, where, when"Once upon a time, a community organizer struggled to coordinate neighborhood repairs."
Every day...Status quo — the routine struggle"Every day, useful items were discarded because neighbors could not find help."
One day...Inciting incident"One day, the organizer sketched a simple repair-matching service."
Because of that...Consequence 1"Because of that, volunteers could list the skills they offered."
Because of that...Consequence 2"Because of that, neighbors could match broken items with local help."
Until finally...Resolution"Until finally, the first fictional repair day could be coordinated in one place."

3. Freytag's Pyramid (Dramatic Structure)

Best for: Speeches, presentations, campaign narratives

ElementPurpose
ExpositionContext — what's the situation?
Rising ActionTension builds — what's at stake?
ClimaxThe turning point — the big reveal or decision
Falling ActionConsequences unfold
DenouementResolution and takeaway

4. The Story Spine

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...

5. The Inverted Pyramid

Best for: Newsletters, blog posts, executive summaries

LayerContent
LeadThe most critical information (who, what, when, where, why)
BodySupporting details, context, evidence
TailBackground, nuance, optional reading

Trigger Phrases

PhraseAction
"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

Step-by-Step Instructions

Step 1: Clarify the Goal

Infer what the audience should feel, think, and do from the request. Ask one focused question only when the missing goal would materially change the story.

Step 2: Harvest the Raw Material

Collect:

  • Characters (who is the hero? who is the mentor? who is the antagonist?)
  • Setting (where and when does this happen?)
  • Conflict (what was the problem or challenge?)
  • Stakes (what was at risk?)
  • Transformation (how did things change?)
  • Lesson (what can be learned?)

Separate confirmed facts from assumptions and gaps before drafting. Ask only for gaps that materially affect the story; otherwise retain visible placeholders.

Step 3: Select the Framework

Match the story type to the right structure:

If you're telling...Use...
A founder origin storyHero's Journey
A product value propPixar Formula
A keynote or speechFreytag's Pyramid
A social media threadStory Spine
A newsletter or articleInverted Pyramid

Step 4: Map Content to Structure

Fill each framework slot with your raw material. Identify gaps and missing beats.

Step 5: Add Narrative Devices

  • Emotional hook: Start with a relatable moment or surprise
  • Specific details: Prefer concrete details supplied by the user. Never add a detail such as "3 AM in a coffee shop" to a factual account unless it is confirmed.
  • Tension: What was almost lost? What was uncertain?
  • Pacing: Short sentences for action, longer ones for reflection

Step 6: Refine and Cut

  • Remove everything that doesn't serve the goal
  • Read aloud to test rhythm
  • Tighten: Can you say it in half the words?

Step 7: End with a Punch

The last line should be memorable — a lesson learned, a question posed, an invitation extended.


Examples

Example 1: Factual Founder Story with Gaps

Input: "I built a project management tool because Trello was too simple and Jira was too complex."

Output (outline):

  • Problem: Existing tools felt either too simple or too complex for the user's needs.
  • Action: The user built a project management tool.
  • Outcome: [What changed for you or your users?]
  • Evidence needed: [Who first used it?] [What measurable result can be verified?]

Do not add a company size, customer crisis, development timeline, adoption count, or testimonial unless the user supplies it.

Example 2: Explicitly Fictional Product Launch Exercise

Input: "Create a fictional launch-story example for a new habit tracking app."

Output: "Fictional example: Once upon a time, there was a developer who wanted a kinder way to build habits. Every day, rigid streaks made one missed day feel like failure. One day, the developer tried a tracker that welcomed restarts. Because of that, returning became easier. Until finally, the idea became an app designed around beginning again."


Pro Tips

  • Start in the middle: The most interesting story doesn't always start at the beginning. Open with the crisis, then flash back.
  • Use contrast: Before/after, then/now, almost lost/eventually won.
  • Use verified specificity: Real, sourced numbers are stronger than generic claims. Use placeholders when the number is not known.
  • Include a limitation: For factual stories, include a supported challenge or trade-off rather than making the subject unrealistically one-dimensional.
  • End with a call-to-story: Invite the audience to see themselves in the narrative.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Review completed code through three roles: a critical reviewer, a verifier, and an adjudicator. Check evidence, look for bugs introduced by fixes, and produce an actionable repair list with regression tests and traceable review reports.

  • Reviewing code before a release
  • Checking major refactors for regressions
  • Verifying that reported fixes actually work
iflytek/skillhub5.3KUpdated Oct 19, 2026

ai-claim-checker

FreeSummary

Assess factual claims in AI-generated text by separating facts from opinions, choosing suitable independent evidence, and explaining what is supported or uncertain. Use it for a completed fact-check or an optional exercise in evaluating AI answers.

  • Fact-checking an AI-generated answer
  • Choosing independent sources for a claim
  • Identifying unverified numbers and assertions
iflytek/skillhub5.3KUpdated Oct 19, 2026

cue-omni-reader

FreeSummary

Parse web pages and authorized local documents, audio, or video with Cue Omni Reader. Use the complete results to summarize content, answer questions, locate sections, or save the parsed output.

  • Summarizing a web page from its URL
  • Answering questions about a local document
  • Reviewing the content of audio or video
iflytek/skillhub5.3KUpdated Oct 19, 2026

Generate brief daily check-ins, evening reflection questions, and weekly or monthly reviews for individuals and teams. Summarize supplied entries to highlight accomplishments, blockers, and supported patterns, with optional suggestions for next actions.

  • Clarifying today's priorities in a morning check-in
  • Drafting an asynchronous team progress update
  • Reflecting on lessons at the end of the day
iflytek/skillhub5.3KUpdated Oct 19, 2026

decision-matrix

FreeSummary

Compare choices using weighted scores, pros and cons, possible failure scenarios, and what each option means giving up. Make preferences and uncertainty explicit, rank alternatives, and identify information that could change the decision.

  • Comparing job offers or client projects
  • Prioritizing features and experiments
  • Exploring failure risks before committing
iflytek/skillhub5.3KUpdated Oct 19, 2026

diagram-maker

FreeSummary

Turn concepts, processes, and system architecture into diagrams. Create a self-contained HTML file with SVG graphics for browser viewing, or an editable Excalidraw file for whiteboard sketches and flowcharts.

  • Illustrating concepts and processes for teaching
  • Mapping software and cloud architecture
  • Creating editable whiteboard sketches
iflytek/skillhub5.3KUpdated Oct 19, 2026

See all skills by iflytek

Report a problem with this skill