CtrlK
BlogDocsLog inGet started
Tessl Logo

phone

Verify phone numbers (carrier + SIM-swap fraud signals) and place AI-powered outbound voice calls via BlockRun's gateway (Twilio + Bland.ai). Trigger when the user asks to look up a number, check fraud risk, buy/rent a phone number, or place an AI voice call. Payment is automatic via x402 from the wallet.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-3

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

The body is highly actionable and token-efficient with clear, validated workflows for risky operations like outbound calls and fraud checks. Its main weakness is progressive disclosure: all reference material lives inline in one file rather than being split into clearly signaled one-level-deep reference files.

Suggestions

Split the per-endpoint reference (request/response shapes, parameter tables, auto-pick rules) into a reference file such as API.md and keep SKILL.md as a concise overview with one-level-deep links, e.g. "Full API: See [API.md](API.md)".

Move the three Example Agentic Flows into an examples reference file, leaving a single representative flow inline plus a pointer, to shorten the main file.

Extract the Notes section into the reference file or fold each note into the relevant endpoint section so the overview stays lean.

DimensionReasoningScore

Conciseness

The body is dense reference material — endpoints with prices, JSON request bodies, parameter tables, and tool names — with no padding explaining concepts Claude already knows. The illustrative dates in the CLI sample output demonstrate the renew-soon warning format rather than stating stale facts, so they do not trigger the time-sensitivity penalty. It is not level 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

Every operation gives an executable HTTP endpoint, a concrete JSON body, CLI commands, and LLM-callable tool names, plus a parameter table with defaults — copy-paste ready. It is not level 2 because the guidance is complete and executable rather than pseudocode or missing key details.

3 / 3

Workflow Clarity

Sequences carry explicit validation: the fraud flow checks "sim_swap.last_sim_swap within the past 7 days" then refuses, and the voice flow gates on an explicit user request, handles 403/400/402 with retry guidance, then polls status until completed before summarizing. It is not level 2 because checkpoints and error-recovery feedback loops are present rather than implicit.

3 / 3

Progressive Disclosure

The skill is a monolithic ~180-line single file containing the full per-endpoint API reference, parameter tables, and agentic flows inline, with no references to separate detailed materials. It is not level 3 because nothing is split out into one-level-deep references and SKILL.md is the complete reference rather than an overview; it is above level 1 because sections are well-organized with easy header navigation and no nested indirection.

2 / 3

Total

11

/

12

Passed

Description

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

The description is specific, trigger-rich, and clearly bounded, explicitly stating both capabilities and when to invoke the skill in third-person voice. It is a strong, low-conflict description that hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Verify phone numbers (carrier + SIM-swap fraud signals)", "buy/rent a phone number", and "place AI-powered outbound voice calls" — matching the level-3 anchor for multiple specific concrete actions. It is not level 2 because the actions are comprehensive and specific rather than naming only a domain and a few actions.

3 / 3

Completeness

Clearly answers both what (verify/fraud/buy-rent/place call) and when via an explicit "Trigger when the user asks to..." clause. It is not level 2 because the when is explicit rather than only implied.

3 / 3

Trigger Term Quality

Natural trigger phrasing — "look up a number", "check fraud risk", "buy/rent a phone number", "place an AI voice call" — is reinforced by a frontmatter trigger list ("phone number lookup", "sim swap", "outbound call", "bland.ai"). Good coverage of terms users would actually say, exceeding the level-2 single-phrase anchor.

3 / 3

Distinctiveness Conflict Risk

A clear niche — phone intelligence and AI voice calls via BlockRun/Twilio/Bland.ai — with distinct triggers unlikely to fire for unrelated skills. Voice is third person ("Verify...", "place...") with no first/second person, so no specificity penalty applies.

3 / 3

Total

12

/

12

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

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

Total

13

/

16

Passed

Repository
BlockRunAI/ClawRouter
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.