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

69%

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

Quality

Content

68%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-organized, mostly lean overview that delegates detail to a real one-level-deep reference, with concrete actionable guidance. Its chief weakness is the batch audit workflow lacking an inline validation or verification step, which caps workflow clarity.

Suggestions

Add an explicit Verify step to the body workflow (e.g., after fixing, re-check that 'nosnippet'/'max-snippet:0' no longer appear and that snippets render), so the batch audit includes a validation checkpoint.

Trim or fold the "Explain" section, since it restates what the nosnippet directive does — knowledge Claude already has.

Convert the reference pointer into a markdown link ("see [references/rule.md](references/rule.md)") to match the well-signaled navigation pattern expected at the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is well-sectioned and mostly lean, but the "Explain" section re-describes what the nosnippet directive does — a concept Claude already knows — which is a minor instance of over-explanation that could be trimmed.	4 / 5
Actionability	Concrete, specific instructions are given ("flag any that contain 'nosnippet' or 'max-snippet:0'", "Replace with 'max-snippet:-1'") with no inline executable code; guidance is actionable for an instruction-only skill, leaving only a minor gap that the reference file's code examples fill.	4 / 5
Workflow Clarity	Check → Fix → Code Review steps are sequenced, but this is a batch audit operation ("Check all pages", "Generate a report of affected URLs") with no validation or verification checkpoint in the body, so the batch-operation cap at 3 applies and it cannot score above 3.	3 / 5
Progressive Disclosure	The body is a concise overview split into clear sections with a well-signaled one-level-deep pointer ("see `references/rule.md`") to a real file holding details; it stops just short of the clean markdown-linked multi-reference structure that defines a 5.	4 / 5
	Total	15 / 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.

The description answers both what and when in third person with concrete page-type triggers and natural keywords, placing it solidly above average. Its main gap is that the 'what' names only one action (auditing) and omits the nosnippet/max-snippet technical terms that users would most naturally invoke.

Suggestions

Name 2-3 concrete actions in the description (e.g., 'Detect nosnippet directives, report affected pages, and replace them with max-snippet:-1') to lift specificity.

Include the technical trigger terms 'nosnippet', 'max-snippet', and 'snippet' so users searching by those keywords match naturally.

Tighten the 'what' clause to pair the audit action with the corrective action, making both halves of completeness equally explicit.

Dimension	Reasoning	Score
Specificity	"auditing robots meta tags" names the domain and one concrete action (auditing), but does not enumerate the detection, reporting, or fix actions, matching the anchor for 1-2 concrete actions rather than the several required for 4.	3 / 5
Completeness	Both what ("auditing robots meta tags") and when ("any important landing page, article, or product page that should appear with a description in search results") are answered with concrete page-type triggers, but the 'what' is thin relative to the explicit, comprehensive trigger-phrasing anchor at 5.	4 / 5
Trigger Term Quality	Natural terms a user would say are present — "robots meta tags", "search results", "landing page", "article", "product page" — but the actual technical keywords "nosnippet", "max-snippet", and "snippet" are missing, leaving a few natural terms absent.	4 / 5
Distinctiveness Conflict Risk	The robots-meta / search-snippet niche is clearly distinct with specific triggers; minor overlap risk only with closely related SEO meta skills keeps it just below the minimal-conflict anchor at 5.	4 / 5
	Total	15 / 20 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: thedaviddias/Front-End-Checklist
Path: skills/nosnippet/SKILL.md
Commit: 30756a7

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