Agent skill · Content & Marketing

blog-decay

Detect content decay from Google Search Console exports by comparing current and previous page performance, flagging quarter-over-quarter traffic drops, dropped pages, and refresh, consolidate, prune, or query-shift actions. Use when the user says "/blog decay", "content decay", "traffic drop", "QoQ decline", "GSC decay", or "refresh declining posts".

AgriciDanielgithub.com/AgriciDanielGitHub ↗
claude-codeMIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-decay --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/blog-decay/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,566
Language: Python

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

From the SKILL.md

# Blog Decay Use `/blog decay` to find pages whose Google Search Console performance has declined quarter-over-quarter. The command compares a current-period export against a previous-period export, flags pages with a 20% or larger decline by default, and recommends the next content action. ## Default Offline Workflow Run the local analyzer against two GSC page exports: ```bash python3 scripts/content_decay.py current.json previous.json ``` Useful options: ```bash python3 scripts/content_decay.py current.json previous.json --threshold 0.30 python3 scripts/content_decay.py current.json previous.json --metric impressions python3 scripts/content_decay.py current.json previous.json --format markdown --output decay-report.md ``` The script accepts JSON lists of page rows with `page` or `url`, `clicks`, and `impressions`. It also accepts the object shape returned by `blog-google` when the rows are under a top-level `rows` key. ## Optional Live GSC Export For live data, use `/blog google gsc` or the underlying `blog-google` command to create each period export, then run the offline analyzer: ```bash python3 skills/blog-google/scripts/run.py gsc_query --property sc-domain:example.com --dim

What's inside
Steps it walks through
  1. Default Offline Workflow
  2. Optional Live GSC Export
  3. Decay Model
  4. Recommended Actions
  5. Cross-references
Commands it runs
python3 scripts/content_decay.py current.json previous.json
python3 scripts/content_decay.py current.json previous.json --threshold 0.30
python3 scripts/content_decay.py current.json previous.json --metric impressions
python3 scripts/content_decay.py current.json previous.json --format markdown --output decay-report.md
python3 scripts/content_decay.py gsc-current.json gsc-previous.json --format markdown
More from claude-blog
All skills →
About this skill
What does the blog-decay skill do?

Detect content decay from Google Search Console exports by comparing current and previous page performance, flagging quarter-over-quarter traffic drops, dropped pages, and refresh, consolidate, prune, or query-shift actions. Use when the user says "/blog decay", "content decay", "traffic drop", "QoQ decline", "GSC decay", or "refresh declining posts".

How do I install it?

Run `npx skills add AgriciDaniel/claude-blog --skill blog-decay --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 AgriciDaniel/claude-blog, a repository with 1,566 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