← SupademoCONTENT HISTORY

Update to Supademo

Snapshot Oct 24, 2026 · 12:56 UTC · version 2.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Supademo and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Restructures long Supademo demos with chapters and tighter pacing so viewers can jump to what they care about. Use when a demo has grown past ~15 steps, has no chapters, or analytics show mid-demo drop-off.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 217
    }
  ],
  "name": "chapter-pacing-organizer",
  "skill_md_contents": "---\nname: chapter-pacing-organizer\ndescription: Restructures long Supademo demos with chapters and tighter pacing so viewers can jump to what they care about. Use when a demo has grown past ~15 steps, has no chapters, or analytics show mid-demo drop-off.\n---\n\n# Chapter & Pacing Organizer\n\nLong demos lose viewers. This skill breaks a demo into skimmable chapters and trims the fat.\n\n## Prerequisites\n\n- Supademo MCP connected\n- The demo to restructure\n\n## Workflow\n\n1. **Read the demo end-to-end.** `get_demo` — map each step to the task it belongs to (e.g., steps 1–4 = \"Connect your account\", 5–9 = \"Build your first report\").\n2. **Propose chapter breaks.** Chapters should follow task boundaries, not arbitrary step counts. 3–6 chapters is the sweet spot. Present:\n   | Chapter | Steps | Title |\n3. **Spot pacing problems.**\n   - Consecutive steps showing near-identical screens → candidates to cut or consolidate through an explicitly planned edit; no generic step-merge tool is available\n   - Setup steps a buyer doesn't care about → cut or collapse into one annotated step\n   - The \"aha\" moment buried past step 10 → suggest moving it earlier with `reorder_steps` if the flow allows\n4. **Apply the authorized plan.** Create missing chapter steps with `create_steps`: use `type: \"chapter\"`, `chapterType: \"Link\"`, the title in `chapter.heading`, and `position` for the intended 1-based insertion point. Edit existing chapters with `update_chapters` using their chapter step IDs. Use `reorder_steps` for sequence changes and `delete_steps` for the exact deletions the user has authorized. Existing authorization counts; ask only when the targets or scope remain unclear.\n5. **Verify.** Re-pull `get_demo` and confirm the chapter list and step order match the approved plan.\n\n## Guardrails\n\n- Identify exact step IDs before deletion and keep the change within the requested scope.\n- If the demo has voiceovers, warn that reordering may break narrative continuity — voiceover scripts may need regeneration (`generate_voiceovers`).\n- Check `get_demo_hotspot_performance` first if available: don't cut steps that are actually engaging viewers.\n\n## Supademo tool conventions\n\nRead [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.\n"
}

SHA-256 of public snapshot: 494983b990e8f24404b726b07bfc0b4381ffd8dec837f9fb3c3d0df89bb76b5f