meta-in-body

Use when auditing HTML document structure. Applies to any page where meta tags (noindex, canonical-url, description, viewport, OG tags) may have been injected into the body by CMS plugins, widgets, or JavaScript rendering.

Quality

95%

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

100%

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

A well-structured, lean instruction skill with actionable guidance, a clear workflow, and clean one-level-deep progressive disclosure to a real reference file. There is light redundancy across the Check and Code Review sections but it does not meaningfully harm the skill.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding of concepts Claude already knows; each section (Quick Reference, Check, Fix, Explain, Code Review) earns its place, with only minor restatement across sections.	3 / 3
Actionability	Guidance is concrete and specific — 'refactor the injection to target document.head instead of document.body' and the Code Review algorithm (traverse the parent chain, flag if an ancestor is <body>) — with no code only because it is an instruction-only skill, which the rubric does not penalize.	3 / 3
Workflow Clarity	The Check → Fix → Explain → Code Review flow is an unambiguous sequence for a single, non-destructive task; the simple-skill note allows a 3 without an explicit validation checkpoint.	3 / 3
Progressive Disclosure	The body is a concise overview that clearly signals a one-level-deep reference ('see references/rule.md'), and that bundle file exists and holds the detailed implementation.	3 / 3
	Total	12 / 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.

A strong, trigger-led description with good keyword coverage and a clear, narrow niche. Its main weakness is framing around one action ('auditing') rather than enumerating multiple concrete actions, capping specificity at 2.

Suggestions

Lead with a verb list of concrete actions (e.g., 'Detect, locate, and report meta tags misplaced in the document body') to lift specificity.

Consider trimming the long enumeration of injection causes to keep the description tighter without losing trigger terms.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain ('auditing HTML document structure') and enumerates specific targets (noindex, canonical-url, description, viewport, OG tags) and injection causes, but centers on a single action ('auditing') rather than listing multiple distinct actions, so it falls short of the multi-verb anchor at score 3.	2 / 3
Completeness	It explicitly answers both what (auditing HTML structure / detecting meta tags injected into body) and when, opening with an explicit 'Use when auditing HTML document structure' trigger.	3 / 3
Trigger Term Quality	It covers natural terms users would say for this task — 'meta tags', 'noindex', 'canonical-url', 'viewport', 'OG tags', 'HTML', 'body' — matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	The narrowed niche — meta tags misplaced in the body via CMS plugins/widgets/JS rendering — is a distinct trigger set unlikely to fire 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/meta-in-body/SKILL.md
Commit: 48405aa

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