pptx-export SKILL.md skillA
pptx-export from wfukatsu/slide-forge is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wfukatsu/slide-forge/pptx-export@git:20260916.2f4b343Pins git:20260916.2f4b343 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wfukatsu/slide-forge
- Path
skills/pptx-export/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260916.2f4b343, committed Sep 16, 2026
- First version recorded
- Aug 10, 2026
- Size
- 4,172 bytes
- Repository stars
- 5
- License
- MIT
Export a generated Google Slides deck to PowerPoint (.pptx) via the Drive API, preserving it exactly as generated. Invoked by the generation skills when the user chooses PPTX at intake, and runs standalone on any accessible deck URL. Use for: PPTX でも出力して, PowerPoint 形式でほしい, パワポで納品, export to PowerPoint. Not: authoring or editing PPTX files directly (document-skills:pptx); QA, which runs on the Slides deck via slide-qa before export.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
*[日本語](SKILL.ja.md)*
# PPTX Export for Generated Decks
## Important
- **The export is a snapshot, not a linked copy.** It captures the deck as it
is at export time. Always export **after** visual QA and any fix loop are
finished — and re-export whenever the deck is regenerated, deleting the
stale `.pptx` from the Drive folder first (same rule as superseded decks).
- **Fixes happen in the spec, never in the .pptx.** On any defect, return to
the originating generation skill, fix the spec, regenerate, re-run QA if it
was chosen, then export again. Editing the exported file forks it from the
source of truth.
- **Run every command from the slide-forge root as cwd** — `${CLAUDE_PLUGIN_ROOT}`
when running from an installed plugin, `/path/to/slide-forge` on a
local clone. Auth and the venv are shared at the repo root (`config/`, `.venv`).
- **Whether to export PPTX is settled at generation time** via the output
format question in intake (`references/interactive-intake.md` §2); the
default is Google Slides only. Standalone runs on an existing deck URL need
no intake.
- **`output: local` in `config/settings.json` makes the export automatic.**
…Read the whole file at its exact version.
How to install
mdr add wfukatsu/slide-forge/pptx-export@sha256:3f87d6ed43609e04The line at the top of this page pins the label git:20260916.2f4b343, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_nkseifvcuwqjpd5i)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 10, 2026 and Sep 16, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.2f4b343 latest | 2026-09-16 | 2f4b343 | 4,172 B | A | view · diff |
| git:20260822.3775b27 | 2026-08-22 | 3775b27 | 4,238 B | A | view · diff |
| git:20260820.89a0da2 | 2026-08-20 | 89a0da2 | 4,464 B | A | view · diff |
| git:20260812.92c38df | 2026-08-12 | 92c38df | 4,063 B | A | view · diff |
| git:20260810.5a10934 | 2026-08-10 | 5a10934 | 4,042 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4172 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wfukatsu/slide-forge · 5 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nkseifvcuwqjpd5i GET https://markdownregistry.com/api/v1/resolve?ref=wfukatsu/slide-forge/pptx-export GET https://markdownregistry.com/api/v1/blob/3f87d6ed43609e0469e513d8694a379e5b877b996300d84f6bc4bb45af067dcc
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.