Skills ppt-orchestra-skill
📦

ppt-orchestra-skill

Safe

Plan professional PowerPoint presentations

Creating consistent, visually varied presentations is difficult when working slide by slide. This skill plans layout, typography, and visual rules before generation, and provides quality checks to ensure professional results.

Supports: Claude Codex Code(CC)
🥉 74 Bronze
1

Download the skill ZIP

2

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

3

Toggle on and start using

Test it

Using "ppt-orchestra-skill". Plan a 5-slide product launch deck with a modern design theme.

Expected outcome:

Slide plan generated: Cover (full-bleed background, 44pt title), Table of Contents (3 sections with icon rows), Content - Features (two-column layout with data callouts), Content - Timeline (process flow with 4 steps), Closing (key takeaways and contact info). Typography: Georgia headers, Calibri body. Theme colors applied. Compile script structure provided.

Using "ppt-orchestra-skill". Run QA on my generated presentation to check for placeholder text and missing content.

Expected outcome:

QA report: 3 issues found. (1) Slide 4 contains 'lorem ipsum' placeholder text in body paragraph. (2) Slide 7 is missing the source citation for the chart data. (3) Slide 2 has center-aligned body text instead of left-aligned. Recommended fixes provided for each issue. Re-verification required after applying fixes.

Security Audit

Safe
v1 • 4/16/2026

All 31 static analysis findings were evaluated and determined to be false positives. The scanner incorrectly flagged hex color codes (e.g., '22223b', '4a4e69') as weak cryptographic algorithms, markdown code block delimiters as shell command execution, and layout documentation text as system reconnaissance. The skill is a legitimate PowerPoint planning and orchestration guide. Shell commands referenced (node compile.js, python -m markitdown, grep) are standard local development tools with no security risk. No prompt injection or malicious patterns were found.

1
Files scanned
156
Lines analyzed
0
findings
1
Total audits
No security issues found
Audited by: claude

Quality Score

38
Architecture
100
Maintainability
87
Content
50
Community
100
Security
91
Spec Compliance

What You Can Build

Marketing pitch deck planning

Plan a branded pitch deck with consistent slide types, typography rules, and visual variety before generating the final presentation.

Consulting presentation QA

Run quality assurance checks on generated client presentations to catch placeholder text, missing content, and formatting inconsistencies.

Educational lecture slides

Structure lecture presentations with clear section dividers, content pages with data visualization, and summary slides for key takeaways.

Try These Prompts

Plan a simple 5-slide deck
Plan a 5-slide presentation for a product launch. Classify each slide as one of the 5 page types and specify the layout, typography, and visual elements for each slide.
Plan a 10-slide sales deck
Plan a 10-slide sales presentation with these sections: Cover, Table of Contents, Problem, Solution, Features, Comparison, Data, Testimonials, Summary, and Contact. For each slide, specify the page type, layout option, font pairing, and color theme.
Plan a conference presentation with data slides
Plan a 15-slide conference presentation. Include Cover, Table of Contents, 3 Section Dividers, 8 Content pages (mix of data visualization, comparison, and timeline types), and a Closing page. Define a custom color theme, enforce typography rules, and specify QA checkpoints for each content slide.
Full orchestration with QA loop
Orchestrate a complete presentation workflow: classify all slides by type, generate individual slide modules, create the compile script, run the QA verification loop using markitdown text extraction, check for placeholder text with grep, fix identified issues, and re-verify affected slides. Report all issues found and fixes applied.

Best Practices

  • Classify every slide into one of the 5 page types before generating content to ensure consistent structure
  • Run the QA verification loop at least once with a fix-and-recheck cycle before declaring success
  • Commit fully to either a simple or complex layout style across the entire presentation - avoid mixing styles

Avoid

  • Centering body text instead of left-aligning paragraphs and lists
  • Repeating the same layout pattern across all slides without visual variety
  • Declaring the presentation complete without completing at least one fix-and-verify cycle

Frequently Asked Questions

What are the 5 slide page types this skill uses?
The 5 page types are: Cover Page (title and tone setting), Table of Contents (navigation), Section Divider (transitions between parts), Content Page (text, mixed media, data visualization, comparison, timeline, or image showcase), and Summary/Closing Page (wrap-up and action items).
Does this skill generate the actual PPTX file?
No. This skill provides planning and orchestration. It generates instructions, slide classifications, and a Node.js compile script that uses pptxgenjs to create the final PPTX file. You must install pptxgenjs separately.
What tools do I need installed to use this skill?
You need pptxgenjs for creating presentations (npm install -g pptxgenjs) and markitdown for text extraction QA (pip install markitdown[pptx]). Both are referenced in the skill instructions.
How does the QA process work?
After generating slides, extract text using markitdown, review for missing content and typos, check for leftover placeholder text using grep, list all issues found, fix them, and re-verify affected slides. Repeat until no new issues appear.
Can I customize the color theme and fonts?
Yes. The skill provides a default theme structure and font pairing table. You can define custom colors in the theme object and choose any font pairing from the provided table or use your own.
How many slides can this skill handle?
The compile script defaults to 12 slides but you can adjust the loop count. The skill works best for presentations with 5-20 slides. For larger decks, consider breaking them into sections with separate compilation.

Developer Details

Author

MiniMax-AI

License

Proprietary. LICENSE.txt has complete terms

Ref

main

File structure

📄 SKILL.md