CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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, lean overview with concrete executable examples, a clear check-then-fix workflow with a validation checkpoint, and a clean one-level-deep reference to the existing references/rule.md.

DimensionReasoningScore

Conciseness

The body is lean — tight Quick Reference bullets, a one-line rationale, and no padding explaining what HTML or links are; every section earns its place, with only minor intro/bullet redundancy on the copy-paste point.

3 / 3

Actionability

Provides copy-paste-ready anchor patterns ("<a href=\"tel:+15551234567\">", "<a href=\"mailto:contact@example.com\">") and concrete scan regexes for phone and email detection.

3 / 3

Workflow Clarity

The Check→Fix→Explain→Code Review sequence is clear, and the Check section's "Verify that phone numbers are wrapped… Flag any that appear as plain text" acts as the validation checkpoint before fixing; as a simple skill, this is unambiguous.

3 / 3

Progressive Disclosure

The SKILL.md body is a concise overview that points one level deep to a real, clearly-signaled file ("see references/rule.md"), and references/rule.md exists in the bundle.

3 / 3

Total

12

/

12

Passed

Description

65%

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 strong, explicit trigger guidance with natural keywords, but it omits the skill's core function — it never names tel:/mailto: links or states what the skill does — leaving the "what" half unanswered and reducing distinctiveness.

Suggestions

Add a leading clause stating what the skill does, e.g. "Wraps phone numbers in tel: links and emails in mailto: links for one-tap mobile contact," before the "Use when" triggers.

Include the distinctive terms "tel: links" and "mailto: links" so the description is unlikely to be confused with a general SEO or LocalBusiness-schema skill.

Fix the grammatical fragment "Use when applies to contact pages" (missing subject) — rephrase as "Use on contact pages" or "Use when auditing contact pages."

DimensionReasoningScore

Specificity

Names the domain ("contact pages," "phone number or email address") and one action ("auditing contact UX") but never states what the skill does — wrapping/auditing tel: and mailto: links — so it is not comprehensive.

2 / 3

Completeness

The "when" is explicit and strong (two "Use when" clauses), but the "what" is missing — the description never mentions tel:/mailto: links or the skill's function, so only one half is clearly answered.

2 / 3

Trigger Term Quality

Good coverage of natural terms users would say: "contact pages," "phone number," "email address," "headers/footers," and "LocalBusiness pages."

3 / 3

Distinctiveness Conflict Risk

The trigger set is somewhat specific, but "auditing contact UX or schema-marked LocalBusiness pages" could overlap a general SEO/structured-data skill, and the distinctive tel:/mailto: terms are absent.

2 / 3

Total

9

/

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.