slides-builder

Single-skill end-to-end pipeline for the Google Slides backend. Read slide-plan.json v1.2, validate via pre-flight, then chain four bundled recipes (create-presentation → create-slides → insert-text → insert-image) and return the Drive URL. This skill does not make design decisions (go to slides-design), does not handle first-time setup (auth / gws install → gws-setup), and does not manage templates (removed in v0.3; see PRODUCT-SPEC §3.2 Non-Goals and §3.5 Phase 2+ triggers).

The 4 per-op recipes (formerly the separate google-slides-api skill, absorbed in v0.4 α-trim) now live under protocols/ of this skill. For raw API method discovery (resource × method tables, parameter shapes), use upstream gws-slides skill or run gws schema slides.<resource>.<method>.

This skill invokes the gws CLI through scripts/gws/gws-wrap.sh (under the plugin root); all shell-script contracts and exit-code mappings are defined in TECH-SPEC §4.2.

Composition pattern — threading the placeholder map

Recipes compose via a small data artifact called the placeholder map — a mapping from (slide_index, placeholder_role) to a Slides API objectId. It is produced by protocols/recipe-create-slides.md (from the createSlide reply plus a follow-up presentations.get) and consumed by recipe-insert-text.md and recipe-insert-image.md to target shapes directly, without relying on fragile {{TEXT_ANCHOR}} substitution.

Example shape: