many-ppt-skills

---
name: many-ppt-skills
description: Pick an AI slide-deck skill and a concrete visual style from a curated registry, filtering on the requirements that decide it — editable in PowerPoint, speaker notes, a mandated corporate template, offline, PDF — with sample imagery and the style ids each project actually uses. Use when the user wants to make a presentation, deck or slides and has not already chosen a tool; asks which slide skill to use or what the difference between them is; wants to know what a style looks like before committing; or names a style id such as soft-editorial or swiss-grid. This skill routes to the skill that makes the deck — it does not make decks itself.
---

# many-ppt-skills

A registry of AI slide-deck skills, the imagery they publish, the style ids they
name that imagery with, and what their own documentation claims they can do.
Your job with it is to get someone from "I need a deck" to an installed skill and
a style id, quickly, without guessing.

Counts are not written down here — `pick.py` prints them live, and a number
copied into prose is a number that goes stale.

**This skill does not generate decks.** It chooses which one will, and hands
over.

## Query the registry — do not read the JSON

The data files total roughly 200KB. Reading them into context to answer one
question is the mistake this repository has a whole principle about
(`principles/05-progressive-disclosure.md`). Use the CLI.

**Run it by absolute path.** Your working directory is the user's project, not
this skill — a bare `scripts/pick.py` resolves against their repo and fails with
"can't open file". Build the path from this skill's own directory, which the
loader gives you when this file opens (Claude Code prints it as *Base directory
for this skill*; a plugin install exposes it as `${CLAUDE_PLUGIN_ROOT}`). Set it
once, and never `cd` into the skill directory — that would move the user's shell
out of their project. The script finds its own data files relative to itself, so
only the path to the script matters.

```bash
SKILL_DIR=~/.claude/skills/many-ppt-skills   # or ${CLAUDE_PLUGIN_ROOT}, or the base directory printed above
python "$SKILL_DIR/scripts/pick.py" route
```

A separate shell call does not remember `SKILL_DIR`, so keep the assignment and
the query in one command, or substitute the literal path.

The five steps are the whole method. Steps 0 and 1 are cheap and decide
everything after them, so do not skip ahead to `list`.

## Step 0 — check what the user already has