Google SEO APIs
AgriciDaniel/claude-seo
Pulls real Google data for SEO work: Search Console, PageSpeed Insights, CrUX field data, the Indexing API and GA4 organic traffic, through /seo google commands.
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…
Install Blog Decay
$ npx skills add AgriciDaniel/claude-blog --skill blog-decay -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-decay --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/blog-decay .claude/skills/blog-decay && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "blog-decay" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-decay into .claude/skills/blog-decay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-decay", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-decayType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add AgriciDaniel/claude-blog --skill blog-decay -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-decay --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/blog-decay .agents/skills/blog-decay && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "blog-decay" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-decay into .agents/skills/blog-decay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-decay", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AgriciDaniel/claude-blog --skill blog-decay -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-decay --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/blog-decay .cursor/skills/blog-decay && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "blog-decay" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-decay into .cursor/skills/blog-decay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-decay", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/AgriciDaniel/claude-blog.git --path skills/blog-decay--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AgriciDaniel/claude-blog --skill blog-decay -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-decay --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/blog-decay .gemini/skills/blog-decay && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "blog-decay" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-decay into .gemini/skills/blog-decay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-decay", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install AgriciDaniel/claude-blog blog-decayInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add AgriciDaniel/claude-blog --skill blog-decay -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/blog-decay .github/skills/blog-decay && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "blog-decay" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-decay into .github/skills/blog-decay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-decay", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AgriciDaniel/claude-blog --skill blog-decay -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-decay --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/blog-decay .opencode/skills/blog-decay && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "blog-decay" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/skills/blog-decay into .opencode/skills/blog-decay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-decay", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
blog-decay- GitHub stars
- 2.3k
- Token cost
- ~959 tokens
- SKILL.md length
- 358 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- The user says /blog decay
- SKILL.md covers Default Offline Workflow, Optional Live GSC Export, Decay Model and Recommended Actions, plus 1 more section
- Calls python3
- Refresh declining posts
What it does
Blog Decay is an agent skill from AgriciDaniel/claude-blog. 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".
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO. It works with Google Search Console. The repository describes itself as: Claude Code blog skill suite: 30 sub-skills, 5 agents, 5-gate v1.9.0 Blog Delivery Contract, dual-optimized for Google rankings and AI citations. Active development at… The licence is MIT.
When your agent uses it
- The user says /blog decay
- Refresh declining posts
Example prompts
- “/blog decay”
- “content decay”
- “traffic drop”
- “/blog-decay”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 2500d4c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Blog Decay loads about 959 tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 358 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from AgriciDaniel/claude-blog at commit 2500d4c, republished under its MIT licence (© AgriciDaniel). 358 words, ~959 tokens.
Download SKILL.mdSave it as
.claude/skills/blog-decay/SKILL.md (or your agent's skills folder).- name
- blog-decay
- description
- 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".
- argument-hint
- <current-gsc.json> <previous-gsc.json> [threshold] [metric]
- user-invokable
- true
- license
- MIT
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:
python3 scripts/content_decay.py current.json previous.jsonUseful options:
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.mdThe 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:
python3 skills/blog-google/scripts/run.py gsc_query --property sc-domain:example.com --dimensions page --start-date YYYY-MM-DD --end-date YYYY-MM-DD --json > gsc-current.json
python3 skills/blog-google/scripts/run.py gsc_query --property sc-domain:example.com --dimensions page --start-date YYYY-MM-DD --end-date YYYY-MM-DD --json > gsc-previous.json
python3 scripts/content_decay.py gsc-current.json gsc-previous.json --format markdownUse adjacent periods of similar length for short-term checks. For seasonality, also run a year-over-year comparison using the same date length, filters, search type, device, country, and property. When possible, inspect up to 16 months of GSC history before diagnosing a traffic drop.
Decay Model
The default metric is clicks. Also review impressions, CTR, average position,
query and page pairs, device, country, and search appearance deltas before
choosing an action.
Severity:
| Decline | Severity |
|---|---|
| 20% to 39.9% | warning |
| 40% to 59.9% | high |
| 60% or more | critical |
Dropped pages are previous-period pages missing from the current export only
after confirming identical filters, sufficient row limits, matching dimensions,
and URL inspection. Otherwise mark them as needs_validation, not
dropped_out.
Show full SKILL.md (128 more words)Show less
Recommended Actions
Use the action as the first triage path only after checking indexation, canonical status, query loss, internal links, backlinks, seasonality, and business value:
| Action | Use when |
|---|---|
| refresh/update content | The page still has demand and likely needs freshness, title, internal link, or section updates. |
| investigate query shift | Clicks fell while impressions held up, suggesting CTR, rank, SERP, or query mix changes. |
| consolidate/redirect | The page dropped out or the loss is severe enough that merging into a stronger URL may recover value faster. |
| prune | The page had very low prior demand and may not justify rewrite effort. |
Cross-references
Use blog-google to collect Search Console exports when live credentials are
available. Use blog-rewrite after decay detection when the recommended action
is refresh/update content and the page is worth improving.
© AgriciDaniel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/blog-decay of AgriciDaniel/claude-blog.
Open the folder on GitHubat commit 2500d4c
Compare with similar skills
Blog Decay next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Blog Decay this skillAgriciDaniel/claude-blog | 2.3k | — | ~959 | Automated safety check: Pass | MIT | |
| Google SEO APIsAgriciDaniel/claude-seo | 19k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| SEO GodAKCodez/seo-god | 113 | — | ~2.2k | Automated safety check: Pass | MIT | |
| SEO Coachakseolabs-seo/seo-coach | 146 | — | ~2.8k | Automated safety check: Pass | None | |
| SEO Setupalisamadiii/Portfolio | 180 | — | ~1.7k | Automated safety check: Pass | None | |
| SEO Coachpetera2c/simple-table | 229 | 2 repos | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
SEO God
AKCodez/seo-god
Agentic SEO operator for your own website: audits and fixes your site with OpenSEO, measures rankings + Google Search Console, works to get ChatGPT and other AI engines citing you, and schedules the…
SEO Coach
akseolabs-seo/seo-coach
Beginner-first SEO coaching for people who want to learn by doing one safe, verifiable step at a time.
SEO Setup
alisamadiii/Portfolio
Full SEO/metadata setup and audit for client websites (Astro, Next.js, any static site).
SEO Coach
petera2c/simple-table
Enter a friendly OpenSEO coach mode that explains workflows, recommends next steps, and helps users use agents, web search, scraping, and MCP data effectively.
Google Search Console
superdesigndev/treg
Traps to avoid when querying Google Search Console through treg — cases where the API returns a confident wrong answer instead of an error, especially around totals and recent-date trends.
More from AgriciDaniel/claude-blog
All 39 skills in this repoBlog Google
AgriciDaniel/claude-blog
Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity…
Blog Audio
AgriciDaniel/claude-blog
Generate audio narration of blog posts using Google Gemini TTS.
Blog Flow
AgriciDaniel/claude-blog
FLOW framework integration for bloggers. An agent skill from AgriciDaniel/claude-blog.
Blog Notebooklm
AgriciDaniel/claude-blog
Query Google NotebookLM notebooks for source-grounded, citation-backed answers from user-uploaded documents.
Blog Image
AgriciDaniel/claude-blog
AI image generation and editing for blog content powered by Gemini via MCP.
Blog Cluster
AgriciDaniel/claude-blog
Semantic topic cluster planning and automated execution engine for claude-blog.
Related
Works with
Categories
Questions about Blog Decay
What does Blog Decay 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…. Blog Decay is an agent skill from AgriciDaniel/claude-blog. 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.
When should I use Blog Decay?
Blog Decay fits situations like: the user says /blog decay; refresh declining posts.
How do I install Blog Decay in Claude Code?
Run `npx skills add AgriciDaniel/claude-blog --skill blog-decay -a claude-code`. Or copy the skill folder (skills/blog-decay in AgriciDaniel/claude-blog) into .claude/skills/blog-decay in your project. Claude Code loads it when a task matches its description.
How do I install Blog Decay in Codex?
Run `npx skills add AgriciDaniel/claude-blog --skill blog-decay -a codex`. Or copy the skill folder (skills/blog-decay in AgriciDaniel/claude-blog) into .agents/skills/blog-decay in your project. Codex loads it when a task matches its description.
Can I use Blog Decay in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgriciDaniel/claude-blog --skill blog-decay -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blog-decay, .gemini/skills/blog-decay, .github/skills/blog-decay and .opencode/skills/blog-decay in your project.
What does Blog Decay need to run?
Going by SKILL.md and its folder, Blog Decay needs the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Blog Decay access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Blog Decay safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Blog Decay use?
Blog Decay is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Blog Decay use?
About 959 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Blog Decay?
Skills that share tags, products or a category with Blog Decay: Google SEO APIs (AgriciDaniel/claude-seo, 19k stars), SEO God (AKCodez/seo-god, 113 stars), SEO Coach (akseolabs-seo/seo-coach, 146 stars) and SEO Setup (alisamadiii/Portfolio, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Blog Decay?
AgriciDaniel (a GitHub user) maintains it in AgriciDaniel/claude-blog, which has 2,348 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 9, 2026.
Source: AgriciDaniel/claude-blog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.