refresh-vs-new-content
Skill7 starsChanged 5 months agoMITView on GitHub
Decide whether to update, consolidate, prune, or create new content for a given page or topic. Use when Codex needs to recommend the best content action based on performance data and competitive analysis.
In this repository22 other files it gives its agents.
- authority-mark-keyword-difficultySkill
- cannibalization-checkSkill
- client-report-writerSkill
- competitor-serp-monitorSkill
- content-decay-monitor-setupSkill
- content-moat-plannerSkill
- content-refresh-briefSkill
- exceed-quality-thresholdSkill
- internal-link-builderSkill
- keyword-opportunity-finderSkill
- keyword-plannerSkill
- live-search-console-dataSkill
- proposal-builderSkill
- schema-fix-writerSkill
- seo-content-briefSkill
- seo-growth-loopSkill
- seo-offer-architectSkill
- seo-priority-scoreSkill
- seo-strategySkill
- technical-seo-triageSkill
- title-meta-rewriterSkill
- traffic-decay-detectorSkill
The file
Files
Refresh vs New Content
Overview
Given a page and its performance data, decide the best content action: refresh (update existing), consolidate (merge pages), prune (remove or redirect), or create new. Uses traffic trends, SERP competitiveness, content quality, and business value.
Inputs
- Page URL and current performance data (GSC/GA4)
- Content quality assessment (depth, freshness, accuracy)
- SERP competitive analysis for the page's primary query
- Business value of the topic
Workflow
- Assess the page's current content quality:
- Outdated information or examples
- Thin content compared to top SERP results
- Missing entities or sections
- Poor user engagement signals (bounce rate, time on page)
- Assess traffic potential:
- Total search demand for the primary query
- Authority feasibility (can this site rank?)
- Seasonality or trend direction
- Decision matrix:
- Refresh: page has good bones, query is stable or growing, authority exists
- Consolidate: page is thin, overlaps with another stronger page on the site
- Prune: query demand declining, page has no unique value, better to redirect authority
- Create new: new query opportunity, site has no existing coverage, authority is feasible
- For refresh: pass to content-refresh-brief for the detailed brief.
- For create new: pass to seo-content-brief.
- For consolidate/prune: recommend the target URL or redirect destination.
Output
Content action recommendation with rationale, expected impact, and handoff to the relevant skill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

