plugins/cache/nyldn-plugins/octo/9.30.0/skills/skill-deck/SKILL.md
Generate slide decks from briefs with optional multi-AI research. Use when: AUTOMATICALLY ACTIVATE when user requests:. "create a deck", "build slides", "make a presentation". "generate a pitch deck", "create board presentation"
npx skillsauth add moliboy5000/.claude skill-deckInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate professional slide decks from briefs with optional research, outline approval, and PPTX export.
The document-skills plugin MUST be installed for PPTX rendering:
/plugin list | grep document-skills
If not installed, tell the user:
The document-skills plugin is required for PPTX generation.
Install it with: /plugin install document-skills@anthropic-agent-skills
Parse the user's topic and description. Use AskUserQuestion to clarify:
Question 1 - Audience:
Question 2 - Slide count target:
Question 3 - Tone:
If the user already provided clear context (e.g., "10-slide investor pitch deck about our Series A"), skip questions where the answer is obvious.
If the topic needs external research or context gathering:
Explore or general-purpose subagent to gather relevant information/octo:discover [topic] first, then /octo:deck to build slides from the results"This step is OPTIONAL. Many decks are built from the user's own knowledge or existing documents.
Build a slide-by-slide outline in markdown format. Structure:
## Slide 1: [Title Slide]
- Presentation title
- Subtitle / Date / Author
## Slide 2: [Agenda / Overview]
- Key topics to cover
## Slide 3: [First Content Section]
- Bullet point 1
- Bullet point 2
- Bullet point 3
## Slide N: [Summary / Next Steps]
- Key takeaways
- Call to action
IMPORTANT: Present the outline to the user for approval using AskUserQuestion:
This is the wireframe gate — the user MUST approve the outline structure before PPTX generation.
Once the outline is approved:
document-skills:pptx skill to convert the approved markdown outline to PowerPoint## heading becomes a slideExample filename: Series-A-Pitch-Deck-2026-02-14.pptx
Apply these when generating outlines:
Executives / Board:
Engineers / Technical:
Investors / Fundraising:
General / Mixed:
This skill works well in combination with:
/octo:discover [topic] — Research first, then build deck from findings/octo:docs — For converting existing markdown to other formats/octo:prd — Generate a PRD, then create a presentation summarizing it/octo:brainstorm — Brainstorm ideas, then structure into a deckUser: "Create a 10-slide deck about our Q1 results"
→ Step 1: Clarify audience (executives)
→ Step 2: Skip (user has the data)
→ Step 3: Generate outline, get approval
→ Step 4: Render PPTX
User: "Build a presentation about AI trends in healthcare"
→ Step 1: Clarify audience and scope
→ Step 2: Research using Task agents
→ Step 3: Generate outline from research, get approval
→ Step 4: Render PPTX
User: "I need a comprehensive investor deck about the autonomous vehicles market"
→ Suggest: "/octo:discover autonomous vehicles market" first
→ Then: "/octo:deck" using the research synthesis
Slide deck skill for claude-octopus v8.12.0+
development
Configure Claude Octopus providers and preferences. Use when: Use this skill when the user wants to "configure Claude Octopus", "setup octopus",. "configure providers", "set up API keys for octopus", or mentions octopus configuration.
tools
Zero-context implementation plans with bite-sized tasks. Use when: Use when you have a spec or requirements for a multi-step task.. Auto-invoke when user says "plan how to implement X", "create implementation plan", . "break down this feature into tasks".
content-media
Process screenshot-based UI/UX feedback to fix visual issues. Use when: AUTOMATICALLY ACTIVATE when user provides visual feedback:. "[Image X] The /settings should be Y". "[Image X] these button styles need to be fixed"
testing
Verify claims with actual evidence before declaring success — use to prevent false completion. Use when: Use when about to claim work is complete, fixed, or passing.. Auto-invoke before: commits, PRs, task completion, moving to next task.. ALWAYS use before expressing satisfaction ("Done!", "Fixed!", "All passing!").