CtrlK
BlogDocsLog inGet started
Tessl Logo

agentphone

Build AI phone agents with AgentPhone API. Use when the user wants to make phone calls, send/receive SMS, manage phone numbers, create voice agents, set up webhooks, or check usage — anything related to telephony, phone numbers, or voice AI.

63

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./skills/agentphone/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%Scale 1-3

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

This skill is highly actionable with excellent executable examples and clear workflow sequencing, but it is massively over-sized for a SKILL.md file. The entire API reference, four complete webhook handler implementations, troubleshooting guide, and use case brainstorming are all inlined, making it a monolithic reference document rather than a concise skill overview with progressive disclosure. The content quality is high but the structure and token efficiency are poor.

Suggestions

Extract the full API Reference section into a separate API_REFERENCE.md file and link to it from the SKILL.md with a one-line summary per resource group (Agents, Numbers, Calls, Messages, Webhooks).

Move the four complete webhook handler examples (streaming Python/Node, tool-calling Python/Node) into a WEBHOOK_EXAMPLES.md file, keeping only one minimal example inline.

Remove the 'Ideas: What You Can Build' section entirely — Claude doesn't need use case brainstorming, and the 'When to Use' section already covers scope.

Remove explanatory prose like 'Here's the full lifecycle', 'These are starting points', and 'Having your own phone number means your agent can do anything a human can do over the phone' — these waste tokens without adding actionable guidance.

DimensionReasoningScore

Conciseness

This skill is extremely verbose at ~800+ lines. It includes extensive API reference documentation, multiple full webhook handler examples in both Python and Node.js, a detailed troubleshooting section, an 'Ideas' section listing use cases Claude doesn't need, and explanatory prose throughout (e.g., 'Here's the full lifecycle', 'These are starting points'). Much of this belongs in separate reference files, not inline. Claude doesn't need to be told what a phone call is or what you can build with a phone number.

1 / 3

Actionability

The skill provides fully executable curl commands for every API endpoint, complete request/response examples with realistic JSON payloads, parameter tables with types and defaults, and full working webhook handler code in Python and Node.js. Everything is copy-paste ready.

3 / 3

Workflow Clarity

The Quick Start provides a clear 5-step sequence (get API key → create agent → buy number → make call → check transcript) with explicit commands and responses at each step. The Rules section includes confirmation requirements before destructive actions (releasing numbers, deleting agents), and the voice call section includes detailed troubleshooting with fix steps. The webhook streaming pattern explicitly includes validation via interim chunks to prevent silence.

3 / 3

Progressive Disclosure

The entire API reference, multiple full webhook handler examples (4 complete implementations), troubleshooting guide, voice capabilities table, webhook event documentation, and use case ideas are all inlined in a single monolithic file. This content should be split across reference files (e.g., API_REFERENCE.md, WEBHOOK_EXAMPLES.md, TROUBLESHOOTING.md) with the SKILL.md serving as a concise overview with pointers. No bundle files exist to offload this content.

1 / 3

Total

8

/

12

Passed

Description

100%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly identifies the specific API (AgentPhone), lists concrete actions, includes an explicit 'Use when' clause with comprehensive trigger terms, and occupies a distinct niche. It follows third-person voice and is concise without being vague.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'make phone calls, send/receive SMS, manage phone numbers, create voice agents, set up webhooks, check usage.' These are clear, actionable capabilities.

3 / 3

Completeness

Clearly answers both what ('Build AI phone agents with AgentPhone API' plus the list of capabilities) and when ('Use when the user wants to make phone calls, send/receive SMS...' with an explicit 'Use when' clause and a catch-all 'anything related to telephony, phone numbers, or voice AI').

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'phone calls', 'SMS', 'phone numbers', 'voice agents', 'webhooks', 'telephony', 'voice AI'. These are terms users would naturally use when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche — telephony, phone agents, and voice AI are specific domains unlikely to overlap with other skills. The mention of 'AgentPhone API' further narrows the scope.

3 / 3

Total

12

/

12

Passed

Validation

72%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 8 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1389 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

8

/

11

Passed

Repository
popey/claude-code-skills
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.