Emotional Impact In Stories logo

Emotional Impact In Stories

Community
fatihguner
emotional-impact-in-stories

Explains the singular mechanism for making audiences cry (surprise, not sadness) and two named techniques for making them laugh (Milk Cans and Baseballs, Babies and Blenders). Applies when a founder is crafting a keynote, investor narrative, brand story, or any communication designed to move an audience emotionally. Use when a story feels informative but flat, when humour falls short, or when a narrative needs to land in the heart rather than the head.

Overview

Publisherfatihguner
Repositoryforeman
Skill nameemotional-impact-in-stories
Stars
63
Forks
10
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by fatihguner on GitHub. Read the source before you install it.

Installation

Install the Emotional Impact In Stories AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/emotional-impact-in-stories
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/fatihguner/foreman.git /tmp/foreman
mkdir -p .claude/skills
cp -r /tmp/foreman/plugins/foreman/skills/emotional-impact-in-stories .claude/skills/emotional-impact-in-stories
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Emotional Impact In Stories in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Emotional Impact In Stories on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Emotional Impact In Stories is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

Emotional Impact in Stories

There is exactly one way to make someone cry -- and it is not sadness. It is surprise. The framework argues this with the conviction of a principle tested in front of thousands of audiences: tears are not produced by tragic content. They are produced by unexpected reveals, unanticipated connections, and the sudden inversion of the emotional expectation the storyteller has carefully constructed. The same principle governs laughter. Every emotional response in storytelling -- tears, anger, joy, outrage -- traces back to a well-cultivated surprise. The entrepreneur who understands this mechanism holds a tool more powerful than any slide deck: the ability to make a room feel something it did not expect to feel.


The Framework

Part I: The Mechanics of Tears

In life, many things provoke tears: grief, pain, overwhelming love, exhaustion. Storytellers have access to none of these. They cannot cause physical pain or recreate years of accumulated loss. All they have is words, deployed in sequence. The only emotional lever available is surprise.

The principle is demonstrated through the story "This Is Going to Suck," in which the storyteller dies briefly after a head-on collision. Audiences wince at the violence. They groan at the description of teeth knocked loose and legs embedded in metal. But nobody cries at the accident. Despite its brutality, the collision is expected -- the audience was told it was coming.

They cry later, when they learn that teenage friends have filled the hospital waiting room. This is the surprise. It was hidden, planted, and detonated at the precise moment of maximum contrast.

Three strategies make surprise work:

1. Build one expectation, then deliver a different (deeper) one.

The emotional architecture is misdirection. Construct a world in which the audience believes they know what the story is about. Then reveal that the story was always about something else. This is called changing the colour of the Elephant -- the audience thought they were tracking one question, and the answer to a different, more profound question arrives instead.

In entrepreneurial contexts: the pitch that appears to be about a product feature turns out to be about the founder's child. The customer case study that appears to be about efficiency gains turns out to be about a warehouse worker's dignity. The deeper layer, arriving unexpectedly, is what produces the response.

2. Heighten contrast immediately before the surprise.

The moment before the surprise should be as emotionally distant from it as possible. The story paints a picture-postcard winter scene -- snow falling on lawns, hope for a good Christmas -- seconds before a collision destroys everything. The beauty amplifies the horror. It describes isolation and abandonment in an emergency room -- no one knows his name, his parents chose to check the car first -- before revealing that friends have arrived.

The principle is universal: laugh before cry, hope before loss, darkness before light. Contrast is the amplifier.

3. Hide the critical information.

If the audience sees the surprise coming, it ceases to be a surprise. Two techniques preserve it:

  • Hiding the bomb in the clutter. Embed the critical detail among other details of apparently equal importance. The request for a nurse to call McDonald's -- the fact that triggers the entire climactic sequence -- is buried in a list of medical procedures. It looks like just another thing happening in an emergency room. It is, in fact, the most important sentence in the story.

  • Camouflaging with laughter. Attach a laugh line to the critical detail. The audience attributes the moment to the storyteller's sense of humour, not to narrative engineering. "I was dead twenty minutes ago and now I'm worried about work, but that drive-through does not run well without me." The laugh obscures the bomb.

What ruins surprise:

  • Thesis statements. "This is a story about a time my friends became my family." The surprise is dead on arrival. Storytelling is the reverse of the five-paragraph essay. Evidence first, thesis last -- if at all.

  • Failing to use stakes. The Backpack, Breadcrumbs, and Hourglass from the stakes framework exist in part to amplify surprise. A plan that is articulated in detail and then fails is more surprising than a plan that fails without setup. Stakes and surprise are symbiotic.

  • Revealing too early. Placing the important detail near the payoff, where the audience can connect the dots. Distance is an ally. Plant the bomb early. Detonate it late.

Part II: The Mechanics of Laughter

The framework is candid: it cannot make a person funny. Humour involves wit, timing, tonality, confidence, and a relationship with language that resists systematic instruction. What it can do -- and what this framework addresses -- is help a storyteller add humour to a story through structural technique, even if the storyteller is not naturally amusing.

Two named methods cover the vast majority of story-based humour:

Milk Cans and a Baseball

The name derives from the carnival game: stack metallic milk cans in a tower, then knock them down with a ball. In comedy, this is setup and punchline. The milk cans are the setup; the ball is the punchline.

The rule: save the funniest word for last. The instinct of most people is to say the funny thing first, because they are excited about it. This ruins the laugh. The tower of expectations must be built before the ball is thrown.

Consider the example: "I sleep in a pantry off their kitchen that they've converted into a tiny bedroom. I share this room with a Jehovah's Witness named Rick, a guy who speaks in tongues in his sleep, and the family's indoor pet goat."

The word goat is last because it is the most unexpected. The milk cans -- Jehovah's Witnesses, pantry, tiny bedroom, Rick, speaking in tongues, in his sleep, indoor, pet -- build a tower of increasingly unusual details. Each one recalibrates the audience's expectations. Then goat demolishes them.

Specificity is funny. "Pouring water over Raisin Bran because I am too stupid and lazy to buy milk" is funnier than "pouring water over cereal." Oddly specific words generate laughs that generic ones cannot. Some words are inherently amusing -- the well-documented comedic potency of the hard K sound bears this out. The choice of Pop-Tarts over crackers is deliberate.

Babies and Blenders

When two things that rarely or never go together are pushed together, humour often results. The framework calls this Babies and Blenders -- the juxtaposition of the innocent and the incongruous.

Calling a three-year-old boy "a little asshole" after describing him as sweet and angelic gets a laugh because the two categories should not occupy the same sentence. Referring to a grandmother as "a sadist" is funny precisely because the words grandmother and sadist have never been introduced to each other.

The technique extends to lists. A storyteller creates a sequence of three items, the third of which is categorically unlike the first two: "Zimmers, pineapple-flavoured ham, and despair." The pattern established by the first two items is broken by the third. The break is the surprise. The surprise is the laugh.

Exaggeration is a subspecies of Babies and Blenders: an unreasonable description pushed against something that does not normally accommodate it. "A Christmas tree seven feet wide and three feet tall." The audience knows the dimensions are false, which is why it works. If the exaggeration is presented as fact, it is no longer exaggeration; it is lying.

The Strategic Use of Humour in Stories

Humour is not the goal of storytelling. Heart is the goal. Humour serves four strategic functions:

  1. Opening laugh. A laugh in the first thirty seconds signals competence, claims the floor, and reassures the audience that the storyteller is okay -- whatever darkness follows, it is in the past.

  2. Laugh before the blow. Placing humour immediately before a painful moment heightens the contrast. "I like to make people laugh before making them cry, because it hurts more that way," as the text puts it.

  3. Breath after tension. Following an intense sequence with a laugh allows the audience to reset. Sustained tension without relief becomes numbing.

  4. Camouflage. A laugh line draws attention away from a critical detail that must be hidden for a later surprise.

Stories must end on heart, not on humour. The final sentences should be moving, vulnerable, or universally connecting. Laughs belong in the middle, carrying the audience forward. The landing must be something bigger.


Prompts

Prompt 1 -- Surprise Architecture:

Here is a story I plan to tell: [paste narrative]. Identify the moment that should produce the strongest emotional response. Then help me restructure the narrative so that (a) a contrasting emotional expectation is built before that moment, (b) the critical information enabling the surprise is hidden earlier in the story using clutter or comedic camouflage, and (c) no thesis statement gives the surprise away.

Prompt 2 -- Humour Injection (Milk Cans and Baseballs):

Here is a passage from my story that is situationally funny but not landing as hard as it could: [paste passage]. Restructure it using the Milk Cans and a Baseball technique. Identify the funniest word or phrase and move it to the end. Build a tower of increasingly specific and unexpected details before it. Suggest oddly specific words to replace generic ones.

Prompt 3 -- Emotional Journey Map:

I am delivering a [pitch / keynote / all-hands address / customer story] and I want the audience to experience at least three distinct emotional states. Map out an emotional journey for the narrative: where should the audience laugh, where should they feel tension, where should they feel moved? Place each humour moment strategically (opening signal, pre-blow contrast, post-tension breath, or camouflage).

Prompt 4 -- Babies and Blenders Audit:

Review this narrative for opportunities to use the Babies and Blenders technique: [paste]. Identify moments where two incongruous elements can be pushed together for comedic effect. Suggest list-of-three constructions where the third item breaks the pattern established by the first two. Ensure that all humour serves the story rather than undermining its emotional destination.


Use Cases

Brand Keynote -- Consumer Health Startup

A founder delivers a keynote about chronic disease management. The narrative is earnest and informative but produces no emotional response. Applying the framework: the surprise is restructured. The story appears to be about technology (the Elephant) but is revealed to be about a patient's relationship with her daughter. The critical detail -- that the daughter programmed the app herself, at age fourteen -- is hidden in a list of beta testers and camouflaged with a laugh line about the daughter's feedback being "more brutal than any venture capitalist's." The audience expects admiration for the technology. They get admiration for a child's love. The keynote ends not on metrics but on the sentence the daughter said to her mother when the app worked for the first time. The room is silent. Then it is not.

Investor Update -- Series B SaaS Company

A CEO sends a quarterly investor letter that typically reads as a dashboard with commentary. Applying the emotional impact framework: the letter opens with a laugh (Milk Cans and a Baseball -- the CEO describes the office's new espresso machine as "the only piece of equipment with a higher utilisation rate than our production servers, and better uptime"). The critical surprise -- that the company's largest competitor has begun referring customers to them -- is hidden in a paragraph about partnership strategy, camouflaged by a self-deprecating aside. The surprise lands three paragraphs later when the CEO reveals the competitor's CEO called personally. The letter ends on heart: a single sentence from a customer support ticket that captures what the product means to the people who use it.

Team Retrospective -- After a Failed Product Launch

A product lead tells the story of a feature launch that missed its targets. The instinct is to present the failure analytically, with charts. Applying the framework: the story is restructured to produce emotional engagement. Babies and Blenders opens the narrative ("We planned this launch for four months and executed it with the precision of a marching band and the market awareness of a goldfish"). The surprise is not the failure itself -- everyone in the room already knows the numbers -- but a piece of customer feedback received during the post-mortem that reframed what the team had actually built. The laugh before the blow comes immediately before the customer's words are read aloud. The story ends not on the failure but on what the team now understands about its customers that it did not understand before.


Anti-Patterns

  • Confusing sadness with emotional impact. A story saturated in tragedy does not automatically move an audience. It numbs them. Emotional impact requires surprise, which requires contrast, which requires the story to not be uniformly dark. The founder who opens with devastation and ends with devastation has given the audience nowhere to travel.

  • Putting the funny word first. The most common humour failure in storytelling. The speaker leads with the punchline because they cannot wait to get to it, then wonders why the room did not laugh. Milk Cans and a Baseball demands patience: build the tower, then throw the ball. Not the reverse.

  • Using humour as the destination. Ending a story on a joke, a pun, or a clever turn of phrase. The audience laughs and then forgets. Heart is what lingers. Laughter is a vehicle, not a destination. The final sentences must land somewhere vulnerable, meaningful, or universally true.

  • Telegraphing the surprise with a thesis statement. "This is a story about how our customers became our family." Every emotional beat that follows is pre-digested. The audience cannot be surprised by something they were told at the outset. Evidence first. Thesis never -- or thesis last and understated.

  • Hiding nothing. Telling the story in strict chronological order with every important detail flagged as important. The audience connects the dots before the storyteller detonates the surprise. Critical information must be planted early, buried in clutter, and camouflaged by laughter. The gap between planting and payoff is the space where surprise grows.


By Stage

StageFocusKey Difference
IdeaSurprise must compensate for the absence of proofThe emotional payload is the founder's personal connection to the problem -- hidden, then revealed
ValidationLaughter builds rapport in early customer and investor conversationsBabies and Blenders can disarm scepticism; the incongruity of a scrappy team tackling a massive problem is inherently funny if framed correctly
Early TractionReal customer stories provide the raw material for surpriseThe critical detail to hide is often the customer's own words -- plant them early, detonate them at the close
GrowthInternal storytelling (all-hands, retrospectives) requires emotional rangeTeams fatigued by metrics need stories that make them laugh and then remind them why the work matters
ScaleSurprise becomes harder as company narratives calcifyThe greatest emotional impact at scale comes from revealing something the audience assumed they already knew about the company -- and showing them they were wrong

At the idea stage, the founder's own biography is often the richest source of surprise. The audience expects a pitch about a market opportunity; the founder reveals a deeply personal reason for caring. The mismatch between expectation and reality is the mechanism. At scale, the mechanism is the same, but the source shifts: the surprise comes from customer stories, employee stories, or data that contradicts the company's own assumptions.


Output Template

markdown
# Emotional Impact Design

## Story / Narrative
[One-sentence summary]

## Target Emotional Response
[What should the audience feel at the climax? Tears, laughter, awe, resolve?]

## Surprise Architecture
- **Apparent story:** [What the audience believes the story is about]
- **Actual story:** [What the story is really about -- revealed at the end]
- **Contrast built before surprise:** [The emotional state the audience is in immediately before the reveal]
- **Critical detail hidden:** [The bomb -- what it is, where it is planted, how it is camouflaged]

## Humour Placement
| Moment | Technique | Strategic Purpose |
|--------|-----------|-------------------|
| [Opening] | [Milk Cans / Babies & Blenders / other] | [Signal competence / claim floor / reassure] |
| [Before blow] | [Technique] | [Heighten contrast] |
| [After tension] | [Technique] | [Allow breath / reset] |
| [Near hidden detail] | [Technique] | [Camouflage critical information] |

## Milk Cans and a Baseball (if applicable)
- **Tower (setup details in order):** [List each milk can]
- **Ball (funniest word, said last):** [The punchline word]

## Babies and Blenders (if applicable)
- **Element A (expected):** [The normal thing]
- **Element B (incongruous):** [The unexpected pairing]

## Landing (Final Sentences)
[Heart, not humour. What is the vulnerable, meaningful, or universally true statement the story ends on?]

Related Skills

  • Building Story Stakes -- Stakes create the tension that surprise releases; the Backpack and Hourglass techniques are direct amplifiers of emotional impact.
  • Storytelling Truth and Vividness -- Cinema of the Mind ensures the audience can see the scene where the surprise detonates; a surprise delivered in a locationless void is a thesis statement in disguise.
  • Story Performance and Delivery -- Timing, tense shifts, and vocal control determine whether a Milk Cans tower lands or collapses; performance is where structural humour becomes actual laughter.
  • Storytelling for Leaders -- Leaders must calibrate emotional impact for context: a board meeting and an all-hands address demand different emotional registers.
  • What Is a Story -- The transformation requirement defines what kind of emotional impact is possible; only genuine change in the storyteller produces genuine feeling in the audience.
  • Reader Psychology -- The cognitive science of how audiences process information explains why surprise works: it violates established expectations, forcing deeper processing and stronger emotional encoding.

Frequently asked questions

What does the Emotional Impact In Stories AI skill do?

Explains the singular mechanism for making audiences cry (surprise, not sadness) and two named techniques for making them laugh (Milk Cans and Baseballs, Babies and Blenders). Applies when a founder is crafting a keynote, investor narrative, brand story, or any communication designed to move an audience emotionally. Use when a story feels informative but flat, when humour falls short, or when a narrative needs to land in the heart rather than the head.

Why use Emotional Impact In Stories on TypingMind?

Because you install it once and use it with any model. Emotional Impact In Stories is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Emotional Impact In Stories in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/emotional-impact-in-stories. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Emotional Impact In Stories?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Emotional Impact In Stories?

As many as you like. As long as a model supports skills, you can use Emotional Impact In Stories with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Emotional Impact In Stories AI skill free?

Yes. It is published on GitHub by fatihguner under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇