CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

51

Quality

56%

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

Quality

Content

61%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 content is a well-structured, single-file overview with concrete formatting specs and a usable template, but it lacks executable examples and validation checkpoints in its workflow. Progressive disclosure is appropriately handled for a self-contained skill.

Suggestions

Add a concrete worked example (real question, real 40-60 word answer paragraph, and a sample FAQ schema JSON-LD block) so guidance is copy-paste ready rather than placeholder-based.

Insert an explicit validation step in the Approach workflow, e.g. 'Verify the answer paragraph is 40-60 words and the target question appears as a header before delivering.'

Tighten the generic Instructions bullets ('Apply relevant best practices and validate outcomes') which overlap with the more specific Approach steps and add little.

DimensionReasoningScore

Conciseness

The body is efficiently organized into tight bullet lists and labeled sections with minimal concept over-explanation; only minor padding (e.g., the closing 'Focus on clear, direct answers' restatement) could be trimmed.

4 / 5

Actionability

Guidance is structured and specific about formats (40-60 word paragraphs, 5-8 list items) and provides a template block, but it is instruction-only with no executable commands or code; the template uses placeholders rather than concrete examples.

3 / 5

Workflow Clarity

The Approach section lists a clear 7-step sequence, but there are no validation checkpoints or feedback loops for verifying snippet eligibility or output quality, and the generic Instructions steps are vague ('validate outcomes').

3 / 5

Progressive Disclosure

Content is well-organized into clear sections (Focus Areas, Snippet Types, Strategy, Approach, Output) at a single level with no bundle files to reference; for a self-contained skill under 50 lines this is good structure with only minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

51%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 names a specific niche and a couple of actions but stays generic in its verbs and trigger phrasing. The 'Use PROACTIVELY' directive substitutes for a natural 'Use when...' clause, which caps completeness.

Suggestions

Replace 'Use PROACTIVELY for question-based content' with an explicit natural-trigger clause such as 'Use when the user mentions featured snippets, position zero, PAA boxes, or wants content formatted for SERP rich results.'

Expand action specificity from 'Formats content'/'Creates snippet-optimized content blocks' to concrete verbs like 'Builds paragraph/list/table answer blocks, adds FAQ/HowTo schema markup, and formats question-answer pairs.'

Add synonyms and file/feature terms users actually say (position zero, PAA, rich results, FAQ schema) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (featured snippets/SERP) and two concrete actions ('Formats content', 'Creates snippet-optimized content blocks'), but the actions are somewhat generic and lack comprehensive coverage of specific formatting operations.

3 / 5

Completeness

Has a clear 'what' but the 'when' is only weakly present via 'Use PROACTIVELY for question-based content' — an imperative directive rather than an explicit natural-trigger clause, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes 'featured snippets', 'SERP features', and 'question-based content', but misses common natural variations like 'position zero', 'PAA', or 'rich results' that users would say.

3 / 5

Distinctiveness Conflict Risk

The featured-snippet/SERP niche is fairly distinct from generic SEO skills, with only minor overlap risk with broader content-optimization skills.

4 / 5

Total

13

/

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

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.