presentation-outline — Claude Code skill: use and install
Builds a Markdown presentation outline with sections, statement slides, and a clear arc. Use it when planning a new deck or shaping a talk before slide work.
MIT 190 installs ★ 17 updated 2026-02-19
npx skills add aaronvanston/skills-presentations --skill presentation-outline -a claude-codeWhat presentation-outline does
This skill turns a topic into a presentation plan with a clear narrative arc. It maps the material into an opening, context or problem, core sections, and a closing. The outline can include goals, section dividers, statement slides, data, code, frameworks, quotes, resources, and Q&A.
It is designed for live presenting, where a slide starts a conversation instead of carrying the whole script. Major sections receive accent colors, and a density review helps remove slides that do not earn a place. A typical structure uses 5-7 sections, while the number of core parts changes with the subject.
The workflow starts by asking for the audience, purpose, and setting, including live or async delivery. The result is Markdown that can be turned into slides. In Claude Code, the skill file is installed at ~/.claude/skills/presentation-outline/SKILL.md.
What it helps with
- turn a presentation topic into a deck outline
- split a talk into sections and slides
- write strong headlines for key slides
- add dividers, goals, and closing content
- trim slides from an overly dense plan
Example prompts for the agent
- Outline a live presentation about moving from a monolith to services.
- Turn this topic into sections with statement slides, dividers, and a closing Q&A.
- Review my talk structure and remove slides that do not earn their place.
How to install presentation-outline
1Skills CLI (Vercel)
npx skills add aaronvanston/skills-presentations --skill presentation-outline -a claude-code2Manually: put the files in place
~/.claude/skills/presentation-outline/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/presentation-outline/
1Skills CLI (Vercel)
npx skills add aaronvanston/skills-presentations --skill presentation-outline -a codex2Manually: put the files in place
.agents/skills/presentation-outline/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aaronvanston/skills-presentations --skill presentation-outline -a cursor2Manually: put the files in place
.cursor/skills/presentation-outline/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aaronvanston/skills-presentations skills/presentation-outline2Manually: put the files in place
.github/skills/presentation-outline/SKILL.md1Skills CLI (Vercel)
npx skills add aaronvanston/skills-presentations --skill presentation-outline -a gemini-cli2Platform CLI
gemini skills install https://github.com/aaronvanston/skills-presentations --path skills/presentation-outlineManually: put the files in place
.devin/skills/presentation-outline/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aaronvanston/skills-presentations --skill presentation-outline -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about presentation-outline
How do I install presentation-outline in Claude Code?
Run npx skills add aaronvanston/skills-presentations --skill presentation-outline -a claude-code, then check ~/.claude/skills/presentation-outline/SKILL.md.
What does presentation-outline do?
The skill creates a Markdown presentation plan with a narrative arc, section structure, slide types, and closing material. The outline is ready to turn into slides.
What should I provide before presentation-outline creates an outline?
Its workflow starts with the audience, purpose, and delivery setting, such as live or async. It then identifies the key messages and maps the presentation arc.
Source text
SKILL.md · MIT
--- name: presentation-outline description: Generate structured presentation outlines with bold statement slides, section dividers, and clear narrative arcs. Use when starting a new presentation, planning a deck structure, or asking "outline a presentation about...", "structure a deck for...", or "create a presentation flow for...". Outputs markdown outlines ready to translate into slides. --- # Presentation Outline Generate presentation structures following a proven flow pattern with bold, minimal slides designed for live presenting. ## Core Principles - **Slides are conversation starters, not scripts** — each slide prompts discussion - **Bold statements over explanations** — headlines that land, not sentences that explain - **Breathing room** — fewer slides with more impact beats many dense slides - **Clear sections** — the audience should always know where they are - **Section colors** — each major section gets its own accent color to reinforce structure ## Standard Flow The base arc adapts to the content. A typical presentation follows 5-7 sections: ``` 1. OPENING (color: teal) - Title slide (topic + subtitle) - Goals/agenda (3 key takeaways max) 2. CONTEXT / THE PROBLEM (color: red) - Current state / where we are today - The tension or question to resolve 3-5. CORE SECTIONS (colors: purple, amber, green, blue) - Section dividers between major topics - 3-5 content slides per section - Mix of statement, data, code, framework, and quote slides 6. CLOSING (color: teal) - Recap (one-liner per section) - Resources - Q&A ``` Sections can expand or contract — a complex topic might have 4 core sections, a focused talk might have 2. ## Slide Types | Type | When to use | Example | |------|-------------|---------| | **Statement** | Land a key point | "Speed is a feature" | | **Big statement** | Maximum impact, one idea | "AI has no memory" | | **Question** | Create tension | "What would we do differently?" | | **Section divider** | Signal topic shift | "Where we play" | | **Goals** | Set expectations | "Goals for today" | | **Data** | Prove with numbers | "3x growth in 6 months" | | **Code** | Show implementation | Syntax-highlighted code block | | **Framework** | Show a model or list | Do's and don'ts, comparison | | **Quote** | Borrow authority | "What got you here won't get you there" | | **Recap** | Summarize before close | "Recap" | | **Resources** | Link references | Grouped by section | | **Next steps** | Drive action | "Where to from here?" | ## Output Format ```markdown # [Presentation Title] [One-line purpose] --- ## 1. Opening **Section color:** teal ### Slide 1: Title - **Headline:** [Title] - **Subtitle:** [Context or date] ### Slide 2: Goals for today - **Headline:** Goals for today - **Points:** - [Takeaway 1] — [Brief explanation] - [Takeaway 2] — [Brief explanation] - [Takeaway 3] — [Brief explanation] --- ## 2. [Section Name] **Section color:** [color] ### Slide 3: Section divider - **Type:** Section divider - **Headline:** [Section title] ### Slide 4: [Slide purpose] - **Type:** [Statement/Big statement/Data/Code/etc.] - **Headline:** [Bold headline] - **Supporting:** [1-2 sentences or bullets] --- ## X. Closing **Section color:** teal ### Slide N: Recap - **Headline:** Recap - **Points:** [One-liner per section] ### Slide N+1: Resources - **Type:** Resources - **References:** [Grouped by section] ### Slide N+2: Q&A ``` ## Workflow 1. **Ask about context** — audience, purpose, setting (live vs. async) 2. **Identify key messages** — what 3 things must land? 3. **Map the arc** — Opening → Problem/Context → Core sections → Close 4. **Assign section colors** — one color per major section 5. **Draft outline** — use the format above 6. **Review density** — cut slides that don't earn their place
© aaronvanston · MIT · aaronvanston/skills-presentations