Use md-to-pptx

Turn an existing Markdown document (a status report, runbook, review or notes) into a PowerPoint deck (.pptx) that opens without a repair prompt, with nothing to install

Turn an existing Markdown document (a status report, runbook, review or notes) into a PowerPoint deck (.pptx) that opens without a repair prompt, with nothing to install. Each heading becomes a slide, lists keep their nesting, tables become real PowerPoint tables, images are embedded, and comments become speaker notes. A section too long for one slide is split onto "continued" slides instead of shrinking the text, and the reply names every split, everything dropped, and any speaker note that would go out with the file.

Reach for it when the user says "turn this markdown into slides", "make this report a PowerPoint", "convert the .md to pptx", "I need this as a deck for Thursday", or "export these notes to PowerPoint".

Install it

npx skilldrop-cli install md-to-pptx                 # Claude Code, your user folder
npx skilldrop-cli install md-to-pptx --project       # Claude Code, this repo
npx skilldrop-cli install md-to-pptx --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the Converters pack: --pack converters installs it with its neighbours.

It ships scripts, so it needs Python 3 (standard library only, nothing to install). What they may touch is declared in its manifest.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "turn this markdown status report into slides for Thursday"
• "Convert runbook.md to a pptx"
• "Can you make my meeting notes in notes.md into a PowerPoint? Keep the tables as tables"
• "Export docs/q3-review.md as a PowerPoint deck with our brand.json fonts and colours"
• "I need this README as slides, nothing fancy, one slide per section"

Requests like these belong to a different skill, so it shouldn't answer them:

• "Build an investor pitch deck from these bullet points, with charts and our corporate template"
• "Outline the slides for my architecture review next week: what should each slide say?"
• "Convert this markdown report to a Word document legal can track changes in"

If another skill answers instead, ask for this one by name: "use md-to-pptx".

Check what you get

A good result:

• The slides follow the headings. The printed outline matches the document's ## headings one for one, plus "(continued)" slides.
• No text below its set size. Overflow is split onto continued slides, and every split is named in the reply.
• Tables are tables. A pipe table becomes a PowerPoint table the user can edit, not a picture or tab-separated text, and a split table repeats its header row.
• Nothing is lost silently. Every WARN is fixed and gone on rerun, or reported in plain words.
• Notes were read. Any note that would embarrass the sender if forwarded is named by slide, and taken out when the deck is going outside the team. Its contents are never repeated in the reply.
• Every image arrived. Each image the document names is on a slide at a readable size, or the reply names it as missing or a placeholder.
• Splits fall between items. A list item and its sub-bullets stay on one slide, and continued slides are evenly filled.
• Facts are untouched. No number, name, date or list order changed, and no slide added that the document lacks.
• Mismatches are named, not fixed. A count or total the document contradicts is quoted back with both figures.
• The file checks out. The checked: line is in the run, and no check is claimed that wasn't run.

See a worked example

• support weekly input
• support weekly

Use something else when

• Planning what each slide should say before any document exists; use slide-outliner
• A Word document to edit and track changes in; use md-to-docx
• A .pptx back to Markdown; use file-to-markdown

Next

• SKILL.md, the instructions the agent reads
• Its page on the site
• Related: brand-kit, file-to-markdown, md-to-docx, slide-outliner

Edit this page on GitHub · View source