CtrlK
BlogDocsLog inGet started
Tessl Logo

phone-calls

Make AI phone calls, buy phone numbers, and get call transcripts via x402. USE FOR: - Making AI-powered outbound phone calls - Scheduling calls and getting transcripts - Buying and managing phone numbers - Leaving voicemails - Transferring calls to humans - Checking if a number has iMessage/FaceTime TRIGGERS: - "call", "phone call", "make a call", "dial" - "buy number", "phone number", "get a number" - "voicemail", "leave a message" - "transcript", "call recording", "call summary" - "AI call", "automated call", "bland" - "imessage", "facetime", "check number", "lookup number" ALWAYS use agentcash.fetch for stablephone.dev endpoints. IMPORTANT: Use exact endpoint paths from the Quick Reference table below.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

A highly actionable, well-structured API skill body with executable examples and clear polling-based workflows. Its main weaknesses are minor code repetition in Workflows, missing error-recovery feedback loops, and a dangling reference to a non-existent rules/getting-started.md with no actual content split across files.

Suggestions

Replace the re-pasted agentcash.fetch blocks in the Workflows section with brief references to the endpoint sections above (e.g., 'Make a call as shown in Make a Call') to remove the conciseness-dragging repetition.

Add an explicit error-recovery checkpoint to the call and lookup workflows (e.g., what to do if status never reaches completed/complete within max_duration, or if the lookup token expires before status is complete).

Either create the referenced rules/getting-started.md or remove the dangling Setup link, and consider splitting the Voice Options table, full response-field schemas, and Cost Estimation into a separate reference file to reduce SKILL.md length and give real progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly lean — tables, executable code blocks, and tight parameter lists with no over-explanation of known concepts — but the Workflows section re-pastes agentcash.fetch call blocks already shown in the main endpoint sections, which is minor repetition that could be trimmed. Not 5 because not every token earns its place; not 3 because there is no unnecessary concept explanation.

4 / 5

Actionability

Fully executable agentcash.fetch calls with concrete URLs, methods, and bodies; parameter docs specify exact constraints (E.164 format, max_duration 1-30, enum values, defaults); response fields are documented; examples cover common cases (call, voicemail, transfer, buy number, lookup). Matches the copy-paste-ready score-5 anchor.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (make call -> poll until completed; two-step async lookup -> poll until complete) with polling intervals and a DNC guardrail, matching the score-4 anchor of clear sequence with most checkpoints. Not 5 because error-recovery feedback loops (failed calls, token expiry handling) are not made explicit; this is a single-operation skill so the destructive/batch 3-cap does not apply.

4 / 5

Progressive Disclosure

Section structure and the Quick Reference table give reasonable navigation, but the only external reference (rules/getting-started.md in the Setup section) is a dangling path absent from the bundle, and all API reference detail (voice options, full response schemas, cost estimation) is inlined in a ~265-line SKILL.md with no content split into separate files. Fits the score-3 anchor of content that should be separate being inline; not 4 because of the broken reference and absence of real file splitting.

3 / 5

Total

16

/

20

Passed

Description

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

A well-crafted description that concisely states capabilities in third person, provides comprehensive natural trigger phrases, and clearly answers both 'what' and 'when'. No weaknesses across any dimension.

DimensionReasoningScore

Specificity

The summary 'Make AI phone calls, buy phone numbers, and get call transcripts' plus a 6-item USE FOR list (outbound calls, transcripts, buying/managing numbers, voicemails, transfers, iMessage/FaceTime checks) names multiple concrete actions with comprehensive coverage, matching the score-5 anchor; it is not 4 because there are no minor coverage gaps.

5 / 5

Completeness

It explicitly states what the skill does (summary sentence) and when to use it (USE FOR + TRIGGERS with concrete trigger phrases), matching the score-5 anchor for clearly answering both what and when.

5 / 5

Trigger Term Quality

The TRIGGERS list covers natural phrases and synonyms users would say ('call', 'phone call', 'make a call', 'dial', 'voicemail', 'leave a message', 'transcript', 'call recording', 'AI call', 'bland', 'imessage', 'facetime', 'lookup number'), matching the comprehensive-coverage score-5 anchor; not 4 because no common variations are missing.

5 / 5

Distinctiveness Conflict Risk

The AI-phone-calls-via-StablePhone/x402 niche with distinct triggers (phone calls, voicemail, number buying, iMessage/FaceTime lookup) is clearly distinguishable with minimal overlap risk, matching the score-5 anchor.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
Merit-Systems/agentcash-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.