CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nosnippet

Use when auditing robots meta tags. Applies to any important landing page, article, or product page that should appear with a description in search results.

Quality

72%

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

Quality

Content

71%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 is a well-structured overview with genuinely actionable check/fix guidance and exemplary progressive disclosure through its single well-signaled reference. Its main weakness is redundancy — the impact explanation appears three times and two sections duplicate the same audit instructions — which costs tokens without adding guidance.

Suggestions

Merge the Check and Code Review sections — both instruct the same audit (parse <meta name='robots'> content and X-Robots-Tag headers for 'nosnippet'/'max-snippet:0'), so one section with the report-generation detail suffices.

Cut the Explain section or fold its one non-duplicated fact into the intro; the CTR impact is already stated in both the intro and Quick Reference.

Add a short inline example of the fixed tag (<meta name='robots' content='index, follow, max-snippet:-1'>) to the Fix section so the common case is copy-paste ready without opening the reference.

DimensionReasoningScore

Conciseness

The reduced-click-through-rate fact is stated three times (intro, "Pages without snippets have significantly lower click-through rates" in Quick Reference, and the Explain section), and the Check and Code Review sections repeat nearly identical meta tag/X-Robots-Tag audit instructions — mostly efficient but clearly could be tightened.

3 / 5

Actionability

Concrete, executable guidance throughout: exact values to flag ("'nosnippet' or 'max-snippet:0'"), an exact replacement ("'max-snippet:-1'"), and both the <meta name='robots'> tag and X-Robots-Tag header. Minor gaps — no inline HTML example or crawl command, though the reference file carries those.

4 / 5

Workflow Clarity

A simple single-task skill with a clear Check → confirm-intent → Fix sequence and an explicit validation checkpoint ("Confirm these pages intentionally suppress snippets"), but the overlapping Code Review and Explain sections after Fix blur the sequence, keeping it just below fully clear.

4 / 5

Progressive Disclosure

The body is a concise, well-sectioned overview that delegates implementation details, code examples, and framework guidance to a clearly signaled, verified, one-level-deep reference ("see `references/rule.md`") — matching the ideal split between overview and reference material.

5 / 5

Total

16

/

20

Passed

Description

62%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 answers both what and when with an explicit trigger clause and a clear audience scope, but its action vocabulary is thin (only 'auditing') and it omits the most natural trigger terms for this problem — nosnippet and snippet. It is a solid mid-range description that would benefit from naming the specific directives it checks and fixes.

Suggestions

Add the natural trigger terms users would say for this issue — "nosnippet", "snippet", and "max-snippet" — since someone hitting this problem will search using those directive names, not the generic phrase "robots meta tags".

State the concrete actions, e.g. "Flags and fixes nosnippet and max-snippet:0 directives so important pages keep their search-result descriptions" instead of the generic "auditing robots meta tags".

Include "SEO" or "search appearance" as a keyword to widen natural-language matching without sacrificing distinctiveness.

DimensionReasoningScore

Specificity

"Use when auditing robots meta tags" names the domain plus a single concrete action (auditing), but never states the specific actions of flagging and fixing the nosnippet directive, matching the '1-2 concrete actions, but not comprehensive' anchor.

3 / 5

Completeness

Both halves are present: an explicit "Use when auditing robots meta tags" trigger and a what (auditing), plus scope ("any important landing page, article, or product page that should appear with a description in search results"). Not 5 because the what stays generic — no concrete phrase like 'flag and fix nosnippet directives'.

4 / 5

Trigger Term Quality

Relevant keywords are present ("robots meta tags", "landing page", "search results"), but the most natural terms a user would say for this exact issue — "nosnippet", "snippet", "SEO", "max-snippet" — are missing, fitting 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The snippet-suppression niche is mostly distinct, but "auditing robots meta tags" broadly could also match sibling SEO skills (noindex auditing, meta-description rules), giving minor overlap risk consistent with the 'mostly distinct' anchor.

4 / 5

Total

14

/

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

thedaviddias/Front-End-Checklist

Path

skills/nosnippet/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.