· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Supademo v2.0.0
Create and manage demos
From the developer
Connect existing Supademo accounts and use their available features. The plugin does not initiate subscription, upgrade, or credit purchases.
Not specified in the available declarations: capabilities.
Find my latest product onboarding demo and summarize its steps.
Developer declarations; not independently tested. Listing last checked Nov 16, 2026. Package observed Nov 15, 2026.
From the marketplace listing
Use Supademo to find, create, edit, organize, share, and analyze interactive product demos and showcases from your connected account. Workflow skills help with demo copy, QA, localization, voiceovers, sales personalization, analytics, and library maintenance. Where enabled, build Demo Agents with accessible knowledge and readiness checks. Workspace roles, plan entitlements, and feature availability apply. Media creation uses uploaded workspace handles; a video becomes one video step rather than an automatic screenshot sequence. Analytics reports describe available measurements and their limits.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 3 observations
Is template instance added: “false”. App-6a53f7d79b5c81919a02e9814eb9f070 updated; open the comparison for details. Supademo updated; open the comparison for details. Full description changed from “Supademo helps teams find, create, edit, organize, publish, and analyze interactive product demos and showcases from...
View comparison →Is template instance added: “false”. App-6a53f7d79b5c81919a02e9814eb9f070 updated; open the comparison for details. Supademo updated; open the comparison for details. Full description changed from “Supademo helps teams find, create, edit, organize, publish, and analyze interactive product demos and showcases from...
View comparison →Package or technical metadata updated
View technical comparison →Find competitors to follow as you develop your plugin.
Turn products, references and scripts into images, videos and audio with Zim Studio. Plan campaigns, write copy and UGC scripts, create s...
Shared terms: copy, creation, feature, knowledge
Generate and edit media with Runway, including planned Ad Director workflows in chat.
Shared terms: feature, media, voiceover, video
AI social media management, on-brand content creation, scheduling, analytics, and marketing workflows with Simplified.
Shared terms: analytics, creation, media, step
Create polished, on-brand product videos directly from ChatGPT with Arcade. Turn a prompt, product brief, screenshots, or meeting notes i...
Shared terms: demo, feature, screenshot, sale
Kolbo.AI helps users create and edit images, video, music, speech, sound, and 3D assets, then organize the results in projects, documents...
Shared terms: library, media, organize, video
--- name: brand-voice-editor description: Edits Supademo demo copy — step annotations, hotspot text, and CTAs — so it matches your brand voice and terminology. Use when demo copy sounds off-brand, inconsistent, or was written by different authors. --- # Brand Voice Editor Rewrite the copy inside a Supademo demo so every step, hotspot, and CTA sounds like it came from one writer — yours. ## Prerequisites - Supademo MCP connected - A brand voice reference: style guide, a doc of approved terminology, or 2–3 examples of on-brand copy the user pastes in ## Workflow 1. **Collect the voice reference.** Ask the user for their style guide or example copy if none was provided. Extract concrete rules: tone (e.g., "confident, not hypey"), banned words, product terminology (e.g., "Showcase" not "playlist"), sentence length, capitalization conventions. 2. **Load the demo.** Use `list_demos` to find the target demo, then `get_demo` to pull every step's annotation text, hotspot copy, and button/CTA labels. 3. **Audit before editing.** Produce a before/after table for every proposed change: | Step | Current copy | Proposed copy | Rule applied | Never rewrite copy that already complies — flag it as "on-brand, no change." 4. **Apply authorized edits.** Approval already given in the conversation counts. For a review-only request, return the proposal; when editing is requested, apply edits with `update_steps` (annotations) and `update_hotspots` (hotspot text, buttons). Batch changes per demo. 5. **Report.** Summarize: steps changed, rules most frequently violated, and any copy you left alone because changing it would alter meaning (e.g., UI labels that must match the product). ## Guardrails - Never change text that mirrors actual product UI — the demo must match what users see in the app. - Publish with `publish_demo` only when publication is included in the user’s authorized task. - Keep character counts close to the original; hotspot tooltips truncate long copy. ## Supademo tool conventions Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
--- name: chapter-pacing-organizer 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. --- # Chapter & Pacing Organizer Long demos lose viewers. This skill breaks a demo into skimmable chapters and trims the fat. ## Prerequisites - Supademo MCP connected - The demo to restructure ## Workflow 1. **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"). 2. **Propose chapter breaks.** Chapters should follow task boundaries, not arbitrary step counts. 3–6 chapters is the sweet spot. Present: | Chapter | Steps | Title | 3. **Spot pacing problems.** - Consecutive steps showing near-identical screens → candidates to cut or consolidate through an explicitly planned edit; no generic step-merge tool is available - Setup steps a buyer doesn't care about → cut or collapse into one annotated step - The "aha" moment buried past step 10 → suggest moving it earlier with `reorder_steps` if the flow allows 4. **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. 5. **Verify.** Re-pull `get_demo` and confirm the chapter list and step order match the approved plan. ## Guardrails - Identify exact step IDs before deletion and keep the change within the requested scope. - If the demo has voiceovers, warn that reordering may break narrative continuity — voiceover scripts may need regeneration (`generate_voiceovers`). - Check `get_demo_hotspot_performance` first if available: don't cut steps that are actually engaging viewers. ## Supademo tool conventions Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
---
name: deal-stage-demo-matcher
description: Recommends the right Supademo demo or showcase for a prospect based on deal stage, persona, and use case — with share links and send copy. Use when a rep asks "what should I send this account?"
---
# Deal Stage Demo Matcher
Stop sending the all-purpose overview demo to everyone. Match the asset to the moment.
## Prerequisites
- Supademo MCP connected
- Deal context: stage, persona, use case, and any objection on the table
## Workflow
1. **Intake.** Stage (first touch / evaluating / security review / negotiation), who's watching (champion, end users, exec sponsor, IT), and what they care about.
2. **Inventory the library.** `list_demos` and `list_showcases`, using `list_tags` to filter by use case. Note which assets exist per funnel stage.
3. **Match by stage logic:**
- **First touch** → short outcome-led overview (≤10 steps); never the deep-dive
- **Active evaluation** → feature deep-dives matched to their stated use case
- **Multi-stakeholder** → a showcase bundling one asset per stakeholder, not five separate links
- **Security/IT review** → admin, permissions, SSO demos
- **Late stage / stalled** → the specific demo answering the open objection
4. **Return ranked picks.** Top 1–2 with a one-line "why this one," plus an existing verified share link. If personalized link creation is part of the request, use `create_demo_links` for demos or `create_showcase_links` for showcases. `get_showcase_share_info` supplies canonical showcase sharing information. A recommendation-only request does not require creating new links.
5. **Draft the send.** 2–3 sentence email/Slack copy referencing their context, with the link. Return the draft; sending requires a separate explicit request and an available authorized messaging tool.
6. **Flag gaps.** If no asset fits ("we have nothing for the CFO persona"), say so — that's roadmap input for the demo team.
## Guardrails
- Recommend from what exists; don't describe demos you haven't verified via `list_demos`.
- Prefer trackable links so `share-link-follow-up` can pick up the thread later.
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
--- name: demo-agent-builder description: Builds or updates a Supademo Demo Agent using accessible knowledge, draft settings, indexing status, and readiness checks. Use for an agent setup or refresh; public publication and automation deliveries need to be included in the requested scope. --- # Demo Agent Builder Read [the tool conventions](../supademo-onboarding/references/tool-use.md). 1. **Resolve the agent.** Use `list_agents` and `get_agent` for an existing agent, or `create_agent` for an authorized new one. Establish its workspace, purpose, audience, and the knowledge the user wants it to use. If Agent tools are absent, explain the feature/review limitation. 2. **Configure the draft.** Use `update_agent` and `update_agent_intro` for requested identity, instructions, and introduction. Use `create_agent_quick_links` for new labels, `update_agent_quick_links` for existing labels, and `remove_agent_quick_links` for removals; read `get_agent` first and match labels case-insensitively. Use `list_agent_voices` if voice selection is needed. Read the schemas instead of copying demo voice/settings fields into Agent tools. 3. **Select knowledge.** Resolve source IDs with `search_agent_knowledge` or asset lists. Use `attach_agent_knowledge` for existing reusable sources, or the corresponding `add_agent_demo_knowledge`, `add_agent_video_knowledge`, `add_agent_document_knowledge`, and `add_agent_text_knowledge` tools for supported content. Uploaded document URLs must come from trusted workspace storage. Use `discover_agent_website_pages` and `add_agent_website_knowledge` only for the website/pages the user requested. 4. **Protect shared source metadata.** Providing demo/video `contentHints` can replace shared workspace hints used by other agents. A video source title only fills a source that has none. Omit these fields when only attachment is intended. Use `get_agent_knowledge_source` to review indexing state and attached content; read raw text only when necessary. `reindex_agent_knowledge` queues work and can re-crawl external websites. 5. **Check readiness.** Re-read `get_agent` and source status, use `evaluate_agent_checklist` when requested or appropriate for release readiness, and retrieve `get_agent_checklist`. Keep queued indexing/evaluation distinct from successful completion. Resolve failed/pending sources or report their status before claiming the agent is ready. 6. **Publish within scope.** `publish_agent` replaces the current live version; `unpublish_agent` removes live availability. Publish after the requested checks when publication is authorized, otherwise leave the draft and report what remains. Verify returned/live version state and, when possible, test the public agent with a relevant question. 7. **Configure automations separately when requested.** Inspect `list_agent_triggers` and connected integrations before using trigger tools. Enabled triggers can deliver conversation data by email or to external CRM/Slack/webhook integrations. Match recipients, actions, enabled state, and conditions to the user's request. Do not add or enable delivery as an incidental part of basic agent setup. Use Monitor insight/session tools only for a requested investigation. Full transcripts and public session sharing are separate from aggregate agent readiness and can expose visitor information.
Referenced files: 1 — file references are metadata, not package contents.
--- name: demo-localizer description: Translates a Supademo demo into target languages, manages the translation lifecycle, and keeps a do-not-translate glossary. Use when expanding a demo library to new markets or when sales needs a localized version for a regional deal. --- # Demo Localizer One demo, every market. Generates and maintains translations without letting them drift out of sync with the source. ## Prerequisites - Supademo MCP connected - Target language(s) and, ideally, a glossary of terms that must not be translated (product names, feature names, trademarks) ## Workflow 1. **Check what exists.** `list_demo_translations` — regenerating an existing language overwrites manual fixes. Identify existing translations and regenerate only when that overwrite is part of the user’s authorized request. 2. **Build the glossary.** Ask for do-not-translate terms if none were given. Default protections: the product name, feature names that are UI labels, customer names in testimonials. 3. **Generate.** `generate_demo_translation` per target language. 4. **Spot-check the output.** Call `list_demo_translations` with `targetLanguage` for full translated entity text and media, then review the highest-stakes copy: step 1, all CTAs, and any step with numbers or claims. Verify: - Glossary terms survived untranslated - CTA labels stayed short enough for buttons - Formal/informal register matches the market (e.g., Sie vs du for German B2B) 5. **Fix in place.** Correct individual strings with `set_demo_translation_text` — don't regenerate the whole language for one bad line. 6. **Report.** Language, steps translated, fixes applied, and anything needing a native-speaker review. ## Lifecycle rules - When source text changes, compare the corresponding translated entities against it. Flag affected strings for review; do not invent translation freshness timestamps. Regeneration overwrites manual fixes, so prefer targeted updates when appropriate. - Remove abandoned languages with `delete_demo_translation` only on explicit request. - Localized voiceovers are a separate pass — see the `voiceover-producer` skill with `list_voices` filtered to the target language. ## Supademo tool conventions Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
---
name: demo-personalizer
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.
---
# Demo Personalizer
"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.
## Prerequisites
- Supademo MCP connected
- The demo to personalize, and which variables the team can actually supply (`name`, `company`, `role`, …) via URL params or lead-capture form fields
## Workflow
1. **Sweep the demo.** `get_demo` — collect the title, every step annotation, hotspot copy, chapter titles, and CTA labels.
2. **Pick insertion points that earn it.** Personalization works at moments of attention, not everywhere:
- **Demo title** — "How {{company}} automates onboarding" (via `update_demo_settings`)
- **Step 1 hook** — the first line they read; naming them here sets the frame
- **The CTA** — "Start {{company}}'s free trial" outperforms generic
- **One mid-demo re-engagement** — a chapter title or annotation right where analytics show attention sagging
Cap it at **3–5 insertions**. A demo that says the prospect's name on every screen reads as mail-merge, not attention.
3. **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.
4. **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.
5. **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.
6. **Wire the data source.**
- **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)
- **Inbound / gated** — map lead-capture form fields to the same variables
7. **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.
## Guardrails
- 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.
- First name and company only in URL params; anything more personal goes through the lead form.
- 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.
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
---
name: demo-qa-checklist
description: Runs a structured pre-publish QA pass on a Supademo demo — typos, flow order, hotspot placement, dead links, chapters, voiceover and translation consistency. Use after editing a demo and before it goes live.
---
# Demo QA Checklist
Catch the embarrassing stuff before a prospect does. Runs a repeatable QA pass and returns a pass/fail checklist per demo.
## Prerequisites
- Supademo MCP connected
- The demo to check (name or ID; find it with `list_demos`)
## Workflow
Pull the full demo with `get_demo`, then walk every step in order and check:
1. **Copy quality** — typos, grammar, double spaces, inconsistent capitalization across steps, placeholder text ("Lorem", "TODO", "test").
2. **Flow coherence** — steps tell one continuous story; no orphan steps that jump context. Suggest `reorder_steps` if the sequence reads out of order.
3. **Hotspot sanity** — every step has a clear next action; hotspot copy under ~120 characters; no two hotspots with identical copy on the same screen.
4. **Links and CTAs** — inspect links and CTA targets in `get_demo`; `create_demo_links`, `update_demo_links`, and `delete_demo_links` mutate trackable links and is not an inspection tool. Check the returned targets: no empty hrefs, no localhost/staging URLs, UTMs present if the team uses them.
5. **Chapters** — long demos (15+ steps) have chapters; chapter titles match their content (`update_chapters` to fix).
6. **Voiceover consistency** — if some steps have voiceover and others don't, flag the gaps; mismatched voices across steps.
7. **Translation freshness** — use `list_demo_translations` with `targetLanguage` to inspect translated text. Compare it with the current source; do not invent a translation timestamp or claim staleness from metadata that is absent.
8. **Version note** — recommend `rename_demo_version` with a QA-passed label so the reviewed state is findable later.
## Output
A checklist per demo:
```
✅ Copy quality — clean
⚠️ Flow — step 7 references "the dashboard we just saw" but dashboard is step 9
❌ Links — step 12 CTA points to staging.acme.com
```
For a QA-only request, return findings. When fixes are requested or already approved, use `update_steps`, `update_hotspots`, `reorder_steps`, and `update_chapters` within that scope. Publication with `publish_demo` requires publication to be part of the user’s request. A metadata check alone does not prove hotspot placement, link reachability, or audio playback; mark those checks unverified until observed.
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
--- name: device-experience-auditor description: Reviews Supademo OS, browser, and country view shares and identifies demos worth checking on mobile. Use for a mobile campaign or accessibility review; device-specific completion rates are unavailable from these tools. --- # Device Experience Auditor Use audience data to prioritize a mobile playback review without inventing device conversion metrics. ## Workflow 1. **Set the scope.** Select the workspace and UTC period. Pass `viewType` explicitly. `get_device_analytics` without `demoId` combines demo and showcase traffic; pass a demo ID for a demo-specific view. 2. **Read the returned breakdowns.** Report OS and browser view shares and their `truncation` flags. These are top-five lists, so missing entries can be in the long tail. Country shares exclude unknown locations and need a coverage caveat. 3. **State the measurement limit.** The tool does not return device classes, per-device completion, or a mobile-versus-desktop conversion gap. OS names can suggest mobile traffic, but label that interpretation and avoid an exact mobile total when the list is truncated or ambiguous. 4. **Inspect candidates.** Use `get_demo` to review screenshot density, annotation length, and hotspot layout. If browser access is available, check actual playback at a mobile viewport and a desktop viewport. Distinguish observed layout problems from hypotheses based on metadata. 5. **Recommend priorities.** Rank by measured traffic and observed usability problems. Suggest a shorter duplicate, clearer annotations, or recapture at a useful zoom. Do not calculate a traffic-times-completion-gap score when completion by device is unavailable. 6. **Report.** For each demo, include the period, audience scope, observed OS/browser shares, truncation, playback evidence, and recommended action. Keep audit-only requests read-only; carry out fixes when the user has requested them. ## Supademo tool conventions Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
---
name: exec-analytics-summary
description: Converts raw Supademo analytics into a leadership-ready narrative — reach, engagement, CTA activity, and one recommendation. Use for QBRs, board updates, or justifying the demo program's budget.
---
# Exec Analytics Summary
Executives don't want completion rates; they want to know if the demo program is working. This skill translates.
## Prerequisites
- Supademo MCP connected
- The reporting period (quarter, month) and the audience (CMO, board, sales leadership)
## Workflow
1. **Aggregate the period.** List accessible demos with `list_demos(scope: "workspace")` and showcases with `list_showcases(scope: "workspace")`, following every page of both lists. Call `get_demo_analytics` for each demo, passing its returned `id` as `demoId`, and `get_showcase_analytics` for each showcase, passing its returned `id` as `showcaseId`. Use the same workspace, reporting dates, and applicable filters. These analytics tools require individual asset IDs; they do not accept a workspace-only query. Use `get_top_performing_demos` / `get_top_performing_showcases` for standouts and matching-population totals. Report any inaccessible assets or failed calls as coverage gaps.
2. **Compare like periods.** Specify UTC dates and the same `viewType`/filters for each call. Use top-performing responses’ `summary.totalViews` for their matching population, not a sum of the returned top-N page. Keep demos and showcases separate to avoid counting a showcase visit and its nested demo view as one deduplicated audience. A null previous-period delta means no prior baseline, not +100% growth.
3. **Structure the narrative — five beats, one page:**
- **Reach** — views and per-asset unique viewers, labeled with their actual definitions; do not add per-asset unique viewers into a workspace-wide people count
- **Engagement** — did they actually watch (completion), and where do they lean in (`get_demo_hotspot_performance` on the top demo)
- **Conversion** — CTA click-throughs; demos that hand off to trials/sales calls
- **Standouts** — the one demo or showcase that outperformed, and the honest laggard
- **Recommendation** — one concrete next move (double down, refresh, kill)
4. **Write for the audience.** No tool jargon ("hotspot," "step") — translate to "the pricing section," "the setup walkthrough." Percentages over raw counts unless raw counts impress.
## Output
A one-page summary in markdown, ready to paste into a doc or deck, with an appendix table of per-demo numbers for the detail-oriented.
## Guardrails
- Views and CTA clicks do not establish a trial, booked meeting, influenced revenue, or pipeline result. Include those claims only with separately provided and attributable business data; never imply causation from engagement alone.
- Flag data gaps honestly (e.g., demos with no UTM discipline can't be traced to campaigns).
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
--- name: feature-launch-demo-updater 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. --- # Feature Launch Demo Updater Ship a feature without shipping stale demos. This skill finds every demo step a product change touches and drafts the fix. ## Prerequisites - Supademo MCP connected - 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" ## Workflow 1. **Parse the change.** Extract what's user-visible: renamed features, moved navigation, new/removed buttons, redesigned screens, changed defaults. 2. **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. 3. **Inspect each candidate.** Pull `get_demo` and scan step annotations, hotspot copy, and chapter titles for mentions of the old name, flow, or screen. 4. **Produce an impact report.** | Demo | Step(s) | What's stale | Fix type | Fix types: `copy-only` (text fix), `recapture` (screenshot shows old UI), `remove` (feature no longer exists). 5. **Apply authorized copy fixes** with `update_steps` and `update_hotspots`. 6. **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`. 7. **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. ## Guardrails - Keep edits and deletions within the user’s requested or approved scope; use exact step IDs. - If a demo has translations (`list_demo_translations`), flag that they'll need regeneration after the source changes. - Verify the updated content, then use `publish_demo` when the user has authorized publication; otherwise return the draft changes. ## Supademo tool conventions Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
--- name: hotspot-dropoff-analyzer description: Analyzes Supademo completion, step engagement, and hotspot click counts to identify likely friction. Use when a demo gets traffic but completion is low; report hypotheses without presenting these metrics as an exact abandonment funnel. --- # Hotspot Drop-off Analyzer Find likely friction in a demo and tie each recommendation to available evidence. ## Workflow 1. **Collect comparable data.** Use the same UTC dates and `viewType` for `get_demo_analytics`, `get_demo_hotspot_performance`, and any needed `get_demo_sessions`. Fetch all relevant pages before filtering sessions. 2. **Keep metric meanings intact.** Hotspot performance contains click events, which can include repeated clicks. Step `viewersReached` is an engagement-weighted measure and need not form a monotonic funnel. Session completion is a percentage of steps reached, not a reliable chronological exit step. Do not derive an exact abandonment count, last step, or unique-viewer conversion rate from these fields. 3. **Identify signals.** Report the demo's completion measure, steps with relatively low engagement, and CTA or hotspot click patterns. Check final CTA activity before treating low end-step engagement as failure. Note small samples and unavailable values. 4. **Inspect the content.** Pull `get_demo` for candidate steps. Look for unclear next actions, competing hotspots, long copy, unexplained screen changes, early forms, and repetitive setup. Treat explanations as hypotheses until actual playback or additional evidence supports them. 5. **Review audience context.** `get_device_analytics` can show OS/browser view shares. It cannot show that mobile visitors abandon faster; use an actual mobile playback check for layout evidence. 6. **Recommend changes.** Return Step | Evidence | Hypothesis | Proposed fix | Tool. Use `update_steps`, `update_hotspots`, `reorder_steps`, `delete_steps`, or `update_chapters` for authorized fixes, then compare the same metrics over a later comparable period. State what remains unmeasured. A content change and a later metric increase do not by themselves establish causation. ## Supademo tool conventions Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
---
name: persona-script-adapter
description: Adapts an existing Supademo demo's script to a specific buyer persona — same click path, different narrative. Use when one product flow needs to speak to admins, end users, and executives separately.
---
# Persona Script Adapter
The clicks stay the same; the story changes. One captured flow becomes three persona-specific demos.
## Prerequisites
- Supademo MCP connected
- The source demo and a persona brief: role, what they're measured on, what they fear, vocabulary they use
## Workflow
1. **Load the source.** `get_demo` — the full step sequence and current copy.
2. **Interrogate the persona.** If the brief is thin, ask: What does this person get fired for? What number are they trying to move? Who do they have to convince internally? Their answers drive every rewrite.
3. **Rewrite the narrative, step by step:**
- **Same screens, different emphasis** — an admin sees "granular permissions"; an exec sees "nothing leaks, no tickets"
- **Reframe outcomes in their metric** — support leader: deflection rate; RevOps: time-to-first-value
- **Adjust vocabulary register** — practitioners get precision, executives get consequences
- **Rewrite the CTA** — "Start free trial" for practitioners; "See the 2-min overview" for execs who won't sign up
4. **Prepare the adaptation** as Step | Original | {Persona} version. Return it for a drafting request, or apply it to the requested variant when those edits are already authorized.
5. **Create the variant.** `duplicate_demo` (never edit the source), then `update_steps` / `update_hotspots` on the copy. Name it clearly: "{Demo} — {Persona}". Resolve or create tag IDs with `list_tags`/`create_tags`, then use `add_demo_tags` for findability.
6. **Optional:** persona-matched voiceover via `generate_voiceovers`.
## Guardrails
- Never mutate the source demo — always duplicate first.
- Don't invent capabilities the screens don't show; adaptation changes framing, not facts.
- If the click path itself is wrong for the persona (execs don't want 25 steps), recommend a trimmed duplicate instead of a re-narrated full flow.
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
---
name: product-change-mapper
description: Cross-references a changelog or upcoming release against the Supademo library and flags every demo a product change will touch — before it ships. Use in release planning so demo updates land with the launch, not weeks after.
---
# Product Change Mapper
The release notes say "redesigned settings page." This skill answers the question nobody asked in the launch meeting: which 9 demos show the old settings page?
## Prerequisites
- Supademo MCP connected
- The change list: changelog, release notes, or a launch plan (works for shipped *and* upcoming changes)
## Workflow
1. **Decompose the changes.** For each item, note the affected surface (screen/flow), the change type (rename, redesign, move, remove, add), and whether it's shipped or upcoming.
2. **Sweep the library.** `list_demos` with `list_folders`/`list_tags` to narrow by product area, then `get_demo` on candidates. Match on step copy mentioning the feature, chapter titles, and captures of the affected screens.
3. **Build the impact matrix:**
| Change | Demo | Steps affected | Severity | When |
Severity: **breaking** (demo now shows wrong/missing UI), **cosmetic** (looks dated, still accurate), **copy-only** (terminology drift).
4. **Sequence the work.** Breaking changes on high-traffic demos first (cross-reference `get_demo_analytics`). For upcoming changes, note the ship date so recaptures are scheduled for launch day, not discovered after.
5. **Mark and hand off.** For authorized tagging, resolve or create the `impacted-{release}` tag ID using `list_tags`/`create_tags`, then apply `add_demo_tags` and pass the queue to `feature-launch-demo-updater` for execution.
## Guardrails
- For a mapping-only request, return the report without changing content; apply tracking tags only when requested. Keeping mapping separate from fixing means the impact report can go in the launch plan as-is.
- For upcoming changes, never edit demos early — the live demo must match the live product until ship day. Suggest `duplicate_demo` to prep the updated version in parallel, swapping at launch.
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
--- name: prospect-showcase-builder description: Assembles a personalized Supademo showcase for a specific account — curated demos, ordered sections, personalized intro, trackable link. Use for high-value deals that deserve more than a pasted demo link. --- # Prospect Showcase Builder A digital sales room in five minutes: the three demos this account actually needs, in the order they should watch them. ## Prerequisites - Supademo MCP connected - Account context: company, evaluating team, use case, stakeholders, stage ## Workflow 1. **Curate ruthlessly.** From `list_demos` (filtered by tags), pick 3–5 demos — not ten. Order tells the story: 1. The outcome overview (why care) 2. Their use case deep-dive (why us) 3. Stakeholder-specific proof (security for IT, reporting for the exec) 2. **Propose before building.** For a planning request, show the picks, order, and section grouping. For an authorized build request, proceed with a reasonable selection and state the assumption. 3. **Build.** `create_showcase` creates a published showcase by default. If a private draft is needed, immediately set `sharing.visibility: "private"` with `update_showcase_settings`; do not imply the creation itself was atomic/private. Then `create_showcase_sections` for new grouping (e.g., "Start here" / "For your team" / "For IT") and `add_showcase_content` to slot demos. 4. **Personalize the wrapper.** Intro copy naming the account and their goal — one warm sentence, not a pitch. Add approved external resources via `add_showcase_content` with `contentType: "link"` and a `url`; use `update_showcase_settings` for the showcase CTA. `create_showcase_links` creates personalized/trackable sharing links, not outgoing resource links. 5. **Get the trackable link.** Create an account-specific link through `create_showcase_links` with a `links` array containing permitted variables/expiry; use the returned ID and URL. `get_showcase_share_info` returns canonical sharing/embed information and does not create a personalized link. Session tools have no link-ID filter and do not identify every anonymous or forwarded viewer. 6. **Hand to the rep** with the link and suggested send copy. ## Reuse pattern For repeated deal shapes, build once and `duplicate_showcase` per account, personalizing only the intro — 90 seconds per deal after the first. ## Guardrails - Create within the user’s requested scope. Reuse an existing approved template where suitable, and verify the returned showcase and section IDs. - Resolve or create workspace tag IDs with `list_tags`/`create_tags`, then tag account-specific showcases using `add_showcase_tags` for the account and `deal-room` so they're findable and archivable when the deal closes. ## Supademo tool conventions Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
--- name: share-link-follow-up description: Uses identified Supademo viewer sessions and showcase details to draft a prospect follow-up grounded in observed engagement. Use before a check-in call; link-level session filtering and inferred buying intent are not available. --- # Share Link Follow-up Draft a useful follow-up from observed engagement while preserving the limits of identification and attribution. ## Workflow 1. **Define the account and assets.** Use the user's provided prospect context and known demo/showcase IDs. A personalized link does not prove the identity of everyone who opens or forwards it. 2. **Read supported data.** Use `get_demo_sessions` or `get_showcase_sessions`; use `get_showcase_session_details` when detailed showcase activity is needed. Session search supports email/name, not company or link ID. There is no link-ID session filter. Fetch all relevant pages for client-side company filtering using returned fields, and label any unresolved account attribution. 3. **Summarize evidence.** Report observed asset activity, completion, revisit counts, and last-view date where returned. Session rows represent viewer IDs, which may be multiple devices for one person. Completion alone does not establish the exact step where a viewer stopped, time spent on a specific section, forwarding, or buying-committee activity. 4. **Choose a useful next step.** Use supplied deal context and observed interests to suggest an explanation, shorter resource, or conversation. Separate hypotheses from observed facts. No recorded engagement means no recorded signal; it does not prove disinterest or email failure. 5. **Write the draft.** Keep it brief and at account level. Reference specific content only when the data supports that claim. Do not expose individual timestamps or private viewer details in outreach. 6. **Return the draft.** Sending requires an explicit user request and an available authorized messaging tool; this skill does not grant permission to contact anyone. ## Supademo tool conventions Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
--- name: staleness-triage description: Ranks the Supademo library by refresh priority using traffic, age, and performance — refresh now, refresh soon, archive. Use quarterly, or whenever "our demos are out of date" needs turning into an actual work queue. --- # Staleness Triage "We should update our demos" is a feeling. This skill turns it into a ranked queue. ## Prerequisites - Supademo MCP connected ## Workflow 1. **Inventory.** `list_demos` for the full library. Read returned demo/version timestamps and state which timestamp represents the age signal; a version date is not necessarily the last source edit. 2. **Score each demo on two axes:** - **Exposure** — recent traffic from `get_demo_analytics`; is it embedded on high-traffic pages, in active showcases (resolve with `list_showcases`, inspect with `get_showcase`), in sales sequences? Mark embed/sequence placement unknown when that evidence is unavailable - **Staleness** — months since last edit, old branding/UI in captures, declining completion trend as a signal to inspect, not proof of outdated UI 3. **Triage into four buckets:** | Bucket | Rule | Action | | 🔴 Refresh now | High exposure × stale | Queue immediately | | 🟡 Refresh soon | Medium exposure × stale, or high exposure × slightly dated | Next cycle | | 🟢 Leave alone | Fresh, or stable performance | Nothing | | ⚫ Archive | No traffic in 90+ days, superseded | Move out of the active library | 4. **Make the queue durable.** Resolve or create `refresh-q3`/`archive-candidate` tag IDs with `list_tags`/`create_tags`, then use `add_demo_tags`; optionally move archive candidates to an Archive folder via `move_demos` when those exact moves are requested or approved. Moving is organization, not unpublishing; it may also affect public folder listings and connected integrations. 5. **Output** the triage table with per-demo evidence (traffic, last edit, trend) so priorities survive scrutiny. ## Guardrails - Archive in this workflow means move/tag; do not infer permission to delete from an audit or archive request. Deletion needs a separate, explicit request identifying the assets. - A low-traffic demo isn't automatically archivable — check whether it's load-bearing in a live showcase or embedded on a page before flagging it. - Hand the 🔴 bucket to `feature-launch-demo-updater` or `demo-qa-checklist` to execute the actual refresh. ## Supademo tool conventions Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
--- name: supademo-onboarding description: Connects a Supademo workflow to the intended account and workspace, resolves accessible assets, and explains missing tools or permissions. Use at first connection or when a demo, workspace, or feature cannot be found. --- # Supademo Onboarding Read [the tool conventions](references/tool-use.md) before using Supademo tools. 1. If the MCP connection requires authentication, use the host's Supademo sign-in flow. Do not ask the user to paste an access token into chat. 2. Call `list_workspaces`. Use a workspace named in the request or already selected in context. Ask a short clarifying question only when multiple accessible workspaces still match. 3. Resolve asset IDs with `list_demos`, `list_showcases`, `list_agents`, or `list_media_library_items`. Use returned names, IDs, pagination, and visibility; do not infer that an empty first page means the asset is absent. 4. Use `get_workspace_settings` when workspace configuration matters. Role, plan, and feature flags govern what the connection can do. Missing Agent or video tools can reflect a feature gate or a pending platform review; do not invent or call undiscovered tools. 5. Continue the requested workflow with the resolved workspace and asset IDs. If a permission or entitlement blocks it, explain the concrete limitation and any useful work that can still be completed. The plugin does not initiate subscription or credit purchases. The MCP connection represents a Supademo account and can reach its accessible workspaces. Selecting a workspace for a task does not narrow the token to that workspace or make the connection read-only. Users can revoke the connection through their connected-app/token settings.
Referenced files: 2 — file references are metadata, not package contents.
---
name: ticket-to-demo-script
description: Converts an engineering ticket, PRD, or changelog entry into a first-draft Supademo demo script — the click path to capture, per-step copy, and chapter breaks. Use when a feature ships and marketing needs its demo yesterday.
---
# Ticket to Demo Script
From "PROJ-142: Implement bulk CSV export" to a capture-ready demo script in one pass.
## Prerequisites
- Supademo MCP connected (for the build step; scripting works standalone)
- The ticket/PRD text — pasted, or pulled via a connected issue tracker
## Workflow
1. **Extract the user-facing story.** From the ticket, answer: Who asked for this? What could they not do before? What's the happy path? Ignore implementation details — the demo shows outcomes, not architecture.
2. **Draft the capture plan.** The exact click path to record, screen by screen:
```
1. Dashboard → the entry point (establishes context)
2. Click {feature entry} → the moment of discovery
3–5. The core flow, one decision per step
6. The result screen → proof it worked
7. CTA
```
Flag any screen needing seeded data ("account must have 3+ projects for this to look real").
3. **Write per-step copy.** Annotation (≤25 words, labels the action) and optional voiceover line (spoken register) for each step. Lead step 1 with the outcome, not the feature name.
4. **Suggest structure.** Chapter breaks if 10+ steps; where the CTA lands; tags to apply.
5. **Hand off for capture.** A human records the flow in Supademo.
6. **Build after capture.** Once steps exist, apply the script with `update_steps`. Create new chapter steps with `create_steps` using `type: "chapter"`, `chapterType: "Link"`, the title in `chapter.heading`, and the planned 1-based `position`; use `update_chapters` only to edit existing chapter step IDs. Apply hotspot CTAs with `update_hotspots` and optionally `generate_voiceovers`.
## Guardrails
- If the ticket is ambiguous about user-facing behavior, list the assumptions at the top of the script rather than guessing silently.
- Check `list_demos` first — the feature may already have a demo to update instead (see `feature-launch-demo-updater`).
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
---
name: top-performer-patterns
description: Reverse-engineers your best-converting Supademo demos into a reusable structural playbook — hook, length, chapter shape, CTA placement. Use before building new demos so they start from what already works.
---
# Top-Performer Pattern Extractor
Your best demos already know what converts. This skill writes it down.
## Prerequisites
- Supademo MCP connected
- Enough history for "top" to mean something (a handful of demos with real traffic)
## Workflow
1. **Identify the winners.** `get_top_performing_demos` supports server-side ranking by views, uniqueViews, or engagement. For completion or CTA engagement, fetch all relevant pages first, then sort the returned fields client-side, excluding null metrics and noting sample sizes. The returned population excludes showcases and unshared demos; do not call it the entire library.
2. **Dissect each.** `get_demo` per winner, plus `get_demo_hotspot_performance` for where viewers engage hardest. Record:
- Total steps and estimated watch time
- What step 1 shows — product outcome, problem statement, or UI tour?
- Where the "aha" screen lands (step number)
- Chapter structure and titles
- CTA count and placement (mid-demo, end, both)
- Voiceover: present or not; annotation length norms
3. **Find the pattern.** What do 4 of 5 share? Be honest when winners diverge — report "two archetypes" rather than forcing one template.
4. **Contrast with the laggards.** Pull 2–3 low-completion demos and note what the winners do that they don't. The differences are the playbook.
5. **Write the playbook:**
```
## Demo playbook — extracted {date}
- Length: {n}–{m} steps (~{x} min)
- Step 1: {pattern}
- Aha moment: by step {n}
- Chapters: {pattern}
- CTA: {pattern}
- Copy: {avg words}/step, {register}
Evidence: {demo} — {completion}%, {demo} — {completion}%...
```
## Guardrails
- Correlation caveat up front: top demos may win because of the feature they show, not their structure. The playbook is a strong prior, not a law.
- Re-run quarterly; patterns drift as the library and audience change.
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
---
name: trackable-link-generator
description: Creates trackable Supademo share links and a labeled registry per prospect, campaign, or channel — with naming conventions, UTM discipline, and expiry rules — while explaining attribution limits. Use when sharing demos anywhere you'll later want to know who watched.
---
# Trackable Link Generator
One generic share link tells you "someone watched." Separate links help organize distribution and personalization, but do not identify every viewer or provide a link-ID filter in session tools.
## Prerequisites
- Supademo MCP connected
- What's being shared (demo or showcase) and at what grain: per-prospect, per-campaign, or per-channel
## Workflow
1. **Pick the grain.**
- **Per-prospect** — outbound and active deals; one link per account to organize personalization and distribution. `share-link-follow-up` can use identified-viewer data, but cannot filter sessions by that link ID
- **Per-campaign** — launches, newsletters, paid; one link per campaign per asset
- **Per-channel** — the same demo embedded on the site vs linked in email vs posted on social gets separate links, or attribution is guesswork
2. **Label the registry** so links stay legible at scale. The MCP link schemas do not have a link-name field; keep this human label in the registry:
`{asset}--{campaign-or-account}--{channel}--{yyyymm}` (e.g., `onboarding-demo--acme-corp--outbound--202608`)
3. **Create the links.** `create_demo_links` for demos, `create_showcase_links` for showcases; use the URL and ID returned by link creation. `get_showcase_share_info` only provides canonical sharing/embed information. Pass a `links` array with `variables` and optional `expiresAt`; update operations change expiry/avatar colors, not variable values. Set expiry on deal-specific links where supported — a demo link in a lost deal's inbox shouldn't work forever.
4. **Add UTM discipline** for links landing in email/ads/social: consistent `utm_source` / `utm_medium` / `utm_campaign` matching the naming convention, so demo analytics and web analytics agree.
5. **Wire personalization (optional).** If the demo uses dynamic variables (see `demo-personalizer`), append the values as query params per link — `?v_name=Sam&v_company=Acme` (URL-encode each value; created link variables use keys without the `v_` prefix) — so each prospect's link renders their personalized demo.
6. **Output a link registry** the team can paste into the CRM or a sheet:
| Link | Asset | Audience | Channel | Created | Expires |
7. **Close the loop.** Use `share-link-follow-up` for supported identified-viewer analysis. Session tools cannot filter by link ID. Analytics tools support `source`/UTM-source filtering, and `list_showcase_analytics_sources` lists showcase sources; source-level analytics are not proof of individual prospect identity.
## Guardrails
- Keep account-specific links separate so personalization and the distribution registry stay accurate; a distinct link alone does not prove account attribution.
- Keep personal data out of URL params beyond first name and company; emails, phone numbers, or anything sensitive belongs in a lead-capture form, not a query string.
- When requested, expire or delete the exact obsolete deal-room links with the supported link operation. There is no link-archive operation, and link expiry does not unpublish the canonical asset URL.
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
--- name: translation-qa-reviewer description: Reviews machine-translated Supademo demos against a glossary and brand terminology, fixing errors string-by-string. Use before a localized demo ships to a regional campaign or gets embedded on a localized site. --- # Translation QA Reviewer Machine translation gets you 90% there. This skill finds the 10% that embarrasses you in front of native speakers. ## Prerequisites - Supademo MCP connected - A demo with at least one translation (`list_demo_translations`) - Glossary / brand terminology list (ask if missing) ## Workflow 1. **Load both versions.** `get_demo` for the source, `list_demo_translations` with `targetLanguage` for full translated strings and entity IDs; without it, the tool returns language summaries. 2. **Run the checks, step by step:** - **Glossary violations** — product and feature names that got translated when they shouldn't be - **Truncation risk** — translated CTAs and hotspot copy significantly longer than source (German +30% is normal; flag anything that will overflow a button) - **Register** — consistent formal/informal address throughout; B2B defaults to formal in most markets - **Untranslated leftovers** — source-language strings that slipped through - **Broken variables** — numbers, dates, or placeholders mangled in translation - **False friends** — obviously wrong sense-for-sense choices (flag for native review rather than guessing) 3. **Fix what's certain.** `set_demo_translation_text` for glossary violations, leftovers, and truncations. Leave judgment calls flagged, not fixed. 4. **Output a QA report:** | Step | Issue | Severity | Fixed / Needs native review | ## Guardrails - You are a safety net, not a substitute for one native-speaker pass before high-stakes launches. Say so in the report. - Never regenerate the whole translation to fix individual strings — that destroys previous manual fixes. ## Supademo tool conventions Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
---
name: video-to-demo-converter
description: Builds a Supademo demo from uploaded video or prepared screenshots, then adds copy and structure. Use for a recording-based demo; explain when a requested screenshot sequence needs separate capture or extraction.
---
# Video to Demo Converter
Turn a recording or prepared media sequence into a demo using the media handles Supademo actually supports.
## Workflow
1. **Choose the output.** One uploaded video becomes one video step. A screenshot walkthrough needs separate image assets, one per step. The MCP tools do not automatically split a recording into screenshot steps. If the user needs that output, prepare the capture/extraction plan and use a separately available, authorized capture workflow, or ask for the screenshots.
2. **Get trusted media handles.** Use conversation handles if present. For local files, call `create_upload_job`, provide its upload URL, and call `get_upload_job` after upload until processing completes. Use returned `videoId` for a completed video, or image URL, width, and height for each image. For explicitly requested library reuse, call `list_media_library_items`: a video's `itemId` is its `videoId`; image items provide `url`, `width`, and `height`. If an image lacks positive dimensions, request a completed upload with those values rather than inventing them.
3. **Build.** For a new demo, call `create_demo_from_uploaded_media` with the ordered media array. Map selected library videos to `{ type: "video", videoId: itemId }` and images to `{ type: "image", imageUrl: url, width, height }`. Each item becomes one regular step in that order. Preserve the returned demo and step IDs. To add library items to an existing demo instead, resolve the target with `get_demo`, then call `create_step_from_media_library_item` with that `demoId`, the selected `itemId`, and its `type`. That tool adds a step; it does not create a demo or return a media handle.
4. **Edit the result.** Read `get_demo`. Add clear step copy with `update_steps` and appropriate hotspots with `create_hotspots`. Create new task-based chapter steps with `create_steps` using `type: "chapter"`, `chapterType: "Link"`, the title in `chapter.heading`, and the planned 1-based `position`; use `update_chapters` to edit existing chapter step IDs. Use `reorder_steps` or `delete_steps` only for changes included in the user's request. There is no generic step-merge tool. Removing a step does not trim dead air inside a video.
5. **Handle audio explicitly.** Do not claim the source narration was removed or restored by conversion. Inspect the resulting video/audio. If new narration is requested, use `voiceover-producer`; adding generated voiceover is separate from editing or muting source video audio.
6. **Verify.** Use `get_demo` and `demo-qa-checklist`. Check the actual media, step order, copy, links, and playback when browser access is available. Publish only when publication is part of the authorized task.
## Source review
Inspect for private data, notifications, and unreadable captures before sharing. Explain any required recapture or redaction, and distinguish completed edits from work the available tools cannot perform.
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
---
name: voiceover-producer
description: Writes a per-step voiceover script for a Supademo demo and generates AI voiceovers in a chosen voice, optionally with background music. Use when turning a silent click-through demo into a narrated product tour.
---
# Voiceover Producer
Turn a silent demo into a narrated tour: script it, pick a voice, generate, review.
## Prerequisites
- Supademo MCP connected
- The demo to narrate
## Workflow
1. **Read the demo.** `get_demo` — understand what each step shows and what the annotation already says.
2. **Draft the script.** Write one short voiceover line per step:
- Spoken register, not written — contractions, short sentences, no bullet-speak
- Don't read the annotation aloud verbatim; the voiceover adds context, the annotation labels the action
- 8–15 words per step; the viewer should never wait for narration to finish
- Open with the outcome ("Here's how you cut onboarding time in half"), not the feature name
3. **Prepare the script** as a table (Step | On screen | Voiceover line). For a drafting request, return it for review. For an authorized generation request, use the supplied or requested script within that scope; do not repeat an existing approval.
4. **Pick the voice.** Use an already selected voice, or `list_voices` to resolve the requested voice. Offer 2–3 options only when a meaningful preference remains missing.
5. **Generate.** `generate_voiceovers` with the approved script and chosen voice.
6. **Optional music.** If requested, use `list_background_music` and apply the selected track through supported `update_demo_settings` fields. Listing a track alone does not apply it.
7. **Review pass.** Re-read `get_demo` and verify generated audio is ready for each intended step; generation may be asynchronous. Listen when playback is available, and mark pronunciation/timing unverified otherwise. Flag steps where the line runs longer than the step naturally displays.
## Guardrails
- If steps already have voiceovers (human-recorded or previous AI), overwrite only when replacement of that existing audio is included in the user’s authorization — removing audio is `delete_voiceover` and it's destructive.
- Keep one voice per demo. Mixing voices mid-demo reads as broken.
- If the demo has translations, note that each language needs its own voiceover pass after `generate_demo_translation`.
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
---
name: weekly-performance-digest
description: Generates a recurring "top demos this week" digest from Supademo analytics — views, completion, CTA clicks, movers up and down — formatted for Slack or email. Use for a Monday-morning demo performance ritual.
---
# Weekly Performance Digest
The Monday-morning answer to "how are our demos doing?" — without opening a dashboard.
## Prerequisites
- Supademo MCP connected
## Workflow
1. **Pull the leaders.** `get_top_performing_demos` and `get_top_performing_showcases` for the last 7 days.
2. **Pull the trend.** Use equal UTC periods and the same explicit `viewType` and filters. Null deltas mean no prior baseline. Use response summaries for matching-population totals; the top-five page is not a workspace total.
3. **Enrich the top 5.** `get_demo_analytics` per top demo: views, unique viewers, completion rate, CTA click-through.
4. **Find the movers.** Demos that jumped or dropped meaningfully week-over-week — a demo that doubled its views because it got embedded somewhere new is the story, not the perennial #1.
5. **Format the digest:**
```
📊 Demo performance — week of {date}
Top demos
1. {name} — {views} views ({±}% WoW), {completion}% completion
...
📈 Mover of the week: {name} — {what changed}
📉 Worth a look: {name} — completion fell {x}pts
💡 One takeaway: {single actionable insight}
```
6. **Keep it short.** One screen of Slack. Numbers rounded. One insight, not five.
## Guardrails
- Never invent a "why" for a metric change — if the cause isn't visible in the data, say "worth investigating," not a fabricated explanation.
- Select the intended workspace from the request/context and `list_workspaces`; ask only if multiple matches remain ambiguous.
- A recurring digest needs a separate host scheduling capability and an explicit user request to schedule it. Formatting for Slack/email does not authorize sending; deliver a draft unless the user has explicitly requested delivery through an available messaging tool.
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.
Referenced files: 1 — file references are metadata, not package contents.
---
name: workspace-librarian
description: Audits and tidies the Supademo workspace — naming conventions, tags, folder structure, duplicates, and orphaned drafts. Use when nobody can find anything, or quarterly before it gets that way.
---
# Workspace Librarian
Every demo workspace drifts toward "Untitled (3)" and a folder called "misc." This skill drifts it back.
## Prerequisites
- Supademo MCP connected
## Workflow
1. **Take inventory.** `list_folders`, `list_demos(scope: "workspace")`, `list_showcases(scope: "workspace")`, `list_tags` — the map of accessible workspace assets and where they belong. Follow all pages of both asset lists, including teammates' shared content. Traverse child folders with `list_folders`, passing each listed folder's `id` as `parentId`; another user's private assets remain outside this inventory.
2. **Audit against library hygiene rules:**
- **Naming** — inconsistent patterns ("Onboarding Flow" vs "demo_onboarding_v2_FINAL"); propose one convention: `{Product area} — {Flow} ({Persona/variant})`
- **Tags** — untagged demos, near-duplicate tags (`sales` vs `Sales` vs `sales-team`), tags used once
- **Folders** — empty folders, junk-drawer folders, demos sitting at root
- **Duplicates** — same flow captured twice; use `get_demo_analytics` to recommend which to keep and propose organizing the other with folders/tags. Removing a duplicate requires explicit authorization identifying the asset. `merge_demos` combines content into a new demo and preserves every source; it does not remove duplicates.
- **Orphaned drafts** — unpublished demos untouched for 60+ days
- **Expired deal rooms** — account-specific showcases (`deal-room` tag) for closed deals
3. **Propose the cleanup plan** — a full change list grouped by action, with counts. Nothing executes yet.
4. **Apply the authorized plan, in dependency order.** Existing user authorization counts; for a review-only request, stop at the change list:
- Renames via demo/folder updates and `rename_folder`
- Tag consolidation via `create_tags`, `update_tags`, and `delete_tags`. Resolve tag IDs first; use `add_demo_tags`/`add_showcase_tags` to preserve unrelated associations and `remove_demo_tags`/`remove_showcase_tags` to detach only superseded tags. Workspace tag deletion detaches the tag from every demo/showcase, so include all affected assets in that change’s scope
- Moves via `move_demos` / `move_showcases`
- Content combinations via `merge_demos` only when the user requests a combined demo from the exact source IDs in the authorized plan; verify the returned new demo ID and content. Keep this separate from duplicate cleanup, and preserve the originals unless their removal is explicitly authorized
- Empty folders last via `delete_folder`. Immediately before deletion, re-read the folder's entry through `list_folders` for its parent and confirm `demoCount`, `showcaseCount`, `videoCount`, and `childFolderCount` are all zero. A missing entry, permission failure, or incomplete inventory does not establish emptiness. Skip any folder whose emptiness cannot be verified; deleting a non-empty folder can archive demos, move showcases, or delete library videos
5. **Report** before/after counts: untagged 34 → 0, root-level demos 12 → 0, tags 61 → 28.
## Guardrails
- Do not infer permission to delete demos or showcases from a cleanup request. Archive here means organizing with folders/tags, and does not unpublish an asset. Deletion needs an explicit request identifying the assets.
- Verify merge source IDs, the returned new demo ID, and resulting content before moving on. Do not count a merge or folder/tag move as removing duplicates. Ask only for missing scope or authorization; do not repeat approvals the user has already supplied.
- Save the naming convention to the team's docs so the drift restarts slower.
## Supademo tool conventions
Read [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling SupadPreview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
Migrates combined MCP actions to independently exposed tools for showcase content/sections/sharing, Demo Hub categories/content, quick links, demo sharing, workspace tags, and asset tag assignments. Updates all affected workflow skills and reviewer cases for the shared 151-tool catalog. Corrects session-summary overwrite metadata. Existing MCP endpoint and OAuth configuration are retained; clients must refresh tools after deployment.
Declared in the saved package. Remote tools may change independently.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 15, 2026.
plugin_asdk_app_6a53f7d79b5c81919a02e9814eb9f070
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.