seo-content-refresher

Identifies outdated elements in provided content and suggests updates to maintain freshness. Finds statistics, dates, and examples that need updating. Use PROACTIVELY for older content.

Quality

43%

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/seo-content-refresher/SKILL.md

Quality

Content

35%Scale 1-5

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

This skill reads more like a general SEO content freshness checklist than an actionable skill for Claude. It is heavy on categorized bullet lists but light on concrete, executable steps—there are no specific tools, commands, or worked examples showing how to actually perform the analysis. The content is also verbose, explaining concepts Claude already understands, and references a bundle file that doesn't exist.

Suggestions

Replace abstract steps like 'Scan content for dates' with concrete instructions: specify what tools or patterns to use (e.g., regex patterns for date detection, specific commands to check link validity).

Add a complete worked example showing an actual piece of content being analyzed, with specific findings and the resulting refresh plan—not just a template with placeholders.

Trim the extensive bullet-point lists (Deliverables, Refresh Tactics, Freshness Signals, Platform Implementation) into a referenced file or remove items Claude already knows, keeping only project-specific or non-obvious guidance.

Either provide the referenced `resources/implementation-playbook.md` bundle file or remove the reference, and add validation steps (e.g., 'verify updated statistics against source URLs before finalizing').

Dimension	Reasoning	Score
Conciseness	The content is noticeably verbose with several sections that explain concepts Claude already knows (what freshness signals are, what content decay means, generic SEO concepts). The 'Use this skill when' and 'Do not use this skill when' sections are tautological. Multiple bullet-point lists repeat similar ideas without adding actionable value.	2 / 5
Actionability	The skill provides high-level checklists and categories but lacks concrete, executable guidance. There are no specific commands, code snippets, or tool invocations—just abstract lists like 'Scan content for dates' and 'Identify statistics and data points' without explaining how. The output template is a generic placeholder rather than a worked example.	2 / 5
Workflow Clarity	The 'Approach' section provides a numbered sequence of steps, and the priority matrix adds some structure. However, there are no validation checkpoints, no feedback loops for verifying that updates are correct or complete, and no clear decision criteria for moving between steps. For a skill involving batch content updates, the lack of verification caps this at 3.	3 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed examples, which is good progressive disclosure. However, no bundle files exist to support this reference, and a large amount of content (deliverables, tactics, freshness signals, platform implementation) is inlined when it could be split into referenced files. The structure has sections but they feel like a flat dump rather than a well-organized hierarchy.	3 / 5
	Total	10 / 20 Passed

Description

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

The description communicates its core purpose — identifying outdated content elements — but lacks natural trigger terms users would actually use and has a somewhat vague 'when' clause. It would benefit from more specific trigger phrases and clearer differentiation from general content editing or review skills.

Suggestions

Add natural trigger terms users would say, such as 'refresh content', 'update old article', 'stale information', 'check for outdated references', or 'content audit'.

Make the 'when' clause more explicit with concrete scenarios, e.g., 'Use when the user asks to review, refresh, or audit existing content for outdated statistics, references, or examples'.

Add distinguishing details about what makes this different from general content editing, such as specifying it focuses on factual accuracy and temporal relevance rather than style or grammar.

Dimension	Reasoning	Score
Specificity	Names the domain (content freshness) and lists a few concrete actions: 'identifies outdated elements', 'suggests updates', 'finds statistics, dates, and examples'. However, it doesn't elaborate on what kinds of updates or outputs are produced, leaving coverage somewhat thin.	3 / 5
Completeness	The 'what' is reasonably clear (identifies outdated elements, finds statistics/dates/examples needing updates). The 'when' is present ('Use PROACTIVELY for older content') but is vague — 'older content' is not a concrete trigger phrase, and it doesn't specify user-facing trigger scenarios like 'when the user asks to review or refresh existing content'.	4 / 5
Trigger Term Quality	Includes some relevant terms like 'outdated', 'statistics', 'dates', 'examples', and 'freshness', but misses natural user phrases like 'update content', 'stale information', 'refresh article', 'old data', or 'review for accuracy'. The terms present are more descriptive than what users would naturally say.	2 / 5
Distinctiveness Conflict Risk	The focus on content freshness and outdated elements is somewhat specific, but 'content' is broad and could overlap with general content editing, content review, or content analysis skills. The description doesn't carve out a sufficiently distinct niche.	3 / 5
	Total	12 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/seo-content-refresher/SKILL.md
Commit: 57c135b

Reviewed: 23 hours 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.