sales-demos-talk-tracklisted

Scaffold a new use-case directory under the sales.demos-docs repo's docs/demos/ from _template/, or verify an existing one: check the five required files are present, discover renderable offline artifacts, run the renderer when applicable, visually inspect the output for broken images, and verify the 'Where the words come from' table has no empty rows and every source file exists. Laptop-only, no playbook. TRIGGER when: the user asks to create, scaffold, or start a new demo talk track or use case, verify or audit an existing talk track's structure or source table, re-render demo assets for the docs, check why a talk-track image looks wrong, or asks about the docs/demos/ conventions. Operates on a sibling checkout of ericcames/sales.demos-docs, not on this repo. SKIP: if the user is writing or editing the talk track prose itself — this skill checks structure and artifacts, not content — or if they only want to run render-demo-assets.py without the surrounding checks.
ericcames/sales.demos · ★ 1 · Data & Documents · score 67

Install: claude install-skill ericcames/sales.demos

# sales-demos-talk-track Scaffold or verify a use-case directory under `docs/demos/` **in the [sales.demos-docs](https://github.com/ericcames/sales.demos-docs) repo**, which has owned the talk tracks since #422. This repo has no `docs/` directory. The skill stays *here*, beside `render-demo-assets.py` and the `linux_configure` role whose templates it verifies against — and because `CLAUDE.md` says never to send someone to another repo's skill. It operates on a sibling checkout. Like `sales-demos-collections-sync`, this skill has **no playbook**, and that is deliberate. The "skill wraps a playbook" contract in `CLAUDE.md` exists so anything touching an environment is runnable from AAP too. This checks documentation on your laptop; it must never run from AAP, and there is nothing for a job template to call. ## Two modes The skill detects the mode from whether the directory exists: - **Scaffold** (`docs/demos/<use-case>/` does not exist in the docs repo) — copy `_template/`, replace placeholders, remind the user of run-sheet-first ordering, add a Draft row to the hub document. - **Verify** (`docs/demos/<use-case>/` exists) — check structure, discover renderable artifacts, run the renderer if applicable, visually inspect the output, and validate the "Where the words come from" table. **Do not verify immediately after scaffolding.** A freshly scaffolded directory is deliberately all placeholders. Verify is for a use case someone has been writing. ## Collect inputs