Agent skill

Storyline Builder

by sruthir28 in sruthir28/enterprise-ai-skills

McKinsey-style storyline framework for building presentation decks.

MITAuto-check passedBusiness, Finance & HR

Install Storyline Builder

skills CLI
$ npx skills add sruthir28/enterprise-ai-skills --skill storyline-builder -a claude-code

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

GitHub CLI
$ gh skill install sruthir28/enterprise-ai-skills storyline-builder --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/sruthir28/enterprise-ai-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/storyline-builder .claude/skills/storyline-builder && 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
storyline-builder
GitHub stars
148
Used in
1 other repo
Token cost
~1.9k tokens
SKILL.md length
591 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

McKinsey-style storyline framework for building presentation decks.

  • Works in 3 steps: Market Strategy / Pitch Deck → Internal Problem-Solving (Issue Tree… → Project Roadmap / Implementation Plan
  • Users need to structure presentations
  • SKILL.md covers What is a Storyline?, Core Principles, Storyline Templates by Situation and How to Build a Storyline, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Storyline Builder is an agent skill from sruthir28/enterprise-ai-skills. McKinsey-style storyline framework for building presentation decks. Use when users need to structure presentations, pitch decks, or strategic communications. Creates logical flow where each storyline becomes a slide title, progressing from problem to solution.

Its SKILL.md is about 1.9k 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 Business, Finance & HR, covering Slides and decks and Fundraising and pitch decks. The repository describes itself as: Open-source AI skills for enterprise professionals. McKinsey consulting frameworks, PM workflows, and practical tools. Currently for Claude, expanding to other LLMs. The licence is MIT.

When your agent uses it

  • Users need to structure presentations
  • Strategic communications

Example prompts

  • “/storyline-builder”

Workflow steps

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

  1. Market Strategy / Pitch Deck
  2. Internal Problem-Solving (Issue Tree Format)
  3. Project Roadmap / Implementation Plan

What it can do on your machine

Read from SKILL.md and the folder at commit ae8fe60. 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

Storyline Builder loads about 1.9k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 591 words of instructions outside code blocks.

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

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 sruthir28/enterprise-ai-skills at commit ae8fe60, republished under its MIT licence (© sruthir28). 591 words, ~1,897 tokens.

Download SKILL.mdSave it as .claude/skills/storyline-builder/SKILL.md (or your agent's skills folder).
name
storyline-builder
description
McKinsey-style storyline framework for building presentation decks. Use when users need to structure presentations, pitch decks, or strategic communications. Creates logical flow where each storyline becomes a slide title, progressing from problem to solution.

Storyline Builder

A structured approach to building presentation storylines where each line becomes one slide title, creating a logical narrative flow.

What is a Storyline?

A storyline is the backbone of a presentation - a sequence of messages that tells a complete story. Each line in the storyline becomes one slide title in the final deck.

Key characteristics:

  • Each line = one slide title (action-oriented message)
  • Logical flow from problem → context → analysis → solution
  • Slide titles are the message, not topics
  • Reader should understand the story from titles alone

Core Principles

Action Titles

  • Titles state the finding, not the topic
  • Good: "Market grew 40% while revenue declined 5%"
  • Bad: "Market Analysis"

Logical Progression

  • Paint the problem or opportunity
  • Provide context (market, competitive landscape)
  • Show data to prove/disprove hypotheses
  • Present solution and next steps

Story Flow

  • Problem → Context → Analysis → Solution → Roadmap
  • Each slide builds on the previous
  • Clear beginning, middle, end

Storyline Templates by Situation

1. Market Strategy / Pitch Deck

Flow: Market opportunity → Competitive position → Product strategy → Go-forward plan

Storyline:
1. [Market name] represents $XXB opportunity growing at XX% CAGR
2. We operate in [specific segment] worth $XXB with XX% growth
3. Top 3 competitors generate $XXM-XXB revenue growing XX-XX% annually
4. Our revenue of $XXM positions us as [rank/position] with XX% growth
5. [Product name] addresses [use case] for [target customer segment]
6. Top 10 customers span [industries/sectors], XX% enterprise vs XX% SMB split
7. Pricing structured as [model type] with $XX average contract value
8. Product differentiation built on [technology/approach] vs competitors
9. Key competitive advantages: [advantage 1], [advantage 2], [advantage 3]
10. Three growth opportunities identified: [opp 1], [opp 2], [opp 3]
11. Focus on [priority opportunity] based on market size and competitive position
12. 18-month roadmap prioritizes [capability 1], [capability 2], [capability 3]
2. Internal Problem-Solving (Issue Tree Format)

Flow: Problem framing → Root cause analysis → Solution options → Prioritization → Next steps

Storyline:
1. [Problem statement] - current state at XX vs target of XX
2. Problem driven by three factors: [factor 1], [factor 2], [factor 3]
3. [Factor 1] contributes $XXM impact (XX% of total problem)
4. [Factor 2] contributes $XXM impact (XX% of total problem)
5. [Factor 3] contributes $XXM impact (XX% of total problem)
6. Root cause analysis reveals [key insight from data]
7. Three solution approaches identified to address root causes
8. Solution 1: [approach] - XX% impact, $XXM investment, XX weeks
9. Solution 2: [approach] - XX% impact, $XXM investment, XX weeks
10. Solution 3: [approach] - XX% impact, $XXM investment, XX weeks
11. Prioritize [solution X] based on impact/effort analysis
12. Implementation roadmap: [Phase 1 by date], [Phase 2 by date], [Phase 3 by date]
13. Success metrics: [metric 1], [metric 2], [metric 3] tracked [frequency]
3. Project Roadmap / Implementation Plan

Flow: Approach → Phases → Activities → Timeline → Success criteria

Storyline:
1. Project objective: [goal statement with measurable outcome]
2. Four-phase approach over XX weeks: Discovery → Design → Build → Launch
3. Project roadmap spans XX weeks with clear owners and milestones:
   - Phase 1 (Weeks 1-X): User research - XX interviews across [segments] | Owner: [role]
   - Phase 2 (Weeks X-X): Solution design - Define stories, sprint planning | Owner: [role]
   - Phase 3 (Weeks X-X): MVP build - [features] across XX sprints | Owner: [role]
   - Phase 4 (Weeks X-X): Launch - Onboard XX customers | Owner: [role]
4. Core team of XX across [# domains]: PM, Design, Engineering, [other] - Gap: Need [X more roles] and $XXK investment
5. Success criteria: [metric 1] = XX, [metric 2] = XX by [date]
6. ROI measurement: Track [business metric] over XX months

How to Build a Storyline

Step 1: Identify the situation type

  • Market/strategy deck?
  • Problem-solving presentation?
  • Project roadmap?
  • Choose appropriate template

Step 2: Customize the flow

  • Replace placeholders with specific content
  • Add or remove slides based on story needs
  • Maintain logical progression

Step 3: Write action titles

  • Each line should be a complete message
  • Include data points and specifics
  • Test: Can someone understand your story from titles alone?

Step 4: Verify flow

  • Does it progress logically?
  • Are there gaps in the logic?
  • Does it lead to clear next steps?

Step 5: Build slides

  • Each storyline becomes one slide
  • Slide title = storyline
  • Slide body supports the title message

Common Storyline Patterns

Problem-to-Solution Arc

Problem statement → Problem sizing → Root causes → 
Solution options → Recommendation → Implementation plan

Market-to-Strategy Arc

Market opportunity → Competitive landscape → Our position → 
Product strategy → Roadmap → Expected outcomes

Analysis-to-Action Arc

Key question → Hypotheses → Data analysis → 
Insights → Recommendations → Next steps

Usage Guidelines

When creating storyline:

  • Start with the end in mind (what decision/action needed?)
  • Use MECE principles to organize sections
  • Include quantitative support where possible
  • Make the "so what" clear at each step

When reviewing storyline:

  • Can you understand the full story from titles alone?
  • Is the logical flow clear?
  • Are titles action-oriented (not topics)?
  • Does it lead to clear conclusion/next steps?
  • Are data points specific (not vague)?
Show full SKILL.md (214 more words)Show less

Common Mistakes to Avoid

  • Topic titles: "Market Analysis" instead of "Market growing 40% CAGR"
  • Missing the "so what": Data without interpretation
  • Illogical jumps: Skipping steps in reasoning
  • Too granular: 50 slides when 15 would tell the story
  • No ending: Storyline trails off without clear next steps
  • Vague language: "Good performance" instead of "Revenue grew 25%"

Tips for Effective Storylines

Start with structure

  • Outline major sections first
  • Fill in detailed slides within each section
  • Typical deck: 15-25 slides for exec presentation

Consider executive summary upfront

  • Optional first slide summarizing key message
  • Useful for: Problem statement, recommendation, expected impact
  • Allows execs to get punchline immediately
  • Rest of deck provides supporting detail

Use parallel structure

  • Keep similar sections in similar format
  • Makes story easier to follow
  • Example: If slide 5 is "Factor 1: $XXM impact", slide 6 should be "Factor 2: $XXM impact"

Include signposts

  • Use section breaks or agenda slides
  • Help audience know where they are in story
  • Example: "Three drivers of the problem" followed by three slides

Build to the punchline

  • Lead audience through your thinking
  • Don't jump to recommendations without proof
  • But don't bury the lede - executive summary upfront often works

Iterate

  • First draft won't be perfect
  • Review logical flow
  • Get feedback before building full slides
  • Much easier to reorganize storyline than finished slides

© sruthir28, 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 storyline-builder of sruthir28/enterprise-ai-skills.

Open the folder on GitHubat commit ae8fe60

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sruthir28/enterprise-ai-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

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

Storyline Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Storyline Builder this skillsruthir28/enterprise-ai-skills1481 repos~1.9kAutomated safety check: PassMIT
Replit Decksanqiufong/slides-from-anything1321 repos~2.9kAutomated safety check: PassApache-2.0
Deckleewayworks/guochuang-gps106—~546Automated safety check: PassMIT
HTML Ppt Creatorcigery-useio/useio-skills104—~2.4kAutomated safety check: PassNone
Pitch Deckemotixco/claude-skills-founder540—~1.1kAutomated safety check: PassMIT
Pitch Deckooiyeefei/ccc495—~920Automated safety check: PassMIT

Similar skills

  • Replit Deck

    sanqiufong/slides-from-anything

    Single-file horizontal-swipe HTML deck in the style of Replit Slides's landing-page template gallery.

    132 GitHub starsUsed in 1 repo~2.9k tokens
    Business, Finance & HRAuto-check passed
  • Deck

    leewayworks/guochuang-gps

    A skill your agent uses when outlining, reviewing, or rehearsing a Guochuang pitch deck, project-book presentation, slide narrative, or visual evidence sequence.

    106 GitHub stars~546 tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed
  • HTML Ppt Creator

    cigery-useio/useio-skills

    HTML 幻灯片制作技能,生成专业级静态 HTML 演示文稿。内置 36 套主题、15 套完整 deck 模板、31 种页面布局、47 个动效,以及演讲者模式(逐字稿提词器+计时器)。最终通过 bundle.js 打包为单 HTML 文件,可拷贝发送给他人。当用户要求做 PPT、幻灯片、演讲稿、分享 slides、pitch deck、小红书图文等时触发。

    104 GitHub stars~2.4k tokensUpdated 17 days ago
    Business, Finance & HRAuto-check passed
  • Pitch Deck

    emotixco/claude-skills-founder

    Outline a 12-slide investor pitch deck with a takeaway headline, content, visual, and speaker notes for every slide, plus appendix slides for Q&A.

    540 GitHub stars~1.1k tokensUpdated 3 days ago
    Business, Finance & HRAuto-check passed
  • Pitch Deck

    ooiyeefei/ccc

    Build a pitch deck as one self-contained HTML file (keyboard and click navigation, staggered slide-entry animations, a persistent brand mark, cited numbers with real links), write its timed…

    495 GitHub stars~920 tokensUpdated 2 mo ago
    Business, Finance & HRAuto-check passed
  • Ib Deck

    daloopa/investing

    Generate an institutional-grade investment banking pitch deck (HTML → PDF)

    489 GitHub stars~1.4k tokensUpdated 3 days ago
    Business, Finance & HRAuto-check passed

More from sruthir28/enterprise-ai-skills

All 14 skills in this repo
  • AI Use Case Scorer

    sruthir28/enterprise-ai-skills

    Score and prioritize AI use cases for your own job. An agent skill from sruthir28/enterprise-ai-skills.

    148 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Decision Memo Builder

    sruthir28/enterprise-ai-skills

    Builds a 1-page decision memo (context → options → recommendation → risks → ask) enforcing McKinsey memo DNA — brutal brevity, SCP storyline clarity, decision-forcing output, evidence density.

    148 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Deck Pipeline

    sruthir28/enterprise-ai-skills

    Multi-agent pipeline that builds a polished presentation deck from a single topic.

    148 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Issue Tree Builder

    sruthir28/enterprise-ai-skills

    McKinsey-style issue tree framework for breaking down complex problems into MECE (Mutually Exclusive, Collectively Exhaustive) components.

    148 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Mckinsey Charts

    sruthir28/enterprise-ai-skills

    Generate McKinsey-style consulting charts as native python-pptx objects (editable inside PowerPoint).

    148 GitHub stars~999 tokensUpdated 1 mo ago
    Auto-check passed
  • Scpr Framework

    sruthir28/enterprise-ai-skills

    SCPR (Situation-Complication-Problem-Recommendation) framework for structured problem solving and executive communication.

    148 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Storyline Builder

What does Storyline Builder do?

McKinsey-style storyline framework for building presentation decks. Storyline Builder is an agent skill from sruthir28/enterprise-ai-skills. McKinsey-style storyline framework for building presentation decks.

When should I use Storyline Builder?

Storyline Builder fits situations like: users need to structure presentations; strategic communications.

How do I install Storyline Builder in Claude Code?

Run `npx skills add sruthir28/enterprise-ai-skills --skill storyline-builder -a claude-code`. Or copy the skill folder (storyline-builder in sruthir28/enterprise-ai-skills) into .claude/skills/storyline-builder in your project. Claude Code loads it when a task matches its description.

How do I install Storyline Builder in Codex?

Run `npx skills add sruthir28/enterprise-ai-skills --skill storyline-builder -a codex`. Or copy the skill folder (storyline-builder in sruthir28/enterprise-ai-skills) into .agents/skills/storyline-builder in your project. Codex loads it when a task matches its description.

Can I use Storyline Builder 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 sruthir28/enterprise-ai-skills --skill storyline-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/storyline-builder, .gemini/skills/storyline-builder, .github/skills/storyline-builder and .opencode/skills/storyline-builder in your project.

What does Storyline Builder need to run?

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

Does Storyline Builder 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 Storyline Builder 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 Storyline Builder use?

Storyline Builder 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 Storyline Builder use?

About 1.9k tokens (SKILL.md is roughly 7.6k 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 Storyline Builder?

Skills that share tags, products or a category with Storyline Builder: Replit Deck (sanqiufong/slides-from-anything, 132 stars), Deck (leewayworks/guochuang-gps, 106 stars), HTML Ppt Creator (cigery-useio/useio-skills, 104 stars) and Pitch Deck (emotixco/claude-skills-founder, 540 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Storyline Builder?

sruthir28 (a GitHub user) maintains it in sruthir28/enterprise-ai-skills, which has 148 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 1, 2026.

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