Use Hail when an assistant or app needs phone numbers in 120+ countries, an email inbox, or inbound and outbound calls, SMS/text messages, and email. Provision numbers, submit carrier registrations, build and route Hail agents, and read conversations and delivery events through MCP or the API.
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Get phone numbers in 120+ countries and an email inbox for your AI assistant. Call, text, and email in both directions. Building an app? Add AI calls, email, and SMS with one API.
This repository contains the official Hail skill for AI assistants and coding agents. It guides an assistant through connecting to Hail, setting up a number or inbox, answering incoming calls, texts, and email, sending messages, and reading conversations and delivery events.
Connect numbers and inboxes to a Hail agent that answers incoming calls, texts, and email. Or use the API and signed webhooks to connect your own assistant or application.
Through MCP, your assistant can:
Purchases and registration submissions need the user's authorization and any required credits. Carrier approval and inventory determine what is available; not every country supports every number type or channel.
You can also connect your own application through signed webhooks. Configure
subscriptions through the REST API or CLI: the current MCP catalog has no
webhook-management tool. Explicit inbox/domain creation uses the console or
REST API; MCP can list identities and work with email. Use route_email_domain
to connect an inbox to an email-enabled Hail agent. Use the default member scope unless the user approves replies to
outside senders.
Read SKILL.md, or get the same instructions at hail.so/skill.md.
For a client that supports Agent Skills:
git clone https://github.com/hail-hq/skills.git hail-skillsInstall hail-skills/skills/hail in your client's skill directory. Follow the
client's instructions for the directory location. Update installed copies when
new versions are published; a local installation is a snapshot.
brew install hail-hq/tap/hail.For REST examples, use an existing HAIL_API_KEY. Create a new account only
when needed. The skill includes optional assistant-led signup and account
recovery instructions. Keep API keys and account claim links out of Git.
Hail uses pay-as-you-go pricing. A new workspace starts at $0 and needs credits before sending. Phone numbers can have setup and recurring charges. Review current pricing before a purchase.
A funded account still needs the right sender setup. SMS may require a dedicated
number and carrier registration. For US 10DLC, the current Hail requirements
and submission interfaces require number_type="local"; it is not an extra
choice to ask the applicant. Preview and amendment tools have different schemas.
Custom email domains need DNS verification.
The skill explains these prerequisites and distinguishes a dedicated incoming
number from a shared outbound call line.
The website's lib/agent-skill-doc.ts generates both this repository's
skills/hail/SKILL.md and the hosted hail.so/skill.md. Maintainers update the
generator, export it into a task worktree of this repository, validate it, and
open linked PRs. Do not edit the generated skill independently.
Review this README and the entire skill when product positioning or platform
behavior changes. The website's publishing runbook and AGENTS.md define the
process. Its PR checks validate API examples; weekly checks compare the deployed
API and the two published copies. Checks detect drift, but people or coding
agents still need to update and review the instructions.
The website serves its local generator. This repository needs no website hosting or Vercel project. GitHub updates do not automatically update an installed skill or prove that a registry has refreshed its listing.
GNU AGPLv3, matching the public Hail project's license.