← 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": "Maps a product change or feature launch to the Supademo demos and steps it affects, then drafts the copy updates and flags steps that need recapture. Use when a release ships and demos show the old UI or outdated language.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 217
    }
  ],
  "name": "feature-launch-demo-updater",
  "skill_md_contents": "---\nname: feature-launch-demo-updater\ndescription: Maps a product change or feature launch to the Supademo demos and steps it affects, then drafts the copy updates and flags steps that need recapture. Use when a release ships and demos show the old UI or outdated language.\n---\n\n# Feature Launch Demo Updater\n\nShip a feature without shipping stale demos. This skill finds every demo step a product change touches and drafts the fix.\n\n## Prerequisites\n\n- Supademo MCP connected\n- A description of the change: release notes, a changelog entry, a PRD, or \"we renamed X to Y and moved it to the settings page\"\n\n## Workflow\n\n1. **Parse the change.** Extract what's user-visible: renamed features, moved navigation, new/removed buttons, redesigned screens, changed defaults.\n2. **Find candidate demos.** Use `list_demos` (filter by relevant tags or folder via `list_folders` / `list_tags`) to shortlist demos likely to show the affected surface.\n3. **Inspect each candidate.** Pull `get_demo` and scan step annotations, hotspot copy, and chapter titles for mentions of the old name, flow, or screen.\n4. **Produce an impact report.**\n   | Demo | Step(s) | What's stale | Fix type |\n   Fix types: `copy-only` (text fix), `recapture` (screenshot shows old UI), `remove` (feature no longer exists).\n5. **Apply authorized copy fixes** with `update_steps` and `update_hotspots`.\n6. **Handle recaptures.** For steps flagged `recapture`, tell the user which screens to re-record. Once new media is uploaded (`create_upload_job` or via the media library with `list_media_library_items`), swap it in with `replace_step_media`.\n7. **Tag for tracking.** Resolve or create the `needs-recapture` tag ID using `list_tags`/`create_tags`, then use `add_demo_tags` so unfinished work stays visible.\n\n## Guardrails\n\n- Keep edits and deletions within the user’s requested or approved scope; use exact step IDs.\n- If a demo has translations (`list_demo_translations`), flag that they'll need regeneration after the source changes.\n- Verify the updated content, then use `publish_demo` when the user has authorized publication; otherwise return the draft changes.\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: 438c53ea2ecd29731be33dcecbccf4d79e1611f327f4e5df99540e6bf4a96f91