---
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; `list_demo_versions` per demo for last-edited dates.
2. **Score each demo on two axes:**
   - **Exposure** — recent traffic from `get_demo_analytics`; is it embedded on high-traffic pages, in active showcases (`list_showcases` contents), in sales sequences?
   - **Staleness** — months since last edit, old branding/UI in captures, declining completion trend (a demo whose completion sagged 15 points often shows a product that no longer looks like that)
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.** Tag with `set_demo_tags` (`refresh-q3`, `archive-candidate`); optionally move archive candidates to an Archive folder via `move_demos` — with confirmation, never silently.
5. **Output** the triage table with per-demo evidence (traffic, last edit, trend) so priorities survive scrutiny.

## Guardrails

- Never delete demos. Archive means move/tag; deletion is a human decision made elsewhere.
- 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.