Outline a presentation as one idea per slide before building any actual slides.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add black141312/ada --skill slide-outline --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Slide Outline?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/black141312-slide-outline)More formats (shields.io, HTML) on the badges page.
---
name: slide-outline
description: Outline a presentation as one idea per slide before building any actual slides.
category: pptx
---
# Slide Outline
Always reach for this before generating a deck. A tight outline prevents bloated, unfocused slides and makes the build step mechanical.
1. Pin down the single goal of the talk and the one action or belief you want the audience to leave with.
2. Identify the audience and time budget (roughly 1-2 minutes per content slide) to bound the slide count.
3. List each slide as a one-line takeaway headline — the assertion, not the topic ("Churn dropped 30% after onboarding redesign", not "Churn").
4. Under each headline note the supporting evidence: a stat, chart, image, or 2-3 bullets — nothing more.
5. Order for narrative flow (hook → context → core argument → evidence → call to action) and check each slide earns its place.
6. Review the outline with the user, then hand it to pptx-deck or pptx-from-markdown to build.
## Rules
- One idea per slide; if a headline contains "and", split it into two slides.
- Headlines are full assertions, not topic labels.
- Keep supporting points to 3 or fewer per slide at the outline stage.
- Cut any slide that doesn't advance the single goal.
- Settle structure and message in the outline; defer all visual styling to the build.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.