SkillAgentSearch skills...

ppt-orchestra-skill

Plan and orchestrate multi-slide PowerPoint creation from scratch. Use before generating a full deck with subagents: classify each slide type, enforce visual variety, set typography/spacing rules, and run text-based QA to catch content issues.

Install / Use

npx skills add MiniMax-AI/skills --skill ppt-orchestra-skill

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Tags

Our assessment of ppt-orchestra-skill

ppt-orchestra-skill scores 87/100 on our quality scale, 2093rd of 4,700 Development & Engineering skills we index (top 45%).

Its SKILL.md is 5.8 KB long, well organised into 9 sections with 3 code examples: a solid amount of guidance for an agent.

With 13,641 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
18/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 7 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-11-02 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 94/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

ppt-orchestra-skill compared with similar skills

All 4 of these similar skills score higher than ppt-orchestra-skill; compare them before choosing.

SkillScoreStarsUpdatedFormat
ppt-orchestra-skill (this skill)by MiniMax-AI8713.6k7mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install ppt-orchestra-skill?
Run npx skills add MiniMax-AI/skills --skill ppt-orchestra-skill. The install tabs above show the steps for each supported agent.
Which AI agents does ppt-orchestra-skill work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is ppt-orchestra-skill safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 94/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is ppt-orchestra-skill still maintained?
The repository was last updated about 7 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: ppt-orchestra-skill description: "Plan and orchestrate multi-slide PowerPoint creation from scratch. Use before generating a full deck with subagents: classify each slide type, enforce visual variety, set typography/spacing rules, and run text-based QA to catch content issues." license: Proprietary. LICENSE.txt has complete terms

Slide Page Types (Standard)

For slide-by-slide generation (one JS file per slide), classify every slide as exactly one of these 5 page types. This keeps structure consistent and prevents "random layout drift".

  1. Cover Page
    • Use for: opening + tone setting
    • Content: big title, subtitle/presenter, date/occasion, strong background/motif
  2. Table of Contents
    • Use for: navigation + expectation setting (3–5 sections)
    • Content: section list (optional icons / page numbers)
  3. Section Divider
    • Use for: clear transitions between major parts
    • Content: section number + title (+ optional 1–2 line intro)
  4. Content Page (pick a subtype)
    • Text: bullets/quotes/short paragraphs (still add icons/shapes)
    • Mixed media: two-column / half-bleed image + text overlay
    • Data visualization: chart + 1–3 key takeaways + source
    • Comparison: side-by-side columns/cards (A vs B, pros/cons)
    • Timeline / process: steps with arrows, journey, phases
    • Image showcase: hero image, gallery, or visual-first layout
  5. Summary / Closing Page
    • Use for: wrap-up + action
    • Content: key takeaways, CTA/next steps, contact/QR, thank-you

Layout options:

  • Two-column (text left, illustration on right)
  • Icon + text rows (icon in colored circle, bold header, description below)
  • 2x2 or 2x3 grid (image on one side, grid of content blocks on other)
  • Half-bleed image (full left or right side) with content overlay

Data display:

  • Large stat callouts (big numbers 60-72pt with small labels below)
  • Comparison columns (before/after, pros/cons, side-by-side options)
  • Timeline or process flow (numbered steps, arrows)

Visual polish:

  • Icons in small colored circles next to section headers
  • Italic accent text for key stats or taglines

Typography

Choose an interesting font pairing — don't default to Arial. Pick a header font with personality and pair it with a clean body font.

| Header Font | Body Font | |-------------|-----------| | Georgia | Calibri | | Arial Black | Arial | | Calibri | Calibri Light | | Cambria | Calibri | | Trebuchet MS | Calibri | | Impact | Arial | | Palatino | Garamond | | Consolas | Calibri |

| Element | Size | |---------|------| | Slide title | 36-44pt bold | | Section header | 20-24pt bold | | Body text | 14-16pt | | Captions | 10-12pt muted |

Spacing

  • 0.5" minimum margins
  • 0.3-0.5" between content blocks
  • Leave breathing room—don't fill every inch

Avoid (Common Mistakes)

  • Don't repeat the same layout — vary columns, cards, and callouts across slides
  • Don't center body text — left-align paragraphs and lists; center only titles
  • Don't skimp on size contrast — titles need 36pt+ to stand out from 14-16pt body
  • Don't default to blue — pick colors that reflect the specific topic
  • Don't mix spacing randomly — choose 0.3" or 0.5" gaps and use consistently
  • Don't style one slide and leave the rest plain — commit fully or keep it simple throughout
  • Don't create text-only slides — add images, icons, charts, or visual elements; avoid plain title + bullets
  • Don't forget text box padding — when aligning lines or shapes with text edges, set margin: 0 on the text box or offset the shape to account for padding
  • Don't use low-contrast elements — icons AND text need strong contrast against the background; avoid light text on light backgrounds or dark text on dark backgrounds
  • NEVER use accent lines under titles — these are a hallmark of AI-generated slides; use whitespace or background color instead

Compiling Slides

After all slide JS files are generated in slides/, create slides/compile.js to compile them into a single PPTX:

// slides/compile.js
const pptxgen = require('pptxgenjs');
const pres = new pptxgen();
pres.layout = 'LAYOUT_16x9';

const theme = {
  primary: "22223b",    // dark color for backgrounds/text
  secondary: "4a4e69",  // secondary accent
  accent: "9a8c98",     // highlight color
  light: "c9ada7",      // light accent
  bg: "f2e9e4"          // background color
};

for (let i = 1; i <= 12; i++) {  // adjust count as needed
  const num = String(i).padStart(2, '0');
  const slideModule = require(`./slide-${num}.js`);
  slideModule.createSlide(pres, theme);
}

pres.writeFile({ fileName: './output/presentation.pptx' });

Run with: cd slides && node compile.js


QA (Required)

Assume there are problems. Your job is to find them.

Your first render is almost never correct. Approach QA as a bug hunt, not a confirmation step. If you found zero issues on first inspection, you weren't looking hard enough.

Content QA

python -m markitdown output.pptx

Check for missing content, typos, wrong order.

When using templates, check for leftover placeholder text:

python -m markitdown output.pptx | grep -iE "xxxx|lorem|ipsum|this.*(page|slide).*layout"

If grep returns results, fix them before declaring success.

Verification Loop

  1. Generate slides → Extract text with python -m markitdown output.pptx → Review content
  2. List issues found (if none found, look again more critically)
  3. Fix issues
  4. Re-verify affected slides — one fix often creates another problem
  5. Repeat until a full pass reveals no new issues

Do not declare success until you've completed at least one fix-and-verify cycle.


Dependencies

  • pip install "markitdown[pptx]" - text extraction
  • npm install -g pptxgenjs - creating from scratch

Related Skills

View on GitHub
GitHub Stars13.6k
CategoryDevelopment
Updated7mo ago
Forks1.2k

Languages

C#

Trust signals

94/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low