content-refresh-system

Systematic content refresh discipline. Quarterly audits, refresh prioritization (which pieces, when, how deep), refresh-vs-merge-vs-delete decisions, the lifecycle that distinguishes intentional refresh from set-and-forget decay. Builds on the refresh sections of pillar-content-architecture and editorial-qa with a program-level discipline. Triggers on content refresh, content decay, content audit, refresh prioritization, content lifecycle, refresh strategy, traffic decay, ranking drop, content freshness, evergreen content, content maintenance. Also triggers when traffic is eroding silently across an aging content library, when teams cannot decide which pieces to refresh, or when refresh work is happening but the impact is unclear.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/content-refresh-system/SKILL.md

Quality

Content

63%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.

Well-structured and actionable with excellent progressive disclosure, but the body is padded with editorial prose and persuasive framing that inflates the token cost without adding operational value. Tightening the narrative passages would materially improve conciseness.

Suggestions

Trim the editorial framing passages (e.g., 'The voice is the senior editorial leader...', the opening 'Content decays...' paragraph) to lean operational prose; keep concrete actions and drop the persuasion.

Add an explicit validation checkpoint before destructive dispositions — e.g., confirm redirect target resolves and the piece has no residual value before executing delete/merge.

Collapse the repeated per-section 'Detail in [...]' lines into the existing Reference files section to reduce redundancy, since each section already names its reference inline.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose — extended editorial exposition ('Content decays. Search behavior shifts; SERP intent reshapes; facts go stale...') and framing ('The voice is the senior editorial leader who has watched refresh programs fail...') pad a body that could be tightened substantially without losing substance.	2 / 5
Actionability	Concrete specifics throughout — time investments per depth (30-90 min, 2-4 hours), the 2x2 prioritization matrix quadrants, and explicit disposition criteria — give mostly executable guidance with only minor gaps.	4 / 5
Workflow Clarity	The 12-consideration framework sequences the program and the per-refresh tracking plus 'refresh-that-did-not-work review' provide feedback loops, though destructive dispositions (delete, 301 redirect) lack an explicit pre-ship validation gate.	4 / 5
Progressive Disclosure	A clean overview body with well-signaled one-level-deep references — nine 'Detail in [`references/...`](...)' pointers, all to verified real files — plus a Reference files section summarizing each.	5 / 5
	Total	15 / 20 Passed

Description

95%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, specific description that names concrete actions, comprehensive trigger terms, and a clear what/when structure with explicit sibling-skill boundaries. The only minor gap is specificity falling just short of exhaustive action enumeration.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Quarterly audits, refresh prioritization (which pieces, when, how deep), refresh-vs-merge-vs-delete decisions' — but stops short of the fully comprehensive coverage of a 5.	4 / 5
Completeness	Explicitly answers both what ('Systematic content refresh discipline...') and when ('Triggers on...', 'Also triggers when...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage including synonyms — 'content refresh, content decay, content audit, refresh prioritization, content lifecycle, refresh strategy, traffic decay, ranking drop, content freshness, evergreen content, content maintenance' — plus situational 'when traffic is eroding silently' phrasing.	5 / 5
Distinctiveness Conflict Risk	Carves a clear lifecycle niche and explicitly distinguishes it from sibling skills — 'Builds on the refresh sections of pillar-content-architecture and editorial-qa' — minimizing trigger conflict.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Path: skills/content-refresh-system/SKILL.md
Commit: a67dd34

Reviewed: 14 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.