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.
Install / Use
npx skills add rampstackco/claude-skills --skill content-refresh-systemInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of content-refresh-system
content-refresh-system scores 86/100 on our quality scale, 2455th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 25 KB long, well organised into 16 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 902 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so content-refresh-system is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
content-refresh-system compared with similar skills
All 4 of these similar skills score higher than content-refresh-system; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| content-refresh-system (this skill)by rampstackco | 86 | 902 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install content-refresh-system?
- Run
npx skills add rampstackco/claude-skills --skill content-refresh-system. The install tabs above show the steps for each supported agent. - Which AI agents does content-refresh-system work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is content-refresh-system safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is content-refresh-system still maintained?
- The repository was last updated about 2 months ago, so content-refresh-system is actively maintained.
Skill content
View source on GitHubname: content-refresh-system description: "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." category: content catalog_summary: "Systematic content refresh: quarterly audits, refresh prioritization, refresh-vs-merge-vs-delete decisions, the lifecycle discipline that distinguishes intentional programs from set-and-forget decay" display_order: 10
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.
What this skill covers
This skill spans the post-publish lifecycle of content. The content suite distinction:
content-strategyis program scope: what to produce.pillar-content-architectureis HUB scope; refresh appears as ONE consideration in hub design.content-brief-authoringis per-piece scope at production time.content-and-copyis execution scope at production time.editorial-qais gate scope: pre-publish verification.content-refresh-system(this skill) is lifecycle scope: program-level refresh discipline across the whole content library, after pieces are in the field.
The audience: editorial leads, content directors, content ops managers, in-house teams running content libraries of 50-5,000+ pieces, agencies maintaining client content programs across years.
What is not in scope: writing the refreshed pieces themselves (that is content-and-copy), the brief that drives the refresh (that is content-brief-authoring), the pre-publish gate on the refreshed piece (that is editorial-qa). This skill is the prioritization and lifecycle discipline; the actual content work plugs into the existing skills.
Refresh-everything vs refresh-nothing vs triaged-refresh
The keystone framing. Two failure modes plus the discipline.
Refresh-everything. Full rewrites on calendar. Every piece gets a refresh on a 12-month or 18-month rotation regardless of signals. Output: editorial capacity consumed by maintenance work that often was not needed, while strong pieces are touched into worse versions and weak pieces consume the same effort as flagship pieces. Cost: opportunity cost on new flagship production; maintenance fatigue in the editorial team; some pieces that were performing well get diluted by unnecessary edits.
Refresh-nothing. Set-and-forget. Pieces ship and never get touched again. Output: traffic decays silently across the library as facts go stale, competitors publish stronger pieces, and SERP intent shifts away from the piece's framing. The library's compounding value erodes invisibly until an algorithm update or a competitor's flagship piece exposes the rot. Cost: cumulative traffic loss that nobody attributes to refresh failure because the loss is gradual; trust loss when readers find stale facts in pieces they expected to be current.
Triaged-refresh. Refresh what matters when signals say so. Audit cadence catches decay early; prioritization concentrates effort on high-value-decaying pieces; weak pieces get refresh-vs-merge-vs-delete dispositions instead of automatic refresh; the program is auditable because every refresh decision was a deliberate response to specific signals. Output: editorial capacity preserved for new production; the library's compounding value protected; refresh work is seen, understood, and measured.
The litmus test. Ask of any refresh decision: what signal triggered this refresh, what depth of refresh did the signal warrant, what outcome do we expect, and how will we measure whether the refresh worked? If the answer is "it was scheduled" or "we always refresh after 12 months," the program is on calendar rather than on signal.
Refresh signals
Five categories of signal that trigger refresh consideration. Pieces that show no signals do not need refresh; pieces that show multiple signals are higher priority.
Traffic decay. Organic traffic to the piece is trending down over a 90+ day window beyond the seasonal baseline. The decay can be slow (5-10% over a year) or sharp (40%+ in a month after an algorithm update). Slow decay typically indicates content drift; sharp decay typically indicates external change.
Ranking drops. The piece is losing position on its target keywords. Drops from page 1 to page 2-3 are particularly consequential; drops within page 1 (position 3 to position 7) are less so but still tracked. Persistent ranking drops over 30+ days indicate a real shift, not search-result volatility.
Factual staleness. The piece contains statistics, references, examples, or claims that are dated. A 2018 stat in a 2026 piece on a fast-moving topic is staleness; a piece that references defunct products or platforms is staleness; a piece that uses pre-shift framings ("AI is starting to influence search" in 2026) is staleness.
SERP intent shift. The dominant SERP format for the target keyword has changed. The piece was written when articles ranked for the keyword; now the SERP wants product comparisons, video, or AI-overview-style answers. The piece may still rank but increasingly for the wrong reason.
Content drift. The piece's positioning no longer matches the brand's current positioning. Voice has evolved; the brand's POV on the topic has sharpened or shifted; the piece reads as the brand-of-three-years-ago. Internal signal more than external; readers may not notice but the team will.
The audit. Every piece in the library can be characterized by which signals it shows. Pieces with zero signals are stable; pieces with one or two signals warrant attention; pieces with three or more signals are typically in active decay.
Detail in references/refresh-signals-checklist.md.
The audit cadence
How often to look. Two cadences with different tradeoffs.
Quarterly audit. A formal review of the content library every 90 days. The team pulls traffic, ranking, and recency data; reviews each piece against the signals; assigns dispositions (refresh, merge, delete, or leave alone). Output: a refresh queue with priorities and a backlog of merge/delete decisions.
- Strength: predictable, auditable, fits naturally into editorial calendar planning.
- Weakness: 90-day delay in detecting sharp decay; piece that lost 40% traffic in week 2 of a quarter is in decay for 75 days before the audit catches it.
Continuous monitoring. Automated detection of traffic and ranking shifts with alerts when thresholds are crossed. Pieces that lose more than X% traffic in Y days trigger a review.
- Strength: catches sharp decay early; allows fast response to algorithm updates.
- Weakness: requires monitoring infrastructure; can produce alert fatigue if thresholds are too tight; misses slow decay that does not cross thresholds.
The hybrid pattern. Most strong refresh programs run both. Quarterly audits catch slow decay, content drift, and pieces that are stable but no longer match the brand's current positioning. Continuous monitoring catches sharp decay and algorithm-update fallout. The two cadences cover different failure modes.
Detail in references/audit-cadence-patterns.md.
Refresh prioritization
Prioritization is the discipline. Most libraries have more pieces showing signals than the team has capacity to refresh. Prioritization concentrates effort on the pieces where refresh produces the most value.
The 2x2 matrix: piece value (high vs low) crossed with traffic state (decaying vs stable).
High-value, decaying. Top priority. Pieces that drive meaningful traffic, conversions, or topical authority and are losing position. Refresh these first; the traffic loss compounds and the lost equity is hard to recover.
High-value, stable. Monitor; do not refresh proactively. Pieces that are performing should not be touched without clear signal; refresh-everything-on-calendar treats this quadrant the same as the high-value-decaying quadrant and damages performance.
Low-value, decaying. Audit for merge or delete. Pieces with low traffic that are decaying further are usually candidates for merge (consolidate into a stronger sibling piece) or delete (and 301 to the closest sibling). Refresh on these pieces rarely justifies the effort; the underlying issue is usually that the piece never had strong demand.
Low-value, stable. Leave alone. Low traffic is the floor; the piece is not costing anything to keep. Touching these pieces in a refresh program burns capacity for no return.
The matrix shifts the program from refresh-everything to refresh-the-quadrant-that-warrants-it. Detail in references/refresh-prioritization-matrix.md.
Refresh depth options
Not every refresh is the same kind of work. Four depth levels.
Light edit. Update statistics, replace dead links, fix factual errors, swap dated examples. Keeps the piece's structure and argument intact. Time investment: 30-90 minutes per piece. Use when the piece is structurally sound and only the surface details have aged.
Substantial revision. Light edit plus rewrite of 1-3 sections that have aged badly. Update the introduction or closing. Add coverage of topics that emerged after the piece was written. Time investment: 2-4 hours per piece. Use when the piece's structure is sound but specific sections have become weak.
Full rewrite. Keep the URL and topic; rewrite the piece end-to-end. Time investment: similar to writing a new piece, sometimes more because of the constraint of preserving the
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
