CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

56

Quality

63%

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-3

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

The body is well-structured with a useful output template and concrete priority thresholds, but it leans on generic boilerplate instructions and overlapping list sections while lacking validation checkpoints in its workflow. No bundle files are present, so disclosure is single-file.

Suggestions

Replace the generic Instructions bullets with concrete, skill-specific steps (e.g., how to detect stale statistics, which sources to cross-check).

Add an explicit validation step to the workflow, such as verifying updated statistics against a primary source before finalizing the refresh plan.

Consolidate the Deliverables, Refresh Tactics, and Freshness Signals lists to remove redundancy and cut tokens.

DimensionReasoningScore

Conciseness

Mostly bullet-driven and not padded with concepts Claude already knows, but several overlapping list sections (Deliverables, Refresh Tactics, Freshness Signals) restate the same ideas and could be tightened.

2 / 3

Actionability

The Content Refresh Plan template and concrete thresholds ('older than 2 years', '>3 positions') add specificity, but the Instructions section is generic boilerplate ('Apply relevant best practices and validate outcomes') rather than executable guidance.

2 / 3

Workflow Clarity

The Approach gives a 7-step sequence, but there are no validation checkpoints or feedback loops; the only verification mention is the vague 'validate outcomes' bullet.

2 / 3

Progressive Disclosure

It is a single self-contained file with clear section headers and no nested references, but at ~117 lines several dense list blocks could be split or trimmed rather than inlined.

2 / 3

Total

8

/

12

Passed

Description

77%Weight 40%Scale 1-3

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 states multiple concrete actions and includes an explicit when-trigger, but its trigger vocabulary is narrow and the 'older content' trigger is broad enough to risk overlap with adjacent skills. Voice is correctly third person.

Suggestions

Broaden trigger terms to natural user phrasings: 'refresh outdated content', 'update stale blog posts', 'content decay', 'update old statistics'.

Tighten the trigger to reduce conflict risk, e.g. 'Use when reviewing older published content for outdated statistics, dates, or examples.'

Drop the ALL-CAPS 'PROACTIVELY' in favor of a concrete trigger condition.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Identifies outdated elements', 'suggests updates', 'Finds statistics, dates, and examples that need updating' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Answers both what (identifies/suggests/finding outdated elements) and when via the explicit trigger clause 'Use PROACTIVELY for older content'.

3 / 3

Trigger Term Quality

Relevant keywords exist ('outdated', 'older content', 'statistics, dates, and examples') but common user phrasings like 'refresh content', 'update my blog post', or 'stale content' are missing.

2 / 3

Distinctiveness Conflict Risk

The content-freshness niche is somewhat specific, but 'older content' as the sole trigger is generic enough to overlap with general SEO or content-editing skills.

2 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
rmyndharis/antigravity-skills
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.