← 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": "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.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 217
}
],
"name": "weekly-performance-digest",
"skill_md_contents": "---\nname: weekly-performance-digest\ndescription: 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.\n---\n\n# Weekly Performance Digest\n\nThe Monday-morning answer to \"how are our demos doing?\" — without opening a dashboard.\n\n## Prerequisites\n\n- Supademo MCP connected\n\n## Workflow\n\n1. **Pull the leaders.** `get_top_performing_demos` and `get_top_performing_showcases` for the last 7 days.\n2. **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.\n3. **Enrich the top 5.** `get_demo_analytics` per top demo: views, unique viewers, completion rate, CTA click-through.\n4. **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.\n5. **Format the digest:**\n\n```\n📊 Demo performance — week of {date}\n\nTop demos\n1. {name} — {views} views ({±}% WoW), {completion}% completion\n...\n\n📈 Mover of the week: {name} — {what changed}\n📉 Worth a look: {name} — completion fell {x}pts\n💡 One takeaway: {single actionable insight}\n```\n\n6. **Keep it short.** One screen of Slack. Numbers rounded. One insight, not five.\n\n## Guardrails\n\n- Never invent a \"why\" for a metric change — if the cause isn't visible in the data, say \"worth investigating,\" not a fabricated explanation.\n- Select the intended workspace from the request/context and `list_workspaces`; ask only if multiple matches remain ambiguous.\n- 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.\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: ccb3254bd31e87bb34639794de3c749bcda92dbb008bcf06811dde563fd30d27