deck://skills

Teach your AI to make a deck that works

A skill pack for Claude Code and any MCP client. /deck runs the whole thing — it interviews you, fixes the story, settles what it looks like, and only then builds. Or point it at a deck you already have and it works out what's wrong before it touches anything.

Workshop slide reading "Use your AI to interview you." Your AI already has your context — your spreadsheets, your numbers, your logos.

Already connected the MCP? Just ask your agent to run install_deck_skills. Otherwise:

npx -y giget@latest gh:deckcp/deck-skills/skills .claude/skills --force

Writes into .claude/skills. Restart your client, then run /deck. Pack v0.9.0 · source on GitHub

How it goes

Five stages, and a gate at the end of each one — nothing advances until you say so. These are slides from the workshop deck we teach it from, which was itself made this way.

  1. Workshop slide: "Step 1 — the AI interview. Do it on your phone. Talk, don't type." Beside it, a phone dictating a long unbroken wall of text.

    1. Out loud, on your phone. Talking gets you what you'd never type.

  2. Workshop slide: "Step 2 — enrich your outline." A raw interview transcript on the left, an arrow, and a structured outline on the right.

    2. The transcript becomes an outline — this deck's own, in fact.

  3. Workshop slide: "Step 3 — critique and iterate. AI can add a lot of value, new ideas, and perspective. But it's often in a rush to build."

    3. Critique held as a mode: findings only, no edits, until you allow them.

  4. Workshop slide: "Step 4 — generate the deck. Hand it the outline. Let it run." A task list shows reading the outline, drafting copy and applying the brand kit.

    4. Only now does it build, on your brand rather than a template.

  5. Workshop slide: "Step 5 — edit it by hand to avoid slop. Editing AI writing by hand gives it a real human voice. Yours." Shown mid-edit in the DeckCP editor.

    5. The last pass is yours, by hand. That's the part it won't do for you.

What's in it

You don't need a DeckCP account to start — the interview and the outline are the part that decides whether a deck works, and they run with nothing connected. When you want it built, your agent makes the workspace itself and hands you a link to claim it.

Why we built it this way — the interview, the gates, and why you never see a layout archetype.