CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

70%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/seo-snippet-hunter/SKILL.md

The canonical home for this skill is seo-snippet-hunter in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

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 delivers genuinely useful, concrete snippet-formatting guidance with specific parameters and an output template. Its weaknesses are inherited template boilerplate, duplicated step lists with no real validation checkpoints, and a reference to a nonexistent file.

Suggestions

Delete the generic 'Use this skill when' / 'Do not use this skill when' and 'Instructions' sections; they add circular filler without actionable content.

Fix the dangling reference: either create `references/implementation-playbook.md` with the promised detailed examples, or remove the pointer and inline one worked example of an optimized snippet block.

Merge 'Snippet Optimization Strategy' and 'Approach' into one sequenced workflow with explicit validation steps (e.g., verify paragraph answers are 40-60 words and the question header matches the target query).

DimensionReasoningScore

Conciseness

The core sections (snippet types, word counts, output template) are tight, but the boilerplate 'Use this skill when' / 'Do not use this skill when' sections are circular filler ('Working on seo snippet hunter tasks or workflows'), the generic 'Instructions' list ('Clarify goals, constraints, and required inputs') tells Claude nothing, and the closing line repeats earlier guidance. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the 4 anchor, which requires only minor trimming.

3 / 5

Actionability

Concrete, actionable specifics dominate: exact word counts ('Paragraph Snippets (40-60 words)', 'Numbered steps (5-8 items)'), a copy-paste output template, and named schema types (FAQPage, HowTo). It is not a 5 because there is no worked example of a real optimized snippet block and tactics like 'Video timestamps for snippets' are bare one-line hints without execution detail.

4 / 5

Workflow Clarity

The 'Approach' section lists a clear 7-step sequence, but validation is only the vague boilerplate 'Apply relevant best practices and validate outcomes' with no concrete checkpoints (e.g., word-count or format verification of the produced blocks). There are also two overlapping step lists ('Snippet Optimization Strategy' vs 'Approach') that muddy the sequence, matching 'steps listed but validation gaps'.

3 / 5

Progressive Disclosure

Section headers organize the body well, but the single reference — 'open `resources/implementation-playbook.md`' — is buried in the boilerplate Instructions block, not clearly signaled as a bundle file, and no such file exists anywhere in the skill bundle (no references/, resources/, scripts/, or assets/ directories), making it a dangling pointer. This fits 'references present but not clearly signaled' with organization gaps, rather than the well-signaled structure of a 4.

3 / 5

Total

13

/

20

Passed

Description

70%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.

A solid description in correct third-person voice: it states what the skill does and includes an explicit, if terse, trigger clause. Main gaps are the thin 'when' clause and missing common synonyms like 'position zero' or 'People Also Ask'.

Suggestions

Expand the 'when' clause with concrete triggers, e.g. 'Use when the user mentions featured snippets, position zero, answer boxes, People Also Ask, or SERP features.'

Add 1-2 more specific actions to the 'what' (e.g., 'generates PAA question/answer pairs and FAQ/HowTo schema markup') to lift specificity.

Drop the filler phrase 'based on best practices', which adds no information.

DimensionReasoningScore

Specificity

The description names the domain ('featured snippets and SERP features') and two concrete actions ('Formats content to be eligible for featured snippets', 'Creates snippet-optimized content blocks'), matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because 'based on best practices' is generic filler and no further specific actions (e.g., PAA pairs, schema markup, format recommendations) are named.

3 / 5

Completeness

Both parts are present: a clear 'what' ('Formats content to be eligible for featured snippets and SERP features. Creates snippet-optimized content blocks') and an explicit 'when' ('Use PROACTIVELY for question-based content'). It is not a 5 because the 'when' clause is terse and lacks concrete trigger phrases (e.g., 'when the user mentions featured snippets, position zero, or People Also Ask'); it is above 3 because the trigger guidance is explicit rather than merely implied.

4 / 5

Trigger Term Quality

'featured snippets', 'SERP features', and 'question-based content' are natural phrases an SEO user would say, giving good keyword coverage. It is not a 5 because common synonyms like 'position zero', 'answer box', 'People Also Ask', or 'rich results' are missing.

4 / 5

Distinctiveness Conflict Risk

The featured-snippet/SERP niche is well-defined with distinct triggers, so it is mostly distinguishable from other skills. It is not a 5 because 'Formats content' and 'question-based content' have minor overlap risk with general content-formatting or copywriting skills.

4 / 5

Total

15

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/seo-snippet-hunter/SKILL.md

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.