Agent skill · Documentation

deck-from-doc

Turn the user's REAL doc into a slide deck — open the source, structure the narrative, and build the actual .pptx — not slide-writing tips. Use when asked to make a deck from this doc, turn my brief into slides, build the presentation from my Drive doc, or deckify this in Cowork. Reads the document via the Google Drive/Docs connector, maps it to a one-idea-per-slide narrative, and produces a real presentation artifact (.pptx) with speaker notes plus a slide-by-slide outline.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill deck-from-doc --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/deck-from-doc/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Deck from Doc (Live) A good doc isn't a good deck — prose has to become one idea per slide with a spine an audience can follow. In Claude Cowork this skill reads the *real* document and builds an actual presentation file, so the user gets slides to refine, not advice on how to make them. ## What This Skill Produces - **The presentation artifact** — a real `.pptx` (or Slides), one idea per slide, with a clear narrative arc and speaker notes - **The slide-by-slide outline** — headline + the single point of each slide, for a fast review before the build - **The narrative spine** — the argument the deck makes, stated in one line ## Required Inputs Ask for these if not provided: - **The doc** — a Drive/Docs link or uploaded file - **Audience & purpose** — who's in the room and the decision/ask — the arc follows - **Length & template** — target slide count; a brand template/theme if one exists ## Framework: Doc → Deck 1. **Find the spine** — the one argument; every slide advances it or is cut. 2. **One idea per slide** — headline states the takeaway; the body supports it. 3. **Show, don't wall-of-text** — turn dense prose into a chart, a list, or a diagram cue. 4. **Arc** — situation →

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: Doc → Deck
  4. Execution (Cowork)
  5. Output Format
  6. Narrative spine
  7. Slide outline
  8. Output
  9. Quality Checks
  10. Anti-Patterns
  11. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the deck-from-doc skill do?

Turn the user's REAL doc into a slide deck — open the source, structure the narrative, and build the actual .pptx — not slide-writing tips. Use when asked to make a deck from this doc, turn my brief into slides, build the presentation from my Drive doc, or deckify this in Cowork. Reads the document via the Google Drive/Docs connector, maps it to a one-idea-per-slide narrative, and produces a real presentation artifact (.pptx) with speaker notes plus a slide-by-slide outline.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill deck-from-doc --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going