CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-title

Use when auditing page metadata or generating SEO-optimized titles. Applies to every HTML page that should appear in search results.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/meta-title/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 reference-linked body for a simple SEO rule skill. Its main weaknesses are redundancy between the intro/Explain and Check/Code Review sections and an internal inconsistency in the character-length criteria.

Suggestions

Reconcile the length thresholds: pick one standard (e.g. 50–60 ideal, 10–60 acceptable) and use it consistently across Quick Reference, Check, and Fix.

Remove or merge the "Explain" section, which nearly duplicates the intro sentence, to cut padding.

Consolidate "Check" and "Code Review" into a single verification checklist, and add an explicit re-check step after applying the fix.

DimensionReasoningScore

Conciseness

The body is compact overall, but the "Explain" section restates the intro nearly verbatim ("appears as the clickable headline in search results and browser tabs... primary on-page SEO factor") and "Code Review" duplicates the "Check" criteria, adding padding without new information.

3 / 5

Actionability

Concrete numeric criteria ("exactly one <title> tag", "between 10 and 60 characters", "primary keyword appears in the first half") and a specific Fix instruction make the guidance actionable, but the length threshold is internally inconsistent (10–60 in Check vs 50–60 in Fix and Quick Reference) and all code examples are deferred to the reference.

4 / 5

Workflow Clarity

The Quick Reference → Check → Fix structure forms a clear check-then-fix sequence with explicit criteria as checkpoints, but there is no re-verify-after-fix step and the conflicting 10–60 vs 50–60 thresholds blur the validation standard.

4 / 5

Progressive Disclosure

A single well-signaled, one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md") points to a real file that contains exactly those details; the overview/body split is clean.

5 / 5

Total

16

/

20

Passed

Description

66%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 solid description with an explicit trigger clause and natural keywords, held back by a fused what/when structure and the broad "page metadata" scope that invites overlap with related SEO skills. Adding standalone capability phrasing and terms like "title tag" would strengthen it.

Suggestions

State the capability separately from the trigger, e.g. "Audit and write SEO-optimized <title> tags for HTML pages. Use when auditing page metadata or generating titles that should rank in search results."

Add the natural trigger terms users actually say, such as "title tag", "meta tags", and "SERP", to improve trigger_term_quality.

Narrow "auditing page metadata" to title-specific metadata (e.g. "title tags and title metadata") to reduce conflict risk with sibling SEO skills like meta-description or canonical rules.

DimensionReasoningScore

Specificity

"auditing page metadata" and "generating SEO-optimized titles" name the SEO domain with two concrete actions, but coverage is not comprehensive (no mention of checking, fixing, or validating titles).

3 / 5

Completeness

An explicit "Use when..." clause with concrete trigger phrases plus a scope statement ("Applies to every HTML page that should appear in search results") covers when clearly, but the 'what' is only embedded in the trigger phrasing rather than stated as a distinct capability.

4 / 5

Trigger Term Quality

Natural phrases like "page metadata", "SEO-optimized titles", "HTML page", and "search results" give good keyword coverage, though common variations such as "title tag", "meta tags", or "SERP" are missing.

4 / 5

Distinctiveness Conflict Risk

The title-generation niche is distinct, but "auditing page metadata" is broad within SEO and would overlap with sibling metadata skills (meta descriptions, canonical URLs, og tags).

3 / 5

Total

14

/

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-title/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.