Agent skill

Storytelling

by artemnovitckii in artemnovitckii/content-skills

A skill your agent uses 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.

MITAuto-check passedWriting & Content

Install Storytelling

skills CLI
$ npx skills add artemnovitckii/content-skills --skill storytelling -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install artemnovitckii/content-skills storytelling --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/artemnovitckii/content-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/storytelling .claude/skills/storytelling && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
storytelling
GitHub stars
102
Token cost
~2.6k tokens
SKILL.md length
1,643 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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.

  • Works in 6 steps: The Dance — context vs. conflict (the… → Direction — write the end first → Story Lens — your unique angle → …
  • Auditing talking-head / narrative / yap content — reel scripts
  • SKILL.md covers When this fires, Before you write: use real…, 1. The Dance — context vs.… and 2. Direction — write the end…, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Storytelling is an agent skill from artemnovitckii/content-skills. 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.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Storytelling and Video scripts and shorts. The repository describes itself as: 5 Claude Code skills that fix Claude's writing: dumbify, storytelling, viral-hooks, anti-ai-writing, and a voice-dna build guide. MIT. The licence is MIT.

When your agent uses it

  • Auditing talking-head / narrative / yap content — reel scripts
  • Story-driven posts
  • Any piece where someone talks to camera

Example prompts

  • “/storytelling”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. The Dance — context vs. conflict (the engine)
  2. Direction — write the end first
  3. Story Lens — your unique angle
  4. Rhythm — write music, not monotony
  5. Tone — talk to one person
  6. The Hook — handoff to viral-hooks

What it can do on your machine

Read from SKILL.md and the folder at commit 1c6e909. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Storytelling loads about 2.6k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 1,643 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from artemnovitckii/content-skills at commit 1c6e909, republished under its MIT licence (© artemnovitckii). 1,643 words, ~2,622 tokens.

Download SKILL.mdSave it as .claude/skills/storytelling/SKILL.md (or your agent's skills folder).
name
storytelling
description
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.

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.

Show full SKILL.md (685 more words)Show less

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

© artemnovitckii, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in storytelling of artemnovitckii/content-skills.

Open the folder on GitHubat commit 1c6e909

Compare with similar skills

Storytelling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Storytelling compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Storytelling this skillartemnovitckii/content-skills102—~2.6kAutomated safety check: PassMIT
Pitch Craft Timed Scriptsooiyeefei/ccc495—~1.7kAutomated safety check: PassMIT
Script Writerailabs-393/ai-labs-claude-skills455—~4kAutomated safety check: PassMIT
Evidence-Grounded Video Writerliuluhaixiu/DaVinci-AutoEdit-Agent484—~711Automated safety check: PassMIT
Seedance Interview1370998960-del/https-github.com-Emily2040-seedance-2.0241—~2.6kAutomated safety check: PassMIT
60-Second Cinematic Story Directorkaruvanan/MiniMax-H3-Director-Cut-Studio132—~1.8kAutomated safety check: PassCustom licence

Similar skills

  • Writes or fixes spoken scripts that must fit a clock: demo voiceovers, deck narration and pitch speeches, with word budgets, storytelling rules and named trim points.

    495 GitHub stars~1.7k tokensUpdated 2 mo ago
    Writing & ContentAuto-check passed
  • Script Writer

    ailabs-393/ai-labs-claude-skills

    This skill should be used whenever users need YouTube video scripts written.

    455 GitHub stars~4k tokensUpdated 11 mo ago
    Writing & ContentAuto-check passed
  • Evidence-Grounded Video Writer

    liuluhaixiu/DaVinci-AutoEdit-Agent

    Writes video scripts, narration, titles and hooks from an approved media review, offers story directions first, and never invents footage, quotes or facts.

    484 GitHub stars~711 tokensUpdated 4 mo ago
    Media & CreativeAuto-check passed
  • Seedance Interview

    1370998960-del/https-github.com-Emily2040-seedance-2.0

    This skill should be used when the user has a vague Seedance 2.0 video idea and asks for creative guidance, story development, scene planning, a director interview, or help turning an undeveloped…

    241 GitHub stars~2.6k tokensUpdated 3 mo ago
    Media & CreativeAuto-check passed
  • 60-Second Cinematic Story Director

    karuvanan/MiniMax-H3-Director-Cut-Studio

    Adapts prose or rough story material into a roughly 60-second MiniMax H3 short with shot planning, Mandarin dialogue and voice-over, and a strong ending.

    132 GitHub stars~1.8k tokensUpdated today
    Media & CreativeAuto-check passed
  • Educational Content And How To

    social-media-skills/skills

    The teach-to-grow content type -- pick a genuinely useful topic, teach ONE thing completely, structure it as a clear lesson, keep it accurate, and route it to the right format.

    134 GitHub stars~1.9k tokensUpdated 9 days ago
    Media & CreativeAuto-check passed

More from artemnovitckii/content-skills

  • Anti AI Writing

    artemnovitckii/content-skills

    A skill your agent uses when writing or auditing any written content — captions, carousels, newsletters, threads, LinkedIn posts, long-form — and as the FINAL filter on every piece.

    102 GitHub stars~3k tokensUpdated 3 mo ago
    Auto-check passed
  • Dumbify

    artemnovitckii/content-skills

    A skill your agent uses when writing or auditing content that has to be easy to follow — explainer reels, teaching carousels, how-to scripts, any piece that teaches or explains something — or when a…

    102 GitHub stars~1.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Viral Hooks

    artemnovitckii/content-skills

    A skill your agent uses when writing or auditing the opening lines of any content — reel hooks, carousel slide 1, video intros, newsletter subject lines, tweet openers — or when a draft's opener…

    102 GitHub stars~2.6k tokensUpdated 3 mo ago
    Auto-check passed

Questions about Storytelling

What does Storytelling do?

A skill your agent uses 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. Storytelling is an agent skill from artemnovitckii/content-skills. 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.

When should I use Storytelling?

Storytelling fits situations like: auditing talking-head / narrative / yap content — reel scripts; story-driven posts; any piece where someone talks to camera.

How do I install Storytelling in Claude Code?

Run `npx skills add artemnovitckii/content-skills --skill storytelling -a claude-code`. Or copy the skill folder (storytelling in artemnovitckii/content-skills) into .claude/skills/storytelling in your project. Claude Code loads it when a task matches its description.

How do I install Storytelling in Codex?

Run `npx skills add artemnovitckii/content-skills --skill storytelling -a codex`. Or copy the skill folder (storytelling in artemnovitckii/content-skills) into .agents/skills/storytelling in your project. Codex loads it when a task matches its description.

Can I use Storytelling in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add artemnovitckii/content-skills --skill storytelling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/storytelling, .gemini/skills/storytelling, .github/skills/storytelling and .opencode/skills/storytelling in your project.

What does Storytelling need to run?

SKILL.md names no scripts, command-line tools or credentials: Storytelling is instructions for the agent only.

Does Storytelling access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Storytelling safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Storytelling use?

Storytelling is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Storytelling use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Storytelling?

Skills that share tags, products or a category with Storytelling: Pitch Craft Timed Scripts (ooiyeefei/ccc, 495 stars), Script Writer (ailabs-393/ai-labs-claude-skills, 455 stars), Evidence-Grounded Video Writer (liuluhaixiu/DaVinci-AutoEdit-Agent, 484 stars) and Seedance Interview (1370998960-del/https-github.com-Emily2040-seedance-2.0, 241 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Storytelling?

artemnovitckii (a GitHub user) maintains it in artemnovitckii/content-skills, which has 102 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on June 20, 2026.

Source: artemnovitckii/content-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.