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+
tools
MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).
development
DEFAULT PIPELINE for all tasks requiring execution. You (Claude) are the strategic orchestrator. Codex agents are your implementation army - hyper-focused coding specialists. Trigger on ANY task involving code, file modifications, codebase research, multi-step work, or implementation. This is NOT optional - Codex agents are the default for all execution work. Only skip if the user explicitly asks you to do something yourself.
development
This skill should be used when the user asks to analyze a UI screen recording and map interaction states into Figma. Trigger for requests such as "put video frames in Figma", "extract states from my recording", "map interactions from video to Figma", "analyze this screen recording", "create a storyboard from my video", "deconstruct this interaction in Figma", "annotate the UI states in my recording", or "pull the key moments from this video into Figma". Also trigger when the user references a video file (.mp4, .mov, .webm, .avi) together with Figma, design review, interaction analysis, prototypes, or UI states. The skill extracts key visual moments from a video, infers interaction triggers, and builds an annotated Figma Design storyboard using native Figma annotations and uploaded screenshot assets.
development
Generate a FigJam project plan board from a PRD plus codebase context. Interactive flow: research → propose sections → per-section deep research → per-section content + block-shape proposal → create FigJam → skeleton → fill → diagrams → wrap. Each content block (section, nested section, intro callout, table, multi-column text, sticky column, diagram section, metadata strip) has its own subskill reference file. Use when the user asks for 'project plan in FigJam', 'interactive project plan', '/generate-project-plan', or provides a PRD and wants per-section confirmation on content + rendering.