← 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": "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.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 217
}
],
"name": "staleness-triage",
"skill_md_contents": "---\nname: staleness-triage\ndescription: 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.\n---\n\n# Staleness Triage\n\n\"We should update our demos\" is a feeling. This skill turns it into a ranked queue.\n\n## Prerequisites\n\n- Supademo MCP connected\n\n## Workflow\n\n1. **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.\n2. **Score each demo on two axes:**\n - **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\n - **Staleness** — months since last edit, old branding/UI in captures, declining completion trend as a signal to inspect, not proof of outdated UI\n3. **Triage into four buckets:**\n | Bucket | Rule | Action |\n | 🔴 Refresh now | High exposure × stale | Queue immediately |\n | 🟡 Refresh soon | Medium exposure × stale, or high exposure × slightly dated | Next cycle |\n | 🟢 Leave alone | Fresh, or stable performance | Nothing |\n | ⚫ Archive | No traffic in 90+ days, superseded | Move out of the active library |\n4. **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.\n5. **Output** the triage table with per-demo evidence (traffic, last edit, trend) so priorities survive scrutiny.\n\n## Guardrails\n\n- 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.\n- 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.\n- Hand the 🔴 bucket to `feature-launch-demo-updater` or `demo-qa-checklist` to execute the actual refresh.\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: bbcb9ee4c8dcbd4aa1e060b2121774edf46b0ef4cd585febf746f7936934f8f9