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

49%

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

36%Scale 1-5

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

This skill reads more like a general SEO knowledge dump than an actionable skill for Claude. It suffers from overlapping sections, vague instructions, and explains concepts Claude already understands. The output template is the strongest element, but the lack of concrete examples, validation steps, and clear workflow sequencing significantly weakens its utility.

Suggestions

Merge the overlapping 'Snippet Optimization Strategy' and 'Approach' sections into a single, clear workflow with explicit validation checkpoints (e.g., verify word count is 40-60, check question-answer alignment).

Remove the boilerplate 'Use this skill when / Do not use this skill when' sections and the Focus Areas list, which restate obvious information and waste tokens.

Add 2-3 concrete before/after examples showing how to transform regular content into snippet-optimized content, rather than just describing the formats abstractly.

Either provide the referenced 'resources/implementation-playbook.md' bundle file or remove the dead reference, and move the Advanced Tactics and Platform Implementation details into a separate reference file.

Dimension	Reasoning	Score
Conciseness	The skill explains many concepts Claude already knows (what paragraph snippets are, what table snippets are, basic SEO concepts). The 'Use this skill when' and 'Do not use this skill when' sections are tautological boilerplate. Multiple sections repeat similar ideas (Snippet Optimization Strategy vs Approach overlap significantly).	2 / 5
Actionability	The output template with markdown is somewhat concrete, but most guidance remains at the level of general advice ('Format content for snippet eligibility', 'Create multiple snippet formats') rather than executable steps. The word count guidance (40-60 words) and the output template are useful but the bulk is vague direction rather than specific, actionable instructions.	3 / 5
Workflow Clarity	There are two overlapping numbered sequences ('Snippet Optimization Strategy' and 'Approach') with no clear distinction between them, creating confusion. Neither sequence includes validation checkpoints or feedback loops. Steps like 'Determine best snippet format' lack criteria for how to make that determination.	2 / 5
Progressive Disclosure	There is a reference to 'resources/implementation-playbook.md' but no bundle files exist to support it, making it a dead reference. The content is moderately structured with headers, but inlines a lot of material (Advanced Tactics, Platform Implementation, all snippet types) that could be better organized into separate reference files.	3 / 5
	Total	10 / 20 Passed

Description

62%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 adequately communicates its purpose around featured snippet optimization and includes a 'when' clause, which is good. However, it lacks specificity about what concrete actions it performs (e.g., paragraph snippets, list snippets, table snippets) and misses several natural trigger terms users might use when seeking this functionality. The proactive trigger for 'question-based content' is helpful but narrow.

Suggestions

Add more specific actions such as 'creates paragraph snippets, list snippets, table snippets, FAQ blocks' to clarify what concrete outputs the skill produces.

Expand trigger terms to include natural synonyms like 'Google snippets', 'position zero', 'answer box', 'search result optimization', 'SEO snippets'.

Broaden the 'when' clause beyond 'question-based content' to include other scenarios like 'how-to guides', 'definition content', or 'comparison tables'.

Dimension	Reasoning	Score
Specificity	Names the domain (featured snippets/SERP features) and mentions two actions ('formats content' and 'creates snippet-optimized content blocks'), but lacks detail on what specific formatting or optimization techniques are applied.	3 / 5
Completeness	Has a clear 'what' (formats content for featured snippets, creates snippet-optimized blocks) and a 'when' ('Use PROACTIVELY for question-based content'), though the 'when' clause is somewhat narrow and could be more explicit about other trigger scenarios beyond question-based content.	4 / 5
Trigger Term Quality	Includes relevant terms like 'featured snippets', 'SERP features', and 'question-based content', but misses common user phrases like 'Google snippets', 'search results', 'position zero', 'FAQ schema', 'answer box', or 'SEO optimization'.	3 / 5
Distinctiveness Conflict Risk	Fairly distinct with its focus on featured snippets and SERP features specifically, though there could be minor overlap with general SEO or content formatting skills. The mention of 'snippet-optimized content blocks' helps differentiate it.	4 / 5
	Total	14 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/seo-snippet-hunter/SKILL.md
Commit: 57c135b

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