CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-content-refresher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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-organized instruction-only skill with some concrete thresholds and a useful output template, but it is padded with tautological use/do-not-use boilerplate and generic filler bullets, its workflow lacks any validation or verification checkpoints, and it dangles a reference to a nonexistent resources/implementation-playbook.md. Guidance is serviceable yet consistently stops one level short of executable precision.

Suggestions

Remove the tautological "Use this skill when / Do not use this skill when" sections and the generic Instructions bullets ("Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes") — they restate the skill name and add no domain value.

Fix the dangling reference: either create `resources/implementation-playbook.md` or delete the pointer, since no such file exists in the bundle.

Add verification steps to the workflow — e.g., how to confirm a statistic is outdated, how to detect expired links, and a check that the refresh plan's priorities align with the traffic/ranking criteria before delivering output.

DimensionReasoningScore

Conciseness

The core domain lists (priorities, tactics, freshness signals) are reasonably lean, but the body includes padded filler: the tautological "Working on seo content refresher tasks or workflows" use/do-not-use sections and generic instruction bullets like "Clarify goals, constraints, and required inputs" and "Apply relevant best practices and validate outcomes" add nothing Claude doesn't know, and Focus Areas duplicates the Update Priorities list. This fits "mostly efficient but includes some unnecessary explanation or could be tightened"; it avoids a 2 because no section teaches concepts Claude already knows.

3 / 5

Actionability

Some genuinely concrete guidance exists ("Statistics older than 2 years", "Examples from 3+ years ago", the structured Content Refresh Plan template), but many bullets are abstract directives with no method — "Assess topic completeness", "Identify specific elements that need refreshing", "Recommend new sections" — leaving key execution details missing. That matches the score-3 anchor (some concrete guidance but incomplete) rather than 4, which requires mostly executable, minor-gap guidance.

3 / 5

Workflow Clarity

The 7-step Approach gives a coherent sequence (scan dates → identify statistics → find examples → check terminology → assess completeness → prioritize → recommend), but there are no validation checkpoints or feedback loops, and several steps are vague about how to execute or verify. This is not a destructive/batch skill so the cap does not bind, but the missing checkpoints fit the score-3 anchor exactly.

3 / 5

Progressive Disclosure

The body is well-sectioned with clear ## headers and is otherwise self-contained, but its only external pointer — "open `resources/implementation-playbook.md`" — references a file that does not exist in the bundle (no resources/ directory), a broken navigation path. This lands at the score-3 anchor (structure present, references not clearly viable/organized) rather than 4, whose references must be usable.

3 / 5

Total

12

/

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.

A solid description with a clear what and an explicit (if vague) when clause, naming several concrete capabilities around identifying outdated statistics, dates, and examples. Its main weaknesses are thin natural-language trigger coverage and an unspecific "Use PROACTIVELY for older content" activation phrase.

Suggestions

Replace "Use PROACTIVELY for older content" with concrete trigger phrases, e.g., "Use when the user asks to refresh, update, or modernize existing pages, blog posts, or articles, or mentions stale/outdated content."

Add natural synonyms users would actually say ("content refresh", "stale statistics", "out-of-date examples") to improve trigger term coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Identifies outdated elements", "suggests updates to maintain freshness", "Finds statistics, dates, and examples that need updating" — which goes beyond the 1-2 actions of a score-3 anchor. It is not a 5 because coverage has minor gaps (no mention of link checking, terminology, or trend monitoring that the body actually covers).

4 / 5

Completeness

Both parts are present: a clear "what" (identify outdated elements, find statistics/dates/examples, suggest updates) and an explicit trigger clause "Use PROACTIVELY for older content". It is not a 5 because the "when" is vague — "older content" is not a concrete trigger phrase, and the guideline says a 5 requires explicit concrete trigger phrases.

4 / 5

Trigger Term Quality

Relevant keywords exist ("statistics", "dates", "outdated", "older content") but common natural variations users would say are missing — e.g., "refresh", "update", "stale", "out of date", "blog post". This matches the score-3 anchor (some relevant keywords, missing common variations) rather than 4, which requires good coverage with only a few terms absent.

3 / 5

Distinctiveness Conflict Risk

The content-freshness niche ("statistics, dates, and examples that need updating") is mostly distinct from other skills. It is not a 5 because "provided content" and "older content" are broad enough that general content-editing or copywriting tasks could plausibly trigger it.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

skills/seo-content-refresher/SKILL.md

Reviewed

Table of Contents

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.