Individual skill
content-refresh-system
Systematic content refresh discipline. Quarterly audits, refresh prioritization (which pieces, when, how deep), refresh-vs-merge-vs-delete decisions, the lifecycle that distinguishes intentional refresh from set-and-forget decay. Builds on the refresh sections of pillar-content-architecture and editorial-qa with a program-level discipline. Triggers on content refresh, content decay, content audit, refresh prioritization, content lifecycle, refresh strategy, traffic decay, ranking drop, content freshness, evergreen content, content maintenance. Also triggers when traffic is eroding silently across an aging content library, when teams cannot decide which pieces to refresh, or when refresh work is happening but the impact is unclear.
dist/codex/.agents/skills/content-refresh-system/SKILL.md
Source commit 9b90db257f7395fab76ff9bfcb808456709f6af3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,042
- Repository last updated
- Oct 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- anthropic Repository topic
- mcp Repository topic
- seo Repository topic
- web-development Repository topic
- agent-skills Repository topic
- claude-code Repository topic
- product-management Repository topic
- web-design Repository topic
- writing Derived category
- engineering Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 25,653 bytesSKILL.mdcore · 25,653 bytesreferences/_claude-frontmatter-extras.yamlasset · 536 bytesreferences/audit-cadence-patterns.mddoc · 10,396 bytesreferences/common-refresh-failures.mddoc · 11,774 bytesreferences/effectiveness-measurement.mddoc · 11,055 bytesreferences/re-promotion-after-refresh.mddoc · 10,690 bytesreferences/refresh-depth-decision.mddoc · 10,655 bytesreferences/refresh-execution-patterns.mddoc · 10,036 bytesreferences/refresh-prioritization-matrix.mddoc · 11,361 bytesreferences/refresh-signals-checklist.mddoc · 10,605 bytesreferences/refresh-vs-merge-vs-delete.mddoc · 10,295 bytes
Read excerpt
# Content Refresh System
A senior editorial leader's playbook for systematic content refresh. The discipline that distinguishes intentional refresh programs from set-and-forget decay, and the prioritization framework that prevents both over-refresh (refresh-everything-on-calendar) and under-refresh (refresh-nothing-until-traffic-collapses).
Content decays. Search behavior shifts; SERP intent reshapes; facts go stale; competitors publish stronger pieces; the brand's own positioning evolves past what older pieces represent. Programs that ignore this reality watch traffic erode silently across the library. Programs that overreact (rewriting everything on calendar) burn editorial capacity that should be producing new flagship work. The discipline is in the middle: refresh what matters when signals say so, and document the decisions so the program is auditable.
This skill is the program-level refresh discipline across the whole content library. It builds on `pillar-content-architecture`'s hub-level refresh consideration (refresh as ONE consideration in hub design) and `editorial-qa`'s pre-publish quality gate (this skill is post-publish lifecycle, not pre-publish QA). Together those skills cover content quality at the moments quality decisions get made; this skill covers the moments between, when content is in the field and decaying or holding.
The voice is the senior editorial leader who has watched refresh programs fail in both directions and who has shipped the systems that produced durable refresh discipline.
When to use this skill: building a refresh program from scratch, auditing why refresh work is happening but traffic is not responding, designing the prioritization that keeps refresh tractable across a 200-piece or 2,000-piece library, or fixing a refresh program that is eating editorial capacity without clear results.
---