← ClaudeAtlas

google-slides-templatelisted

Generate or update Google Slides from a registered master/template with interactive intake, strict offline validation, Drive source collection, and optional visual QA. Use when a template URL or registered template exists.
wfukatsu/slide-forge · ★ 2 · Data & Documents · score 66
Install: claude install-skill wfukatsu/slide-forge
*[日本語](SKILL.ja.md)* # Google Slides from a template Claude Code is the primary host for this shared skill. Codex and Antigravity run the same procedure through their host adapters. Work from the slide-forge repository root with `.venv/bin/python`. Read this file completely. Then follow `references/workflow-contract.md`. Load detailed references only when activated by the routing table below. ## Scope Use this skill to: - generate a new deck from a registered template; - inspect and register a supplied, unregistered master before generation; - update selected pages of a slide-forge-managed deck from its complete source spec, or rebuild all pages when full replacement is explicitly approved. Use `google-slides` for a deck without a corporate master, `template-forge` to create a new master design, and `image-slots` when the only task is filling empty image frames in an existing deck. ## Non-negotiable rules - Before editing a user-owned deck in place, run `.venv/bin/python scripts/snapshot_version.py <URL>` and report the revision. - For a local fix, use `--into <deck> --update-slides <pages>` after snapshot; it preserves every unselected page. Bare `--into` replaces every page and requires target/master verification plus explicit full-replacement approval. - Ask only for missing branch decisions; never ask again for supplied or delegated (`your call`) decisions. - Get explicit approval for page count, layout, and every action title before authoring, unless