← 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": "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.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 217
    }
  ],
  "name": "exec-analytics-summary",
  "skill_md_contents": "---\nname: exec-analytics-summary\ndescription: 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.\n---\n\n# Exec Analytics Summary\n\nExecutives don't want completion rates; they want to know if the demo program is working. This skill translates.\n\n## Prerequisites\n\n- Supademo MCP connected\n- The reporting period (quarter, month) and the audience (CMO, board, sales leadership)\n\n## Workflow\n\n1. **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.\n2. **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.\n3. **Structure the narrative — five beats, one page:**\n   - **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\n   - **Engagement** — did they actually watch (completion), and where do they lean in (`get_demo_hotspot_performance` on the top demo)\n   - **Conversion** — CTA click-throughs; demos that hand off to trials/sales calls\n   - **Standouts** — the one demo or showcase that outperformed, and the honest laggard\n   - **Recommendation** — one concrete next move (double down, refresh, kill)\n4. **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.\n\n## Output\n\nA 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.\n\n## Guardrails\n\n- 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.\n- Flag data gaps honestly (e.g., demos with no UTM discipline can't be traced to campaigns).\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: 2bd4f8bb3485ca165c4685823fdbb7f65f94bcde1913ec222db2cdd7c44ce8ae