Storytelling logo

Storytelling

Community
artemnovitckii
storytelling

Use when writing or auditing talking-head / narrative / "yap" content — reel scripts, video scripts, story-driven posts, any piece where someone talks to camera or tells a story. The hook stops the scroll; storytelling holds the watch after it. Not for pure tactical demos or bare listicles with no through-line.

Overview

Publisherartemnovitckii
Repositorycontent-skills
Skill namestorytelling
Stars
118
Forks
25
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 artemnovitckii on GitHub. Read the source before you install it.

Installation

Install the Storytelling 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/artemnovitckii/content-skills/tree/master/storytelling
  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/artemnovitckii/content-skills.git /tmp/content-skills
mkdir -p .claude/skills
cp -r /tmp/content-skills/storytelling .claude/skills/storytelling
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

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

Storytelling

The hook earns the first 2 seconds. Storytelling earns every second after. This skill is the craft of holding attention across the body of a spoken or narrative piece — so the viewer who stopped scrolling actually finishes, and wants to share.

Six techniques. The first four do most of the work; the last two are delivery and handoff.

When this fires

  • Always, on any talking-head / narrative / opinion / story-driven content (most reels, all long-form, founder stories, hot takes).
  • The Dance and Rhythm apply even to tutorials and listicles — any content with a through-line benefits from open loops and varied cadence.
  • Direction and Story Lens shine most on story/opinion pieces — where there's a narrative or a take to angle.
  • Skip only for pure mechanical demos with zero narration ("watch me click this").

Before you write: use real material, never invent

Pull the actual beats from your own real notes, or ask the person whose story it is. Never fabricate biography — invented founder stories, fake numbers, or imagined events on someone's real account destroy the exact trust this content is built to earn. If you don't have the real beats, get them first. Structure is this skill's job; the truth is yours.


1. The Dance — context vs. conflict (the engine)

Great stories alternate context (the character is doing something) and conflict (oh no, a complication). Conflict opens a loop in the brain; context closes it — then opens the next. That dance is what keeps a viewer locked in, in a feature film or a 30-second reel.

The tactical rule (from the South Park writers): between every beat, the connector should be BUT or THEREFORE — never "and then." "And then" piles detail on detail with no tension and the viewer leaves. "But/therefore" creates the open conflict loops.

Weak — "and then" piling:

My rent doubled and then enrollment dropped and then I almost closed and then I tried a free class and then it sold out and then I added more and then now I'm booked.

Strong — but/therefore loops:

My rent doubled. THEREFORE I was three months from closing. BUT I had all these empty evening slots. THEREFORE I tried one free date-night class — BUT I had no idea if a single person would show. (loop held open…) Twelve couples booked it in a day.

Stack several of these in the first 30 seconds. Each "but" is a head-fake that keeps the storyline moving. When you outline, literally write the beats and force a "but" or "therefore" between each — if "and then" fits, the beat is boring; rewrite it.

2. Direction — write the end first

The best place to start a story is the end. Decide where you're taking the viewer, then work backward to build the dance in the middle.

The last line is the "last dab": make it so memorable that if someone heard only that line, they'd share it. In short-form the video loops, so the last line is secretly the setup for the first line on replay — write it to hand off into the hook.

Tactic: write the first line and the last line first. Leave the middle blank. Then fill it with but/therefore beats that earn that ending.

  • Weak ending: "…and now we're fully booked. Follow for more!"
  • Last dab: "I stopped selling pottery and started selling the night out — and that's the only reason this place still exists."

3. Story Lens — your unique angle

A topic isn't enough; dozens of people cover the same topic. The lens is your unique prism on it — the same white light, bent differently. Finding the uncommon lens is how you become a category of one instead of one more version of the same video.

For any topic, list the obvious lenses first, then push past them:

  • Topic: a celebrity at a big event. Obvious lens: what they wore. Less common: a prediction. Rarest: the business impact they drove — the angle nobody else took.
  • Topic: your studio's comeback. Obvious: "I almost quit, then it worked out." Sharper lens: "the thing that saved my business is the thing I was embarrassed to sell."

How to generate a non-obvious lens (the "push past" is the hard part — use these moves):

  • Invert the villain. The obvious villain (the rent, the algorithm, the competitor) usually isn't the real one. What if the real villain was your own assumption?
  • Find the asset in the failure. The thing you were embarrassed by, or saw as proof you were losing, is often the actual product (the empty slots, the weird niche, the "too small" audience).
  • Jump to the second-order effect. Don't cover the event — cover what it quietly caused that nobody's connecting.
  • Switch the POV. Tell it from the angle no one takes (the customer's, the loser's, the thing's).
  • Flip the cost/benefit. What everyone calls the win was actually the cost, or vice versa.

Pick the lens before writing — it changes every line after.

4. Rhythm — write music, not monotony

Sentences of the same length, in a row, drone. The ear gets bored and the viewer churns. Vary it: short. Then medium. Then, once in a while, a longer sentence that builds with energy and rolls to a close. That variation is what makes writing sing.

Tactic: write every sentence on its own line. Look straight down the left edge. If the line endings make a jagged edge, your lengths vary — good. If they all stop at about the same place, it's monotonous — break some up, run some together. (The jagged edge is a proxy for spoken rhythm — the real test is reading it aloud and hearing the variation in breath, not just counting words.)

It sold out. Couples loved it — two people, one wheel, clay everywhere, laughing. So I added more.

Short. Long. Short. That's the music.

5. Tone — talk to one person

The creators who feel like they're in the room with you win. The way to get there: write and film as if you're talking to one close friend, not "an audience." Type the script like a text or a voice note to that one person. (Tape their photo under the lens if it helps.)

Match this to your actual voice — if you have a voice file (see the voice-dna skill in this pack), read it for how you talk to a friend. Conversational, direct, no performing. If a line sounds like a speech, rewrite it as something you'd actually say.

6. The Hook — handoff to viral-hooks

The hook is left for last here on purpose: it's critical, but it's a separate skill. Use the viral-hooks skill to write/stop-test the opening line. Two things storytelling needs from the hook:

  • The first line must be punchy and indicative of the plot — not "wait till you see this."
  • For video, lead with a visual hook (show while you tell — eyes perceive faster than ears).

Don't duplicate hook mechanics here; call viral-hooks.

Founder / personal stories are sanctioned I-framed. The viral-hooks skill flags creator-POV "I" framing as a relevance killer — but a first-person founder story on the owner's own account is the exception it allows. Don't force an awkward "you" pivot the genre rejects. The relevance comes from universal resonance (the viewer recognizes their own situation in yours), not from literally saying "you." Make sure the I-story lands on a feeling or lesson the viewer shares.

Length budget (the one hard constraint): spoken delivery runs ~2 words/second. So a 30s reel ≈ 60-75 words, 45s ≈ 110-130 words, 60s ≈ 150-170 words. Write to the runtime you asked for — craft-per-line doesn't matter if the script runs 20 seconds long. Cut beats, not the lens or the last dab.


Writing mode (drafting a script)

  1. Lens — pick the unique angle before anything else (§3).
  2. Direction — write a working-draft first line and the last-dab line; leave the middle empty (§2). (The first line here is a placeholder to aim at — step 6 hardens it into the real hook.)
  3. Dance — fill the middle with but/therefore beats; kill every "and then" (§1).
  4. Rhythm — one sentence per line; check for the jagged edge; vary lengths (§4).
  5. Tone — read it aloud as if to one friend; rewrite anything that sounds performed (§5).
  6. Hook — finalize the opener via viral-hooks (§6), replacing the step-2 working draft.
  7. Length — trim to the runtime budget (§6): ~2 words/sec. Cut beats, keep the lens and last dab.

Audit mode (checking a draft)

Score and flag with the specific offending line:

  • Dance: count the "and then" / detail-piling beats with no tension → flag each; rewrite as but/therefore.
  • Direction: is the last line a shareable last dab that loops, or does it trail off / end on a generic CTA? → flag.
  • Lens: is the angle the obvious one anyone would take? → flag, propose a sharper lens.
  • Rhythm: are sentences monotonously similar in length? → flag the flat stretch.
  • Tone: any line that sounds like a speech, not a friend? → flag, rewrite.

The checklist (every narrative piece)

  • Real beats (from your own notes), nothing invented?
  • A unique lens, not the obvious angle?
  • First + last line written first; last line is a shareable "last dab" that loops?
  • But/therefore between beats, several open loops in the first 30s — zero "and then"?
  • Jagged edge — varied sentence lengths?
  • Sounds like you talking to one friend?
  • Hook handled by viral-hooks (punchy, plot-indicative, visual for video)?

Common mistakes

MistakeWhy it fails
"And then… and then…" beatsNo tension, no open loops — the viewer churns mid-body
Generic transformation arc"I struggled, then I succeeded" is everyone's story; the lens is what makes it yours
Trailing-off ending / "follow for more"Wastes the last dab — and in a loop, wastes the re-hook
Flat rhythm (all same-length sentences)Drones; subconsciously pushes the viewer to the next video
Performing instead of talkingBreaks the in-the-room intimacy; people feel sold-to and leave
Inventing story details to fill the arcFabricated authenticity is the fastest way to lose a real audience

Frequently asked questions

What does the Storytelling AI skill do?

Use when writing or auditing talking-head / narrative / "yap" content — reel scripts, video scripts, story-driven posts, any piece where someone talks to camera or tells a story. The hook stops the scroll; storytelling holds the watch after it. Not for pure tactical demos or bare listicles with no through-line.

Why use Storytelling on TypingMind?

Because you install it once and use it with any model. Storytelling 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 Storytelling in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/artemnovitckii/content-skills/tree/master/storytelling. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Storytelling?

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 Storytelling?

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

Is the Storytelling AI skill free?

Yes. It is published on GitHub by artemnovitckii 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 👇