ppt-superpower

Orchestrate multi-step PPT pipelines and route slide generation tasks.

8|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/SenseTime-FVG/sensenova-claw --skill ppt-superpower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ppt-superpower
Source: https://github.com/SenseTime-FVG/sensenova-claw/tree/main/.sensenova-claw/skills/ppt-superpower
Command: npx skills add https://github.com/SenseTime-FVG/sensenova-claw --skill ppt-superpower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes decision-making and routing for presentation creation so users do not have to manage complex multi-step PPT pipelines manually. It determines whether to create a new deck, continue an existing deck, or perform localized page or asset edits and then routes work to the appropriate downstream skills.

Core Features & Use Cases

  • Mode selection: Chooses the most appropriate mode among fast, guided, and surgical depending on user intent (one-shot generation, staged confirmation, or targeted repair).
  • Deck directory governance: Ensures a fixed, self-contained deck_dir with required subfolders and mandates creation of task-pack.json, info-pack.json, style-spec.json, and storyboard.json as canonical artifacts.
  • Routing and orchestration: Routes to downstream skills such as source analysis, task packing, storyboard, asset planning, page HTML generation, review, and final PPTX export based on triggers and artifact presence.
  • Safety and workflow rules: Enforces review-before-export, prevents writing intermediate outputs outside the deck_dir, and avoids skipping critical planning stages.
  • Use case: Create a full product launch deck, continue edits on a previously uploaded deck, or apply a surgical fix to a single slide's visuals or assets.

Quick Start

Create a new presentation deck for "AI product launch" and generate task-pack.json, style-spec.json, and storyboard.json in a new deck_dir while running in guided mode.

Frequently Asked Questions about ppt-superpower

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate multi-step PPT generation and routing decisions for a new deck?

Multi-step PPT generation is orchestrated by routing tasks across downstream skills, selecting fast, guided, or surgical modes based on your intent, and mandating canonical artifacts like storyboard.json and style-spec.json before final PPTX export.

What is the best way to apply targeted edits or asset planning to an existing presentation?

Targeted presentation edits use a surgical mode to perform localized page repairs or asset planning within a fixed deck directory, ensuring intermediate outputs remain self-contained and routing only to necessary downstream skills.

Do I need to manually create task-pack.json and storyboard.json before starting deck generation?

No, you do not need to manually create task-pack.json or storyboard.json, because the orchestration pipeline automatically produces these canonical artifacts inside the fixed deck directory during the workflow stages.

How does the presentation export workflow enforce review stages before generating a PPTX file?

The presentation export workflow enforces a strict review-before-export safety rule, preventing the final PPTX export from triggering until all upstream stages, including storyboard generation and asset planning, are fully completed and validated.

Can I use fast mode for one-shot deck generation instead of staged confirmation?

Yes, fast mode is specifically selected for one-shot deck generation when staged confirmation is unnecessary, whereas guided mode is chosen for staged workflows and surgical mode for targeted slide repairs.

Why must intermediate outputs be written inside a fixed deck directory during PPT creation?

Intermediate outputs must remain inside a fixed deck directory to maintain workflow safety, prevent file sprawl, and ensure downstream skills can reliably locate required artifacts like info-pack.json for routing and review.