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

88%

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

Quality

Content

87%

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

The body is lean, well-organized, and properly delegates detail to a single real reference file. The main gap is the absence of an explicit validation/verification checkpoint within the body itself for the audit workflow.

Suggestions

Add an explicit 'Verify' step in the body (e.g., re-crawl affected URLs after the fix and confirm no 'nosnippet'/'max-snippet:0' remains) rather than relying solely on references/rule.md for verification.

Include one executable detection snippet in the Check section (e.g., a grep/curl command over rendered HTML and X-Robots-Tag headers) so the audit step is copy-paste runnable.

Trim the 'Explain' section, which restates the Quick Reference, to reduce token overlap.

Dimension	Reasoning	Score
Conciseness	Tight bulleted sections (Quick Reference, Check, Fix, Explain, Code Review) with no padding or explanation of basic SEO concepts Claude already knows; the slight overlap between Explain and Quick Reference does not rise to verbosity.	3 / 3
Actionability	Concrete detection targets ('nosnippet', 'max-snippet:0', X-Robots-Tag header) and a specific remediation ('Replace with max-snippet:-1') give copy-applicable, actionable guidance; being instruction-only is not penalized since the guidance is specific.	3 / 3
Workflow Clarity	Check/Fix/Explain/Code Review provide a sequence, but the body has no explicit verification checkpoint (the verify loop lives only in references/rule.md), leaving validation implicit for a batch audit.	2 / 3
Progressive Disclosure	The body is a concise overview with a clearly signaled, one-level-deep pointer ('see references/rule.md'), and that referenced bundle file exists, matching the ideal overview-plus-reference structure.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 is concise, uses third person, and provides an explicit 'Use when' trigger with natural keywords and clear scope. Its only weakness is that it names a single action rather than enumerating multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and page scope ('auditing robots meta tags', 'landing page, article, or product page') with a single concrete action verb, but does not enumerate multiple distinct actions, so it falls short of a 3.	2 / 3
Completeness	An explicit 'Use when...' trigger states when to apply it, and 'Applies to any important...page that should appear with a description' states what it targets, answering both what and when.	3 / 3
Trigger Term Quality	'Use when auditing robots meta tags' plus 'landing page', 'article', 'product page', and 'search results' gives good coverage of natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The robots-meta-tags audit niche with nosnippet-specific framing is distinct and unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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: 48405aa

Reviewed: about 8 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.