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

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable body with concrete commands, severity/action tables, and validation logic for the batch analysis. Main gaps are the referenced script not being present in the bundle and minor tightening opportunities.

Suggestions

Ship the referenced `scripts/content_decay.py` (and document the `skills/blog-google/scripts/run.py` path) so the copy-paste commands are actually executable from the bundle.

Trim the intro paragraph that restates the frontmatter description to reduce token redundancy.

Add an explicit validation step in the offline workflow (e.g., verify both exports share identical filters/dimensions before trusting the diff) to push workflow clarity to 5.

Dimension	Reasoning	Score
Conciseness	The body is efficient and largely assumes Claude's competence, but the intro mildly restates the description and a few sentences could be tightened; minor instances of over-explanation rather than padding.	4 / 5
Actionability	Provides concrete, copy-pasteable commands with flags (`python3 scripts/content_decay.py current.json previous.json --threshold 0.30`) and the accepted JSON shapes, but the referenced `content_decay.py` script is not present in the bundle, leaving a minor executability gap.	4 / 5
Workflow Clarity	Clear offline-then-optional-live sequence with validation checkpoints (dropped-page confirmation requirements, action-triage checklist after checking indexation/canonical/query loss), satisfying the batch-operation feedback requirement; minor gaps keep it below 5.	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections (Default Offline Workflow, Optional Live GSC Export, Decay Model, Recommended Actions, Cross-references) with one-level-deep cross-references, but the skill is over 50 lines and the referenced script files are not actually shipped in a bundle.	4 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely states capabilities and provides explicit, natural trigger phrases. It clearly answers both what the skill does and when to use it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'comparing current and previous page performance', 'flagging quarter-over-quarter traffic drops, dropped pages', and 'refresh, consolidate, prune, or query-shift actions' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (detect GSC content decay via period comparison and action flagging) and 'when' (concrete trigger phrases), matching the score-5 anchor.	5 / 5
Trigger Term Quality	The 'Use when the user says' clause enumerates natural trigger phrases users would actually say — '/blog decay', 'content decay', 'traffic drop', 'QoQ decline', 'GSC decay', 'refresh declining posts'.	5 / 5
Distinctiveness Conflict Risk	The GSC quarter-over-quarter content-decay niche is specific with distinct command-style triggers, minimizing overlap with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	14 / 16 Passed

Repository: AgriciDaniel/claude-blog
Path: brain/.raw/sources/claude-blog-skill/skills/blog-decay/SKILL.md
Commit: 84f7abf

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.