Agent skill · Security

content-decay-detector

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".

Affitorgithub.com/AffitorGitHub ↗
claude-codecursorMIT
Install
npx skills add Affitor/affiliate-skills --skill content-decay-detector --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Version: 1.0.0
Declared author: affitor
Requires: Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent
Path: skills/blog/content-decay-detector/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 586
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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-audit` reveals declining pages ## Input Schema ```yaml 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 #

What's inside
Steps it walks through
  1. Stage
  2. When to Use
  3. Input Schema
  4. Workflow
  5. Step 1: Gather Content Data
  6. Step 2: Check for Decay Signals
  7. Step 3: Score Decay Priority
  8. Step 4: Generate Refresh Instructions
  9. Step 5: Self-Validation
  10. Output Schema
  11. Output Format
  12. Error Handling
  13. Examples
  14. Flywheel Connections
More from affiliate-skills
All skills →
About this skill
What does the content-decay-detector skill do?

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".

How do I install it?

Run `npx skills add Affitor/affiliate-skills --skill content-decay-detector --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Affitor/affiliate-skills, a repository with 586 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going