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

78%

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/meta-in-body/SKILL.md

Quality

Content

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

A well-structured, actionable skill body that delegates detail to a real one-level-deep reference and keeps the overview focused on detection and remediation. The main improvement would be de-duplicating the detection instructions restated across Quick Reference/Check/Code Review and making the validation step an explicit workflow checkpoint.

Suggestions

Consolidate the detection instructions repeated across 'Quick Reference', 'Check', and 'Code Review' into a single canonical procedure to remove the redundancy and tighten token use.

Make the HTML-validator / parsed-DOM validation an explicit numbered checkpoint in the workflow (e.g., a 'Verify' step after 'Check') rather than only a bullet in Quick Reference.

Lead the description with a concrete action verb (e.g., 'Detects <meta> tags misplaced in the document body') so the 'what' is as explicit as the 'when'.

Dimension	Reasoning	Score
Conciseness	Mostly lean and efficient with no basic-concept padding, but the detection logic is restated across 'Quick Reference', 'Check', and 'Code Review', and the opening sentence repeats the 'ignored by search engines' point, giving minor trim opportunities.	4 / 5
Actionability	Provides concrete, executable guidance ('Parse the HTML and check whether any <meta> elements appear outside <head>', 'refactor the injection to target document.head instead of document.body') with specific elements named; the body lacks runnable code/commands, which are appropriately delegated to the reference file.	4 / 5
Workflow Clarity	Clear Check → Fix → Explain sequence plus a dedicated Code Review traversal procedure, with validation signaled ('Validate with HTML validator or inspect parsed DOM'); this is a detection/audit skill so no destructive-batch cap applies, though validation checkpoints are implicit rather than explicit steps.	4 / 5
Progressive Disclosure	Clean overview with well-organized sections and a clearly signaled one-level-deep reference to references/rule.md (verified to exist on disk); content is appropriately split between the summary and the reference.	5 / 5
	Total	17 / 20 Passed

Description

78%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 focused, well-triggered description that clearly signals when to use the skill and names the specific meta-tag types and injection sources involved. It is concise and distinguishable, with only minor room to lead with a sharper action verb and add a couple of common synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain ('auditing HTML document structure') and enumerates concrete specifics — 'noindex, canonical-url, description, viewport, OG tags' and injection sources ('CMS plugins, widgets, or JavaScript rendering') — with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('auditing HTML document structure' / meta-in-body detection) and when ('Use when auditing... Applies to any page where meta tags... may have been injected into the body'), though the 'what' action is slightly implied rather than stated as a leading verb.	4 / 5
Trigger Term Quality	Includes natural terms users would say ('meta tags', 'noindex', 'canonical-url', 'OG tags', 'injected into the body', 'CMS plugins') with good coverage; a few common synonyms like 'SEO tags' or 'head tags' are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — meta tags misplaced in <body> — with specific, distinctive triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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/meta-in-body/SKILL.md
Commit: 30756a7

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