CtrlK
BlogDocsLog inGet started
Tessl Logo

meta-title

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

66

Quality

80%

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

85%

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

The body is a well-structured, actionable audit skill with clean progressive disclosure to a real reference file; its only weakness is the 'Explain' section and some section overlap that restate concepts Claude already knows.

Suggestions

Remove or trim the 'Explain' section, which restates what a <title> tag is and basic SEO ranking concepts Claude already knows.

Consolidate overlapping Quick Reference, Check, and Code Review sections to reduce redundancy and save tokens.

DimensionReasoningScore

Conciseness

The body is mostly lean actionable bullets and a checklist, but the 'Explain' section restates what a <title> tag is and that Google uses it for ranking — concepts Claude already knows — and the Quick Reference/Check/Fix/Code Review sections overlap, so it is mostly efficient with some unnecessary explanation.

2 / 3

Actionability

Provides concrete, specific audit guidance — exact character ranges (50–60, 10–60), keyword placement, uniqueness rules, and an ordered 5-point Code Review checklist; as an instruction-only skill the absence of inline code is not penalized because the guidance is actionable and specific.

3 / 3

Workflow Clarity

For this simple single-purpose audit task the Check→Fix flow and the ordered Code Review checklist make the action unambiguous, satisfying the simple-skill allowance where a clear single action scores 3.

3 / 3

Progressive Disclosure

Well-organized sections (Quick Reference, Check, Fix, Explain, Code Review) with a clearly signaled one-level-deep reference to references/rule.md (verified to exist), matching the clear-overview-with-well-signaled-references anchor.

3 / 3

Total

11

/

12

Passed

Description

75%

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 has an explicit 'Use when...' trigger and a clear, distinct SEO-title niche, but its action list is somewhat high-level and its trigger terms omit common phrasings like 'page title' and 'title tag'.

Suggestions

Expand the action list with more specific concrete operations (e.g., 'audit <title> length, uniqueness, and keyword placement') to reach anchor 3 for specificity.

Add common natural trigger terms users would say — 'page title', 'meta title', 'title tag' — alongside the existing ones to improve trigger coverage.

Keep the strong 'Use when...' trigger; consider tightening 'auditing page metadata' to focus on the title-specific scope of this skill.

DimensionReasoningScore

Specificity

Names two concrete actions ('auditing page metadata', 'generating SEO-optimized titles') but they are high-level and not a comprehensive list of specific operations, matching the 'names domain and some actions' anchor rather than the multiple-specific-actions anchor 3.

2 / 3

Completeness

Explicitly answers both what ('auditing page metadata or generating SEO-optimized titles') and when via a prominent 'Use when...' clause, satisfying the anchor for clearly answering both what and when with explicit triggers.

3 / 3

Trigger Term Quality

Includes relevant natural terms ('page metadata', 'SEO-optimized titles', 'HTML page', 'search results') but misses common variations users would say such as 'page title', 'meta title', or 'title tag', so coverage is partial rather than full.

2 / 3

Distinctiveness Conflict Risk

Scoped narrowly to page metadata and SEO titles for HTML pages in search results, a clear niche with distinct triggers unlikely to conflict with other skills.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.