CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/meta-in-body/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.

A well-structured, appropriately decomposed skill body: a concise overview with a clearly signaled reference file holding the code examples and framework detail. The main cost is redundancy — the same rule is restated across four sections, and the Explain section teaches a concept Claude already knows.

Suggestions

Merge or drop the Explain section (it restates the intro's point about meta tags being document-level metadata) to remove the largest redundant passage.

Consolidate the Check and Code Review sections, which describe the same detection procedure twice.

Make post-fix validation an explicit final step (e.g., 'After moving tags, re-run the validator and re-inspect the parsed DOM to confirm all metas resolve to <head>') to close the workflow's validation loop.

DimensionReasoningScore

Conciseness

The core rule — meta tags belong in <head> and are ignored in <body> — is restated in the intro, Quick Reference, Fix, and Explain sections (e.g., "Meta tags are document-level metadata and must live in <head>..."). The Explain section in particular covers a basic HTML fact Claude already knows, matching anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened'); it is above anchor 2 because there is no library tutorial-style padding, and below anchor 4 because the repetition and the concept-explanation section are more than minor.

3 / 5

Actionability

Guidance is concrete and specific: "traverse up the parent chain — if any ancestor is <body> ... flag it", "refactor the injection to target document.head instead of document.body", with named targets (meta name='robots', meta property='og:*', link rel='canonical'). This matches anchor 4 ('mostly executable guidance; concrete ... with minor gaps'); as an instruction-only skill the absence of code is acceptable per the rubric notes, but a ready-to-run selector/snippet (delegated to references/rule.md) keeps it from anchor 5.

4 / 5

Workflow Clarity

The Check → Fix sequence is clear and ordered, with a verification step named in Quick Reference ("Validate with HTML validator or inspect parsed DOM to confirm placement") and error-recovery direction in Fix (retarget the injection script). This fits anchor 4 ('clear sequence with most checkpoints present; minor validation gaps'); it falls short of anchor 5 because the post-fix re-validation loop is implied rather than an explicit step, and the intervening Explain / Code Review sections blur the single flow.

4 / 5

Progressive Disclosure

The body is a lean ~45-line overview organized into labeled sections (Quick Reference, Check, Fix, Explain, Code Review), ending with a clearly signaled one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — a real file that contains exactly that. This matches anchor 5 ('clear overview with well-signaled one-level-deep references; content appropriately split').

5 / 5

Total

16

/

20

Passed

Description

73%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 well-targeted, distinctive description with an explicit 'Use when' trigger and rich domain keywords. Its main weakness is that the capability side is thin: it says when the skill applies more concretely than what the skill actually does.

Suggestions

Lead with a concrete capability statement (e.g., 'Detects and flags meta tags placed in <body> and moves them into <head>') before the 'Use when' clause.

Add one or two more natural trigger phrases such as 'SEO audit' or 'search engine directives not being honored' to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names one concrete action — "auditing HTML document structure" — and a well-defined domain (meta tags injected into body), but does not list the specific actions the skill performs (detect, flag, fix). This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'); it is below anchor 4 because no multiple specific actions are enumerated, and above anchor 2 because the domain and applicability conditions are concrete, not generic.

3 / 5

Completeness

It has an explicit 'Use when auditing HTML document structure' trigger clause plus a clear applicability statement ("Applies to any page where meta tags ... may have been injected into the body"), so both what and when are present — matching anchor 4. It falls short of anchor 5 because the 'what' is a single generic action ('auditing') rather than a concrete statement of what the skill does (e.g., 'Detects and fixes meta tags placed in <body>').

4 / 5

Trigger Term Quality

Strong natural terms users would say in this niche: "meta tags", "noindex", "canonical-url", "viewport", "OG tags", "CMS plugins", "widgets", "JavaScript rendering", "injected into the body". This fits anchor 4 ('good keyword coverage; a few natural terms missing') rather than 5 because common variations like "SEO", "search engines", or "<head>" phrasing are absent.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly delimited — meta tags misplaced in body, with named directives (noindex, canonical-url, OG tags) and named injection sources (CMS plugins, widgets, JavaScript rendering). Triggers are distinct and unlikely to fire for unrelated skills, matching the anchor 5 example's clear-niche pattern.

5 / 5

Total

16

/

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