CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tel-mailto

Use when applies to contact pages, business listing pages, headers/footers, and any page displaying a phone number or email address. Use when auditing contact UX or schema-marked LocalBusiness pages.

Quality

69%

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/tel-mailto/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The content is a well-structured, actionable overview for a simple single-purpose rule: concrete href examples and scan regexes make the Check and Fix steps immediately executable, and implementation detail is appropriately deferred to the single, clearly-signaled references/rule.md. Minor gains are available from removing the duplicated E.164 and copy-paste-friction statements and making the verification step an explicit checkpoint.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no padding explaining HTML or what contact links are, with concrete guidance in tight sections ("Wrap phone numbers in `<a href="tel:+15551234567">`..."). It is not a 5 because of minor redundancy: the E.164 format rule appears in both Quick Reference and Fix, and the plain-text copy-paste friction point appears in both the intro and Quick Reference — a few tokens could be trimmed.

4 / 5

Actionability

Concrete, near copy-paste guidance dominates: exact href examples ("`<a href="tel:+15551234567">+1 (555) 123-4567</a>`"), scanning regexes ("\+?[0-9\s\-().]{7,}" and "[\w.-]+@[\w.-]+\.[a-z]{2,}"), and explicit fix patterns. It is not a 5 because the Check regexes are hedged ("patterns like") rather than definitive, and the Explain/Code Review sections are abstract directives without concrete verification commands; it is well above 3 since the core fix guidance is executable rather than pseudocode.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clearly delineated by headed sections, and Code Review says to "describe how to verify the final page output". It is not a 5 because verification is mentioned as an instruction rather than an explicit validation checkpoint (no feedback loop for flagged-but-unfixed cases), matching 'Clear sequence with most checkpoints present; minor validation gaps' rather than the explicit validate-fix-retry pattern. This is a simple non-destructive audit skill, so the destructive/batch cap at 3 does not apply.

4 / 5

Progressive Disclosure

The body is a concise ~34-line overview with clear section headers, and the single deeper detail is cleanly offloaded: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — a well-signaled, one-level-deep reference that exists in the bundle. This matches the anchor 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation' with no nesting or buried references.

5 / 5

Total

17

/

20

Passed

Description

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

The description has solid trigger coverage for the contact-page/local-business domain but never states what the skill does — no capability or action is mentioned, only when to use it. It reads as a trigger-only sentence (with a grammatically awkward 'Use when applies to') that would leave Claude guessing about the skill's actual function.

Suggestions

Add a leading 'what' clause with concrete actions, e.g., 'Audits and fixes tel: and mailto: link markup on pages: wraps phone numbers in <a href="tel:..."> and emails in <a href="mailto:..."> using E.164 format.'

Include the core natural trigger terms 'tel link', 'mailto link', and 'click-to-call' so users requesting this specific fix phrase-match naturally.

Fix the ungrammatical 'Use when applies to contact pages' phrasing to a proper clause such as 'Use when working on contact pages' or merge it into a single well-formed 'Use when...' sentence.

DimensionReasoningScore

Specificity

The description names the domain ("contact pages, business listing pages, headers/footers, and any page displaying a phone number or email address") but states no concrete actions — there is no verb describing what the skill does (e.g., wrap numbers in tel: links, audit markup). This matches the anchor 'Names the domain but actions are minimal or generic'; it is not a 3 because no 1-2 concrete actions are ever listed, and not a 1 because the domain itself is specific rather than pure abstraction.

2 / 5

Completeness

Only the 'when' is present ("Use when applies to contact pages..." and "Use when auditing contact UX..."); the 'what' — what the skill actually does — is never stated. This exactly matches the anchor 'only when is present without what'. It is not a 3 because a clear 'what' is entirely missing rather than weakly implied, and not a 1 because the 'when' clauses are concrete and specific. The awkward 'Use when applies to' phrasing further degrades clarity of the trigger statement.

2 / 5

Trigger Term Quality

Natural user phrases are present: "contact pages", "phone number", "email address", "contact UX", "schema-marked LocalBusiness pages" — good keyword coverage. It falls short of 5 because core natural synonyms like "tel link", "mailto", and "click-to-call" are absent; it is above 3 because several natural phrases users would actually say are included, not just generic or jargon terms.

4 / 5

Distinctiveness Conflict Risk

Triggers are mostly distinct — phone/email links on contact and LocalBusiness pages carve a clear niche unlikely to fire unrelated skills. Minor overlap risk remains with closely related skills (e.g., a general local-business schema or contact-page rule, given "schema-marked LocalBusiness pages"), matching the anchor 'Mostly distinct; minor overlap risk with closely related skills' rather than 5's minimal-conflict bar.

4 / 5

Total

12

/

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/tel-mailto/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.