Flagship Skill · Content refresh system

The content refresh system skill.

Refresh on signal, not on calendar.

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 and under-refresh. Quarterly audits, refresh prioritization, refresh-vs-merge-vs-delete decisions, the lifecycle that protects the library's compounding value.

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.

View the skill on GitHubBrowse the full catalog

What this skill is for

The lifecycle-scope skill in the content suite.

The content suite spans strategy, hub architecture, briefs, execution, scaled production, gates, and workflow. This skill is the lifecycle layer: program-level refresh discipline across the whole content library, after pieces are in the field. It builds on pillar-content-architecture (hub-level refresh) and editorial-qa (pre-publish gate) with the post-publish discipline both leave to a separate skill.

  1. 01

    content-strategyPROGRAM scope

    Decides what to produce.

  2. 02

    pillar-content-architectureHUB scope

    Designs the topical hub structure. Refresh as one consideration in hub design.

  3. 03

    content-brief-authoringPER-PIECE scope

    Briefs each piece.

  4. 04

    content-and-copyEXECUTION scope

    Writes each piece.

  5. 05

    long-form-content-frameworksLONG-FORM PIECE scope

    Structural patterns for individual long-form pieces.

  6. 06

    programmatic-seoSCALED scope

    Generates pages at scale from data.

  7. 07

    editorial-qaGATE scope

    Verifies before publish.

  8. 08

    ai-content-collaborationWORKFLOW scope

    How humans and AI compose across all content stages.

  9. 09

    content-refresh-systemLIFECYCLE scope (this skill)

    Post-publish refresh discipline across the whole library. Signals, prioritization, dispositions, effectiveness measurement.

  10. 10

    content-repurposingTRANSFORMATION scope

    Turning one piece into many derivative formats.

  11. 11

    content-distributionCHANNEL scope

    Getting content to audiences via owned, earned, paid channels.

The keystone distinction

Three positions. Both extremes are failure modes.

Programs that refresh everything on calendar burn capacity that should be producing new flagship work. Programs that refresh nothing watch traffic erode silently across the library. The discipline is in the middle.

Failure mode

Refresh-everything

Full rewrites on calendar. Every piece on a 12-month rotation regardless of signals. Strong pieces get touched into worse versions; capacity goes to maintenance work that often was not needed.

Failure mode

Refresh-nothing

Set-and-forget. Pieces ship and never get touched again. Traffic decays silently as facts go stale, competitors publish stronger pieces, SERP intent shifts. The library's compounding value erodes invisibly.

The discipline

Triaged-refresh

Refresh what matters when signals say so. Audits catch decay early; prioritization concentrates effort on high-value-decaying pieces; weak pieces get refresh-vs-merge-vs-delete dispositions instead of automatic refresh.

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," the program is on calendar rather than on signal.

The prioritization matrix

Value crossed with traffic state. Four quadrants, four strategies.

Without prioritization, refresh work happens on the cheapest pieces or the most visible pieces. With prioritization, capacity concentrates on the quadrant where refresh produces the most value. The matrix is what turns a refresh queue from a backlog into a strategy.

Decaying

Stable

High value

Top priority

Refresh now

Substantial revision or full rewrite. The traffic loss compounds; lost equity is hard to recover.

Low risk

Monitor

Do not refresh proactively. Pieces that are working should not be touched without clear signal.

Low value

Disposition

Audit for merge or delete

Refresh rarely justifies effort. The underlying issue is usually weak demand. Consolidate or redirect.

No action

Leave alone

Low traffic is the floor; the piece is not costing anything. Touching these pieces burns capacity.

Programs that adopt the matrix typically allocate 60-70% of refresh capacity to the high-value-decaying quadrant, 15-20% to merge and delete dispositions in the low-value-decaying quadrant, and 5-10% to the rare content-drift refresh in the high-value-stable quadrant.

The framework

Twelve considerations for content refresh.

When designing or auditing a refresh program, walk these 12 considerations.

  1. 01Triaged-refresh, not refresh-everything
  2. 02Five signal categories named
  3. 03Audit cadence: quarterly + continuous
  4. 04Prioritization matrix applied
  5. 05Depth matched to signal strength
  6. 06Disposition: refresh, merge, or delete
  7. 07Single ownership per refresh
  8. 08Capacity allocation explicit
  9. 09Re-promotion built into workflow
  10. 10Per-refresh tracking and logging
  11. 11Effectiveness measured at 30 and 90 days
  12. 12The-refresh-that-did-not-work review

What is in the skill

Thirteen sections covered in the body.

The SKILL.md spans the refresh discipline from the keystone triaged-refresh framing through signals, audit cadence, prioritization, depth, dispositions, execution, re-promotion, effectiveness measurement, and the failure-mode catalog.

  1. 01

    What this skill covers

    Post-publish lifecycle scope. Distinction from pillar-content-architecture (hub-level refresh as one consideration) and editorial-qa (pre-publish gate vs post-publish lifecycle). Audience: editorial leads running 50-5,000+ piece libraries.

  2. 02

    Refresh-everything vs refresh-nothing vs triaged-refresh

    The keystone framing. Calendar-driven refresh wastes capacity; set-and-forget decays the library; triaged refresh concentrates effort on signals. Litmus test: what signal triggered this refresh, what depth did the signal warrant, and how will we measure whether it worked?

  3. 03

    Refresh signals

    Five signal categories: traffic decay, ranking drops, factual staleness, SERP intent shift, content drift. Pieces with zero signals are stable; pieces with three or more are typically in active decay.

  4. 04

    The audit cadence

    Quarterly audit catches slow decay; continuous monitoring catches sharp decay. The hybrid pattern runs both. Threshold design and alert calibration discipline.

  5. 05

    Refresh prioritization

    2x2 matrix: value × traffic state. High-value-decaying first; low-value-decaying audited for merge/delete; high-value-stable monitored not refreshed; low-value-stable left alone. The discipline of NOT refreshing the stable quadrant.

  6. 06

    Refresh depth options

    Light edit (30-90 min), substantial revision (2-4 hours), full rewrite (8-16 hours), structural redesign (multi-week project). Match depth to signal strength. The depth-creep anti-pattern.

  7. 07

    Refresh vs merge vs delete decisions

    Three dispositions, not just refresh. Merge when authority is being split. Delete when there is no demand. The under-recognized failure of refreshing pieces that should have been merged or deleted.

  8. 08

    Refresh execution patterns

    Single owner per refresh, editorial-workflow integration scaled to depth, capacity allocation explicit, batching vs integration tradeoffs. The fast-track pattern for sharp decay.

  9. 09

    Re-promotion after refresh

    Schema markup, visible date, sitemap, Search Console resubmission, audience re-share. The refresh-that-nobody-told-anyone-about underperforms. Re-promotion intensity matches refresh depth.

  10. 10

    Refresh tracking and effectiveness

    Per-refresh log with signals, depth, capacity, predicted outcome, actual at 30 and 90 days. Pattern detection across refreshes. The refresh-that-did-not-work review surfaces the program's most valuable learning.

  11. 11

    Common failure modes

    11+ patterns: refresh-everything-on-calendar, set-and-forget, refresh that should have been merge or delete, unprioritized queue, refresh-on-stable-piece regression, capacity overcommitment, effectiveness invisible, light-edit-as-default.

  12. 12

    The framework: 12 considerations

    Triaged not calendar, signals named, audit cadence committed, prioritization matrix applied, depth matched to signal, disposition per piece, single ownership, capacity allocation, re-promotion, tracking, effectiveness, the-refresh-that-did-not-work review.

  13. 13

    Closing: refresh is content's immune system

    Set-and-forget treats the library as static and watches it decay. Refresh-everything burns capacity that should be producing new flagship work. The discipline is the immune system: invisible when working, catastrophic in its absence.

Reference files

Nine references that go alongside the SKILL.md.

The references hold signal detection, audit cadence, the prioritization matrix, depth decisions, refresh-vs-merge-vs- delete disposition, execution patterns, re-promotion discipline, effectiveness measurement, and the failure-mode catalog. Each closes with a methodology-vs-implementation section.

  • references/refresh-signals-checklist.md

    Five signal categories with detection patterns. Traffic decay, ranking drops, factual staleness, SERP intent shift, content drift. The library audit shape and cadence.

  • references/audit-cadence-patterns.md

    Quarterly audit mechanics; continuous monitoring mechanics; hybrid pattern; alert-threshold design; cadence variations by program shape; audit governance.

  • references/refresh-prioritization-matrix.md

    2x2 matrix with quadrant strategies. Per-quadrant capacity allocation. Common matrix failures. The dynamic-classification discipline.

  • references/refresh-depth-decision.md

    Four depth levels with work, time investment, use cases. Signal-to-depth matching framework. The depth-creep anti-pattern. Multi-depth refresh sequences.

  • references/refresh-vs-merge-vs-delete.md

    Three dispositions and their criteria. The disposition decision flow. The under-recognized failure of refreshing what should have been merged or deleted. Dispositions that need approval.

  • references/refresh-execution-patterns.md

    Single-owner discipline, editorial-workflow integration shapes by depth, capacity allocation patterns by library stage, batching vs integration vs hybrid tradeoffs, fast-track and stalled-refresh recovery patterns.

  • references/re-promotion-after-refresh.md

    Signal-to-search-engine patterns, substantive-vs-cosmetic distinction, audience re-promotion patterns, internal-link refresh discipline, URL-preservation default, re-promotion checklist by depth.

  • references/effectiveness-measurement.md

    Minimum per-refresh log fields, 30-day and 90-day measurement windows, pattern-detection cadence, the refresh-that-did-not-work review, metric-by-purpose mapping.

  • references/common-refresh-failures.md

    14+ failure patterns with diagnoses and cures. The cross-cutting pattern: shortcuts in discipline. Discipline-as-cure observation.

Browse all reference files on GitHub

Pairs with these platforms

Three platforms with refresh-relevant workflows.

The skill is platform-agnostic; the discipline applies regardless of where content is hosted. These platforms ship workflows that fit refresh programs: Frase (refresh-relevant content optimization with brand voice), AirOps (managed refresh workflows that compose AI generation with human review gates), BigQuery (traffic and ranking data warehouse for the analysis the audit depends on).

Bridges to other skills in the catalog

Six sister skills that compose with the refresh discipline.

The refresh discipline composes with strategy, hub architecture, the pre-publish gate, AI workflow, and the SEO audit and traffic-diagnosis skills. SEO content audit is the SEO-led equivalent of editorial-led refresh; the two compose where SEO and editorial perspectives both inform dispositions.

  • Program scope

    content-strategy

    Decides what to produce. Refresh capacity is part of the strategic allocation; programs maturing past production-only need refresh as a real budget line.

  • Hub scope

    pillar-content-architecture

    Hub-level refresh as ONE consideration in hub design. This skill provides the program-level prioritization, signals, and dispositions that apply across the library, hubs included.

  • Gate scope

    editorial-qa

    Pre-publish quality gate. This skill is post-publish lifecycle. Together they cover the full content lifecycle: editorial-qa catches problems before ship; this skill catches problems after ship.

  • Workflow scope

    ai-content-collaboration

    AI participation rules apply within refresh workflows. AI-assisted refreshes need voice discipline and per-derivative review just as new-piece AI work does.

  • SEO audit scope

    seo-content-audit

    Decides what to keep, update, merge, redirect, or delete from an SEO lens. This skill is the editorial-led refresh discipline; seo-content-audit is the SEO-led equivalent. The two compose.

  • Diagnostic scope

    seo-traffic-diagnosis

    Diagnoses why traffic moved. The diagnostic informs disposition: refresh, merge, or delete. Used together with this skill for traffic-decay refresh decisions.

Direction 7 Tier 2 content

The second of four Tier 2 content skills.

Content refresh system is the second of four Tier 2 content skills shipped together in Direction 7 Dispatch A. The other three: long-form-content-frameworks (long-form structural craft), content-repurposing (cross-format adaptation), and content-distribution (channel work).

Tier 2 extends Tier 1 (the foundational content suite of strategy, hub architecture, briefs, execution, programmatic, QA, and AI collaboration) into the disciplines that mature programs need: long-form structural craft, post-publish lifecycle, cross-format transformation, and channel-fit distribution.

The catalog now carries 81 skills. The content category spans 12 entries covering the full content workflow from strategy through distribution.

Open source under MIT

Read the SKILL.md on GitHub.

The skill source lives in the rampstackco/claude-skills repository alongside dozens of other skills covering the full lifecycle of brand and product work. MIT licensed.

View SKILL.mdBrowse the full catalog

Frequently asked questions.

What does 'triaged refresh' actually mean operationally?
Refresh on signal, not on calendar. Quarterly audits plus continuous monitoring detect signals (traffic decay, ranking drops, factual staleness, SERP intent shift, content drift). Pieces showing signals get prioritized via the value × traffic-state matrix: high-value-decaying first, low-value-decaying audited for merge or delete, stable quadrants left alone. Depth matches signal strength: light edit, substantial revision, full rewrite, or structural redesign. Each refresh is logged so the program learns. The discipline preserves capacity for high-value work and protects the library's compounding value.
How is this skill different from pillar-content-architecture's refresh treatment?
Pillar-content-architecture treats refresh as ONE consideration in hub design (the hub-level refresh that keeps a pillar plus cluster system current). This skill is the program-level refresh discipline across the WHOLE content library, not just within hubs. The two compose: hub-level refresh decisions follow from hub architecture; this skill provides the prioritization framework, signal taxonomy, audit cadence, and disposition decisions that apply across the library, hubs included.
How is this skill different from editorial-qa?
Editorial-qa is the pre-publish quality gate. This skill is the post-publish lifecycle. The two compose: editorial-qa catches problems before pieces ship; this skill catches problems after pieces are in the field and decaying. Both are quality disciplines at different moments; together they cover the whole content lifecycle.
When should I refresh vs merge vs delete a piece?
Refresh when the piece has demand and a path to recovery. Merge when authority is being split between two or more pieces competing for the same query (combine into a stronger consolidated piece; redirect the merged URLs). Delete when there is no demand, no merge candidate, and the topic is not load-bearing for the program (delete and 301 to the closest sibling). The under-recognized failure: refreshing pieces that should have been merged or deleted. Programs that adopt merge and delete as first-class dispositions typically recover 20-40% of refresh capacity.
How often should the audit run?
The hybrid pattern: quarterly audit plus continuous monitoring. The quarterly audit catches slow decay, content drift, and SERP intent shifts that need human review. Continuous monitoring catches sharp decay (40%+ traffic loss in 30 days) and algorithm-update fallout that quarterly cadence would miss for 75 days. Both running together cover the full range of decay signals.
What does 'capacity allocation' look like for refresh?
Newer libraries (under 100 pieces, under 2 years old): 5-15% of editorial capacity to refresh. Mid-stage libraries (100-500 pieces, 2-5 years old): 15-30%. Mature libraries (500+ pieces, 5+ years old): 25-40%. Without sustained refresh capacity, mature libraries erode. Without bounded capacity, refresh consumes new-production capacity. The right allocation matches library age and decay rates; quarterly review of actual vs planned capacity catches misallocation early.