seo-snippet-hunter

Formats content to be eligible for featured snippets and SERP features. Creates snippet-optimized content blocks based on best practices. Use PROACTIVELY for question-based content.

Quality

50%

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-snippet-hunter/SKILL.md

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 content is well-organized and free of concept padding, with useful concrete specifics like word-count targets, schema types, and an output template. It is held back by duplicated step-lists, placeholder-only examples, missing validation checkpoints, and a monolithic single-file structure.

Suggestions

Merge the redundant 'Snippet Optimization Strategy' and 'Approach' sections into one sequenced workflow with explicit validation checkpoints (e.g. 'verify the answer paragraph is 40-60 words and leads with the keyword').

Add at least one fully worked example (a real question with a complete 40-60 word answer block) instead of placeholder-only templates.

Move platform implementation details and advanced tactics into reference files (e.g. PLATFORMS.md, ADVANCED.md) and link to them one level deep to reduce the monolithic body.

Dimension	Reasoning	Score
Conciseness	The body is largely lean lists with no concept over-explanation, but 'Snippet Optimization Strategy' and 'Approach' overlap heavily and could be merged, and the 'You are a featured snippet optimization specialist' line is mild role fluff.	2 / 3
Actionability	Provides concrete specifics (40-60 word targets, 5-8 item lists, named schema types FAQPage/HowTo, an output template, platform notes), but the template uses placeholders rather than a fully worked example and several 'Approach' steps remain abstract.	2 / 3
Workflow Clarity	Steps are listed and sequenced, but two overlapping step-lists (Strategy vs Approach) make the intended workflow ambiguous, and there are no validation checkpoints (e.g. verify answer length, confirm snippet eligibility).	2 / 3
Progressive Disclosure	The skill is well-sectioned with clear headers, but at ~104 lines with no bundle files it is a single-file monolith; platform implementation, advanced tactics, and full schema templates that could be split out are all inline.	2 / 3
	Total	8 / 12 Passed

Description

50%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 identifies a clear niche and uses proper third-person voice with a couple of concrete actions, but its trigger guidance is directive rather than natural and its keyword coverage is limited. It sits solidly at the midpoint across all dimensions.

Suggestions

Rewrite the trigger as a natural 'Use when...' clause, e.g. 'Use when optimizing content for featured snippets, position zero, answer boxes, or question-based SERP features.'

Expand trigger-term coverage to include common variations users say: 'position zero', 'answer box', 'rich results', 'PAA', 'People Also Ask'.

Replace 'based on best practices' with one or two more concrete actions (e.g. 'structures question-answer blocks, builds comparison tables, adds FAQ/HowTo schema').

Dimension	Reasoning	Score
Specificity	Names the snippet/SERP domain and two concrete actions ('Formats content to be eligible for featured snippets', 'Creates snippet-optimized content blocks'), but 'based on best practices' is vague padding rather than a comprehensive list of distinct actions.	2 / 3
Completeness	Answers 'what' clearly and provides a 'when', but the trigger is phrased as a directive ('Use PROACTIVELY for question-based content') rather than a natural user-speech 'Use when...' clause, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Includes genuine natural terms ('featured snippets', 'SERP features', 'question-based content') but coverage is thin, missing common variations like 'position zero', 'answer box', 'rich results', or 'PAA'.	2 / 3
Distinctiveness Conflict Risk	The featured-snippet/SERP niche is fairly distinct, but the broad 'question-based content' trigger could overlap with general content, FAQ, or SEO skills, leaving some conflict risk.	2 / 3
	Total	8 / 12 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-snippet-hunter/SKILL.md
Commit: e63f7dd

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