Name: seo-content-refresher
Rating: 58.4 (1 reviews)
Author: administrakt0r

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

67%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/seo-content-refresher/SKILL.md

The canonical home for this skill is seo-content-refresher in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

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

The body is a well-structured, actionable content-refresh guide with a concrete output template, but it carries generic boilerplate and overlapping lists that dilute conciseness, and its single external reference points to a non-existent file. Workflow clarity is solid for a non-destructive suggestion skill.

Suggestions

Remove the tautological "Use this skill when" / "Do not use" boilerplate and the abstract Instructions bullets, or replace them with skill-specific triggers to tighten conciseness.

Create the referenced `resources/implementation-playbook.md` (or point the reference at a real file) so progressive disclosure is not broken by a dangling link.

Consolidate the overlapping Focus Areas, Refresh Tactics, and Freshness Signals lists, or move the bulk detail into the referenced playbook to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Content is mostly list-based and free of concept-explaining padding, but generic boilerplate ("Working on seo content refresher tasks or workflows", the abstract Instructions bullets) and overlapping lists (Focus Areas vs. Refresh Tactics vs. Freshness Signals) could be tightened. Not a 4 because several sections are removable redundancy rather than minor trims.	3 / 5
Actionability	Concrete guidance throughout — numeric update priorities ("Statistics older than 2 years", "Examples from 3+ years ago"), a High/Medium priority matrix, a 7-step Approach, and a copy-paste Content Refresh Plan template. Not a 5 because it offers no tooling or method for actually locating outdated statistics.	4 / 5
Workflow Clarity	The Approach gives a clear 7-step sequence (Scan → Identify statistics → Find examples → Check terminology → Assess completeness → Suggest priorities → Recommend sections), and the Output template plus Deliverables act as implicit checkpoints. Not a 5 because there are no explicit validation steps; not capped at 3 because this is a non-destructive suggestion skill rather than a batch/destructive operation.	4 / 5
Progressive Disclosure	Good sectioning with clear headers (Focus Areas, Guidelines, Priority Matrix, Approach, Output) and one clearly-signaled one-level-deep reference ("open `resources/implementation-playbook.md`"). Not a 5 because that referenced file does not exist in the bundle and detail lists (Refresh Tactics, Freshness Signals, Platform Implementation) are inlined rather than split out.	4 / 5
	Total	15 / 20 Passed

Description

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

The description clearly conveys both capability and usage timing with concrete actions, but its trigger-term coverage is incomplete — it omits the most natural user synonyms (refresh, update, SEO) that the skill name itself implies. Distinctiveness is good for the content-freshness niche.

Suggestions

Add natural trigger terms users actually say — e.g., "refresh", "update", "outdated blog post", "SEO content" — to broaden trigger-term coverage beyond "older content".

Strengthen the when clause with concrete triggers, e.g., "Use when refreshing dated blog posts, updating old statistics, or reviving declining content."

Mirror the body's fuller action list (e.g., update meta titles, fix expired links) to lift specificity from 4 to 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Identifies outdated elements", "suggests updates to maintain freshness", "Finds statistics, dates, and examples that need updating" — with only minor coverage gaps (e.g., link-checking, meta updates). Not a 5 because the actions stop short of the comprehensive set the body later enumerates.	4 / 5
Completeness	Clearly states what (identifies outdated elements, suggests updates, finds stats/dates/examples) and when ("Use PROACTIVELY for older content"). Not a 5 because the when clause is thin and lacks concrete trigger phrases; not a 3 because both halves are explicitly present.	4 / 5
Trigger Term Quality	Relevant keywords appear ("outdated elements", "statistics, dates, and examples", "older content", "freshness") but core natural synonyms a user would say — "refresh", "update", "SEO", "blog post/article" — are absent. Not a 4 because more than a few natural terms are missing.	3 / 5
Distinctiveness Conflict Risk	The content-freshness niche ("outdated elements", "maintain freshness", "older content") is mostly distinct with only minor overlap risk against general editing skills. Not a 5 because "older content" is a somewhat broad trigger.	4 / 5
	Total	15 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/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.