A skill your agent uses when applies to contact pages, business listing pages, headers/footers, and any page displaying a phone number or email address.

MITAuto-check passed

Install Tel Mailto

skills CLI
$ npx skills add thedaviddias/Front-End-Checklist --skill tel-mailto -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thedaviddias/Front-End-Checklist tel-mailto --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tel-mailto .claude/skills/tel-mailto && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tel-mailto
GitHub stars
74k
Token cost
~549 tokens
SKILL.md length
230 words
Files
2 (incl. references)
Skills in repo
390
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when applies to contact pages, business listing pages, headers/footers, and any page displaying a phone number or email address.

  • Applies to contact pages
  • SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Business listing pages

What it does

Tel Mailto is an agent skill from thedaviddias/Front-End-Checklist. 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.

Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).

The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.

When your agent uses it

  • Applies to contact pages
  • Business listing pages
  • Headers/footers
  • Any page displaying a phone number

Example prompts

  • “/tel-mailto”

What it can do on your machine

Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • frontendchecklist.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tel Mailto loads about 549 tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 230 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~549
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 230 words, ~549 tokens.

Download SKILL.mdSave it as .claude/skills/tel-mailto/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
tel-mailto
description
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.
metadata.category
seo
metadata.priority
medium
metadata.difficulty
beginner
metadata.estimatedTime
10
metadata.source
frontendchecklist.io
metadata.url
https://frontendchecklist.io/rules/seo/tel-mailto

On mobile devices, tel: and mailto: links trigger the native phone dialer and email client with one tap; plain-text contact info forces copy-paste and measurably reduces contact conversion rates.

Quick Reference

  • Wrap phone numbers in <a href="tel:+15551234567"> for click-to-call on mobile devices
  • Wrap email addresses in <a href="mailto:contact@example.com"> for one-click email compose
  • Use E.164 format for tel: links: + followed by country code and number, no spaces or dashes
  • Plain text phone numbers and emails require users to copy-paste — a UX and conversion friction point

Check

Scan the HTML for phone numbers (patterns like \+?[0-9\s\-().]{7,}) and email addresses ([\w.-]+@[\w.-]+\.[a-z]{2,}). Verify that phone numbers are wrapped in <a href="tel:..."> and emails in <a href="mailto:...">. Flag any that appear as plain text.

Fix

Wrap each phone number in an anchor tag: <a href="tel:+15551234567">+1 (555) 123-4567</a>. Wrap each email in: <a href="mailto:contact@example.com">contact@example.com</a>. Format tel: values using E.164 (+[country][number]) without spaces.

Explain

Explain how tel: and mailto: URI schemes work in HTML, why E.164 format is required for international compatibility, and how these links improve mobile UX and contact conversion rates.

Code Review

Review metadata generation, rendered HTML, structured data, and response headers related to Tel & Mailto Links. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/rules/seo/tel-mailto

© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/tel-mailto of thedaviddias/Front-End-Checklist.

  • SKILL.md
  • references/rule.md

Open the folder on GitHubat commit e8d14d0

Compare with similar skills

Tel Mailto next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tel Mailto compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tel Mailto this skillthedaviddias/Front-End-Checklist74k—~549Automated safety check: PassMIT
Music Listruvnet/ruflo74k—~332Automated safety check: PassMIT
Mailtrap Managing Contactssickn33/agentic-awesome-skills47k1 repos~1.9kAutomated safety check: PassMIT
Contact Widgetnexu-io/open-design100k—~1.6kAutomated safety check: PassApache-2.0
Etsy Search Listingssickn33/agentic-awesome-skills47k1 repos~1.2kAutomated safety check: PassMIT
Contactsvellum-ai/vellum-assistant1.4k—~8.9kAutomated safety check: PassMIT

Similar skills

  • Music List

    ruvnet/ruflo

    List the account's saved music productions with metadata and audiourl

    74k GitHub stars~332 tokensUpdated yesterday
    Auto-check passed
  • Mailtrap Managing Contacts

    sickn33/agentic-awesome-skills

    Manage Mailtrap contacts, lists, segments, custom fields, imports, CRM syncs, and campaign audiences through the UI or API.

    47k GitHub starsUsed in 1 repo~1.9k tokens
    Sales & SupportAuto-check passed
  • Contact Widget

    nexu-io/open-design

    Self-contained floating chat widget with welcome screen, social links, meeting button, and message input.

    100k GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Etsy Search Listings

    sickn33/agentic-awesome-skills

    Fetch live Etsy search listing rows for a keyword, market phrase, or category via Apify Actor publicrecords/etsy-search-scraper (MCP).

    47k GitHub starsUsed in 1 repo~1.2k tokens
    Data & AnalyticsAuto-check passed
  • Contacts

    vellum-ai/vellum-assistant

    Manage contacts, communication channels, access control, and invite links

    1.4k GitHub stars~8.9k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed
  • Export Google Contacts directory to a Google Sheets spreadsheet.

    31k GitHub stars~249 tokensUpdated 4 days ago
    Documents & OfficeAuto-check passed

More from thedaviddias/Front-End-Checklist

All 390 skills in this repo
  • Content Dates Audit

    thedaviddias/Front-End-Checklist

    Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.

    74k GitHub stars~691 tokensUpdated 5 days ago
    Auto-check passed
  • FAQPage Schema Markup

    thedaviddias/Front-End-Checklist

    Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.

    74k GitHub stars~774 tokensUpdated 5 days ago
    Auto-check passed
  • Favicon Audit and Setup

    thedaviddias/Front-End-Checklist

    Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.

    74k GitHub stars~731 tokensUpdated 5 days ago
    Auto-check passed
  • Content Freshness Signals

    thedaviddias/Front-End-Checklist

    Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.

    74k GitHub stars~741 tokensUpdated 5 days ago
    Auto-check passed
  • Geo Meta Tags Audit

    thedaviddias/Front-End-Checklist

    Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).

    74k GitHub stars~763 tokensUpdated 5 days ago
    Auto-check passed
  • Improve a Front-End Checklist Rule

    thedaviddias/Front-End-Checklist

    Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.

    74k GitHub stars~1.3k tokensUpdated 5 days ago
    Auto-check passed

Questions about Tel Mailto

What does Tel Mailto do?

A skill your agent uses when applies to contact pages, business listing pages, headers/footers, and any page displaying a phone number or email address. Tel Mailto is an agent skill from thedaviddias/Front-End-Checklist. Use when applies to contact pages, business listing pages, headers/footers, and any page displaying a phone number or email address.

When should I use Tel Mailto?

Tel Mailto fits situations like: applies to contact pages; business listing pages; headers/footers; any page displaying a phone number.

How do I install Tel Mailto in Claude Code?

Run `npx skills add thedaviddias/Front-End-Checklist --skill tel-mailto -a claude-code`. Or copy the skill folder (skills/tel-mailto in thedaviddias/Front-End-Checklist) into .claude/skills/tel-mailto in your project. Claude Code loads it when a task matches its description.

How do I install Tel Mailto in Codex?

Run `npx skills add thedaviddias/Front-End-Checklist --skill tel-mailto -a codex`. Or copy the skill folder (skills/tel-mailto in thedaviddias/Front-End-Checklist) into .agents/skills/tel-mailto in your project. Codex loads it when a task matches its description.

Can I use Tel Mailto in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill tel-mailto -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tel-mailto, .gemini/skills/tel-mailto, .github/skills/tel-mailto and .opencode/skills/tel-mailto in your project.

What does Tel Mailto need to run?

SKILL.md names no scripts, command-line tools or credentials: Tel Mailto is instructions for the agent only.

Does Tel Mailto access the network?

SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.

Is Tel Mailto safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Tel Mailto use?

Tel Mailto is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tel Mailto use?

About 549 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Tel Mailto?

Skills that share tags, products or a category with Tel Mailto: Music List (ruvnet/ruflo, 74k stars), Mailtrap Managing Contacts (sickn33/agentic-awesome-skills, 47k stars), Contact Widget (nexu-io/open-design, 100k stars) and Etsy Search Listings (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tel Mailto?

thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.

Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.