← SupademoCONTENT HISTORY
WHAT CHANGED
Update to Supademo
Snapshot Oct 24, 2026 · 12:56 UTC · version 2.0.0
Collection source: downloaded plugin package.
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 JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Injects dynamic variables ({{name}}, {{company}}) into the right places in a Supademo demo — title, step copy, hotspots, chapters, CTAs — with graceful fallbacks, then wires per-prospect URLs. Use to turn one demo into a 1:1 asset for every account.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 217
}
],
"name": "demo-personalizer",
"skill_md_contents": "---\nname: demo-personalizer\ndescription: Injects dynamic variables ({{name}}, {{company}}) into the right places in a Supademo demo — title, step copy, hotspots, chapters, CTAs — with graceful fallbacks, then wires per-prospect URLs. Use to turn one demo into a 1:1 asset for every account.\n---\n\n# Demo Personalizer\n\n\"See how Acme cuts onboarding time in half\" converts better than \"See how our customers cut onboarding time in half.\" This skill finds the places where that's true — and only those.\n\n## Prerequisites\n\n- Supademo MCP connected\n- The demo to personalize, and which variables the team can actually supply (`name`, `company`, `role`, …) via URL params or lead-capture form fields\n\n## Workflow\n\n1. **Sweep the demo.** `get_demo` — collect the title, every step annotation, hotspot copy, chapter titles, and CTA labels.\n2. **Pick insertion points that earn it.** Personalization works at moments of attention, not everywhere:\n - **Demo title** — \"How {{company}} automates onboarding\" (via `update_demo_settings`)\n - **Step 1 hook** — the first line they read; naming them here sets the frame\n - **The CTA** — \"Start {{company}}'s free trial\" outperforms generic\n - **One mid-demo re-engagement** — a chapter title or annotation right where analytics show attention sagging\n Cap it at **3–5 insertions**. A demo that says the prospect's name on every screen reads as mail-merge, not attention.\n3. **Write fallbacks for every variable.** Organic and ungated viewers arrive with no values — \"How {{company|your team}} automates onboarding\" must render as \"How your team automates onboarding,\" never as raw `{{company}}`. No insertion ships without a fallback.\n4. **Prepare the plan** — Location | Current copy | Personalized copy | Fallback render. Return it for a planning request; carry out edits already authorized by the user without repeating approval.\n5. **Apply.** `update_steps` for annotations, `update_hotspots` for hotspot copy, `update_chapters` for chapter titles and chapter-button CTA labels, `update_demo_settings` for the title.\n6. **Wire the data source.**\n - **Outbound / 1:1** — query params on per-prospect links from `trackable-link-generator` (`?v_company=Acme`); at scale, the email tool's merge fields fill the URL (`?v_company={{account.name}}`; URL-encode rendered values)\n - **Inbound / gated** — map lead-capture form fields to the same variables\n7. **Test both states.** Use the returned canonical or trackable URL. Created link variables use unprefixed keys such as `company`; URL overrides use the `v_` prefix. View once with values populated and once bare, confirming the personalized and fallback renders both read cleanly.\n\n## Guardrails\n\n- Personalize framing, never facts — \"{{company}}'s dashboard\" is a lie if the screens show your own sample data. Frame around the viewer; don't fake their environment.\n- First name and company only in URL params; anything more personal goes through the lead form.\n- If the demo has translations, personalization spans need the same treatment per language (`set_demo_translation_text`) or locked-out variables will leak English into localized demos.\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: 10f0d80c112a7e4333dd4c499fbb7ad8af2c86b9e5edb34ac203afa568179f49