content-decay-detector
Skill757 starsChanged 8 months agoMITView on GitHub
Monitor existing content for ranking drops and trigger refresh workflows. Triggers on: "check for content decay", "which content needs updating", "content refresh", "ranking drops", "traffic decline", "stale content", "content audit", "what to refresh", "outdated content", "content performance check", "update old articles", "declining rankings", "content maintenance", "refresh priority list", "which articles are losing traffic", "SEO content audit".
In this repository55 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- affiliate-checkSkill
- ab-test-generatorSkill
- conversion-trackerSkill
- internal-linking-optimizerSkill
- performance-reportSkill
- seo-auditSkill
- content-repurposerSkill
- email-automation-builderSkill
- multi-program-managerSkill
- paid-ad-copy-writerSkill
- proprietary-data-generatorSkill
- affiliate-blog-builderSkill
- comparison-post-writerSkill
- content-moat-calculatorSkill
- how-to-tutorial-writerSkill
- keyword-cluster-architectSkill
- listicle-generatorSkill
- content-pillar-atomizerSkill
- content-research-briefSkill
- infographic-generatorSkill
- reddit-post-writerSkill
- tiktok-script-writerSkill
- twitter-thread-writerSkill
- viral-post-writerSkill
- bio-link-deployerSkill
- email-drip-sequenceSkill
- github-pages-deployerSkill
- social-media-schedulerSkill
- bonus-stack-builderSkill
- grand-slam-offerSkill
- guarantee-generatorSkill
- landing-page-creatorSkill
- product-showcase-pageSkill
- squeeze-page-builderSkill
- value-ladder-architectSkill
- webinar-registration-pageSkill
- category-designerSkill
- compliance-checkerSkill
- create-skillSkill
- funnel-plannerSkill
- self-improverSkill
- skill-finderSkill
- affiliate-program-searchSkill
- commission-calculatorSkill
- competitor-spySkill
- content-angle-rankerSkill
- find-and-verify-affiliate-programSkill
- monopoly-niche-finderSkill
- niche-opportunity-finderSkill
- purple-cow-auditSkill
- submit-programSkill
- traffic-analyzerSkill
- trending-content-scoutSkill
- your-skill-nameSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
After seo-audit reveals declining pages
- Very specific: line 57
Chaining from S6 seo-audit: Use declining_pages as the content_list.
- Very specific: line 63
If content_list not provided:
- Very specific: line 70
Read shared/references/seo-strategy.md for decay signals and refresh methodology.
- Distinctive: line 74
Look for decay signals:
- Distinctive: line 77
Missing elements: No images, no data, thin content compared to current SERP
- Distinctive: line 185
Can't determine ranking positions: Use available signals (content age, competitor freshness, outdated info) for prioritization.
- Very specific: line 211
After refreshing, seo-audit (S6) tracks whether rankings recovered → measure refresh ROI, refine decay detection sensitivity
- Distinctive: line 215
Before delivering output, verify:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content Decay Detector
Monitor existing content for ranking drops and generate a prioritized refresh queue. Refreshing decaying content is the highest-ROI SEO activity — it's faster and cheaper than creating new content, and recovering a lost position is easier than earning a new one.
Stage
S3: Blog & SEO — Blog maintenance and optimization. This skill keeps your existing content competitive and prevents rankings from silently eroding.
When to Use
- User has existing blog content and wants to check for decay
- User notices traffic declining on specific pages
- User asks "what content needs updating?"
- User says "content decay", "ranking drops", "stale content", "refresh", "content audit"
- Monthly maintenance check — should run every 30 days on active blogs
- After
seo-auditreveals declining pages
Input Schema
site_url: string # REQUIRED — the site to audit
# e.g., "myblog.com", "example.com/blog"
content_list: object[] # OPTIONAL — specific pages to check
- url: string # Page URL
title: string # Page title
publish_date: string # Original publish date
last_updated: string # Last update date
target_keyword: string # Primary keyword
check_competitors: boolean # OPTIONAL — whether to check if competitors published fresher content
# Default: true
timeframe: string # OPTIONAL — "30d" | "90d" | "6m" | "1y"
# Default: "90d"Chaining from S6 seo-audit: Use declining_pages as the content_list.
Workflow
Step 1: Gather Content Data
If content_list not provided:
web_search:site:[site_url]— discover indexed pages- Identify the top 15-20 most important pages (by topic relevance)
- For each page, note: title, URL, apparent publish/update date
Step 2: Check for Decay Signals
Read shared/references/seo-strategy.md for decay signals and refresh methodology.
For each page:
web_searchfor the page's target keyword — check current ranking position- Look for decay signals:
- Outdated information: Product features, pricing, dates mentioned
- Competitor freshness: Newer, better content published by competitors
- Missing elements: No images, no data, thin content compared to current SERP
- Broken patterns: "2023" in a title when it's 2025+, discontinued products mentioned
Step 3: Score Decay Priority
For each decaying page, assign priority:
| Factor | Score | Criteria |
| Revenue impact | 1-5 | Contains affiliate links + had traffic = high revenue impact |
| Decay severity | 1-5 | Major outdated info = 5, minor = 1 |
| Fix effort | 1-5 (inverted) | Easy fix = 5, full rewrite = 1 |
| Competitor threat | 1-5 | Competitor published better version = 5 |
Priority = Revenue × Decay × Fix_Ease × Competitor_Threat (normalized)
Step 4: Generate Refresh Instructions
For each page in priority order, specify:
- What's decayed — specific outdated elements
- What to update — concrete changes to make
- What to add — new sections, data, or elements competitors have
- Internal linking — new pages to link to/from since original publish
- Estimated effort — time to refresh
Step 5: Self-Validation
- Decay signals are evidence-based (not guesses)
- Priority ordering makes business sense (revenue-impacting first)
- Refresh instructions are specific and actionable
- Effort estimates are realistic
- Not recommending refreshes for content that's performing fine
Output Schema
output_schema_version: "1.0.0"
content_decay:
site: string
pages_analyzed: number
pages_decaying: number
total_refresh_effort: string # Estimated total hours
decaying_pages:
- url: string
title: string
priority: string # "P0-critical" | "P1-high" | "P2-medium" | "P3-low"
decay_signals: string[]
refresh_actions: string[]
estimated_effort: string
revenue_impact: string # "high" | "medium" | "low"
healthy_pages: string[] # Pages that don't need refresh
chain_metadata:
skill_slug: "content-decay-detector"
stage: "blog"
timestamp: string
suggested_next:
- "affiliate-blog-builder"
- "seo-audit"
- "internal-linking-optimizer"
- "keyword-cluster-architect"Output Format
## Content Decay Report: [Site]
### Summary
- **Pages analyzed:** XX
- **Pages decaying:** XX
- **Total refresh effort:** XX hours
- **Estimated traffic recovery:** XX%
### Priority Refresh Queue
#### P0 — Critical (do this week)
**[Page Title]** — [URL]
- Decay: [what's wrong]
- Action: [what to do]
- Effort: [time estimate]
- Impact: [expected result]
#### P1 — High (do this month)
[same structure]
#### P2 — Medium (schedule)
[same structure]
### Healthy Pages (no action needed)
- [Page] — still ranking, content fresh
- [Page] — recently updated
### Monthly Maintenance Schedule
- Week 1: Refresh P0 pages
- Week 2: Refresh P1 pages
- Week 3: Create new content for gaps found
- Week 4: Internal linking reviewError Handling
- No site URL: "I need your blog URL to check for content decay. What's the site?"
- Site has no indexed pages: "I can't find indexed pages for this URL. Check that the site is public and indexed by search engines."
- All content is fresh: "Great news — no significant decay detected. Run this check again in 30 days."
- Can't determine ranking positions: Use available signals (content age, competitor freshness, outdated info) for prioritization.
Examples
Example 1: "Check my blog for content decay" → Discover indexed pages, check each for decay signals, generate prioritized refresh queue with specific actions per page.
Example 2: "Which of my articles need updating?" → Analyze content list, identify outdated pricing, stale comparisons, missing new products. Rank by revenue impact.
Example 3: "Content decay check" (after seo-audit) → Pick up declining pages from seo-audit output. Deep-dive each with competitor analysis and specific refresh instructions.
Flywheel Connections
Feeds Into
affiliate-blog-builder(S3) — refresh instructions for specific articlesinternal-linking-optimizer(S6) — decaying pages may need better internal linkskeyword-cluster-architect(S3) — content gaps revealed by decay analysis
Fed By
seo-audit(S6) — declining pages to investigateinternal-linking-optimizer(S6) — pages with weak link structure may be decayingperformance-report(S6) — traffic decline data
Feedback Loop
- After refreshing,
seo-audit(S6) tracks whether rankings recovered → measure refresh ROI, refine decay detection sensitivity
Quality Gate
Before delivering output, verify:
- Would I share this on MY personal social?
- Contains specific, surprising detail? (not generic)
- Respects reader's intelligence?
- Remarkable enough to share? (Purple Cow test)
- Irresistible offer framing? (refresh actions feel actionable)
Any NO → rewrite before delivering.
References
shared/references/seo-strategy.md— Decay signals, refresh methodology, priority matrixshared/references/flywheel-connections.md— Master connection map
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.

