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

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

57%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, mostly actionable instruction set with concrete thresholds and an output template. Its weaknesses are redundant list sections that pad token cost, missing validation checkpoints in the workflow, and no progressive disclosure despite exceeding a concise single-file scope.

Suggestions

Consolidate overlapping list blocks (Focus Areas / Update Priorities / Refresh Priority Matrix and Deliverables / Refresh Tactics / Freshness Signals) into single tighter sections to reduce redundancy.

Add a validation checkpoint to the Approach workflow, e.g. a step to verify flagged statistics/dates against current sources before finalizing the refresh plan.

Move the Refresh Priority Matrix and Platform Implementation details into a referenced reference file (e.g. references/refresh-matrix.md) and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient list-based content with no over-explanation of basics, but several overlapping list blocks (Focus Areas vs. Update Priorities vs. Refresh Priority Matrix; Deliverables vs. Refresh Tactics vs. Freshness Signals) add padding that could be consolidated.	3 / 5
Actionability	Provides concrete decision thresholds ("Statistics older than 2 years", "Examples from 3+ years ago", "Pages losing rankings >3 positions") and a copy-ready output template, with only minor gaps on how to locate the outdated elements.	4 / 5
Workflow Clarity	The 7-step Approach sequence is clear, but no validation or verification checkpoints are provided to confirm findings before producing the refresh plan.	3 / 5
Progressive Disclosure	Sections are clearly headed and organized, but the skill exceeds 50 lines with all content inlined and no bundle files or signaled references to split out the priority matrix or platform-implementation detail.	3 / 5
	Total	13 / 20 Passed

Description

75%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 is solid: it names concrete capabilities, includes an explicit trigger phrase, and occupies a distinct niche. The main weakness is the terse, slightly generic trigger guidance that could add more natural synonyms and concrete trigger scenarios.

Suggestions

Expand the trigger guidance with concrete natural phrases users would say, e.g. "Use when refreshing old blog posts, updating stale statistics, or reviving declining pages."

Add synonyms and variations such as "refresh", "update", and "stale" to broaden natural keyword coverage.

Tighten the action list to name what kind of updates are suggested (e.g. "replaces outdated statistics, updates dates in titles, adds recent examples") for fuller specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("Identifies outdated elements", "Finds statistics, dates, and examples", "suggests updates") with only minor coverage gaps on what the updates entail.	4 / 5
Completeness	Clearly states what the skill does and provides an explicit "Use PROACTIVELY for older content" trigger, but the when-guidance is terse and could be more specific.	4 / 5
Trigger Term Quality	Includes natural terms (outdated, older content, statistics, dates, freshness) with an explicit trigger phrase, but misses common synonyms users would say like "refresh" or "stale".	4 / 5
Distinctiveness Conflict Risk	Targets a fairly distinct content-freshness niche with clear triggers, with only minor overlap risk against general content-editing or SEO skills.	4 / 5
	Total	16 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/seo-content-refresher/SKILL.md
Commit: 3eff4af

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