content-refreshlisted

# Content Refresh Skill Detects content decay, prioritizes refresh candidates, generates briefs, and tracks refresh effectiveness. **Universal rule**: no company, domain, or GSC property is ever hardcoded. Everything client-specific comes from `clients/<slug>/client.json` and the client context. GSC is the PREFERRED signal source, never a prerequisite: the skill degrades gracefully through the signal cascade below. ## Commands | Command | Purpose | |---------|---------| | `/content-refresh <client>` | Dashboard: queue, recent refreshes, tracking | | `/content-refresh scan <client>` | Run decay scan (manual trigger) | | `/content-refresh queue <client>` | Show prioritized refresh queue | | `/content-refresh <client> [url]` | Check specific URL's refresh status | | `/content-refresh report <client>` | Effectiveness report | --- ## Client Parameters (resolve FIRST) From `clients/<slug>/client.json`: `domain`, `url`, `gsc_property`, `language`. Data reserve: `clients/<slug>/data/` (crawl + DataForSEO baseline written by seo-collect). Outputs: `clients/<slug>/outputs/refresh/`. --- ## Signal Sources (cascade, never abort) | Priority | Source | Signals available | Condition | |---|---|---|---| | 1 | **GSC, via seo-monitoring** (`outputs/monitoring/`: latest `gsc-*.json` export, snapshots, history; direct gsc-mcp query ONLY if monitoring has never run) | clicks, impressions, CTR, positions per page (the full detection) | GSC access connected for this client | | 2 | **DataF