CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

telephony

Provision Twilio numbers, SMS/MMS, and AI outbound calls.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/productivity/telephony/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body delivers excellent, fully executable command guidance with clear workflow sequencing, verification checkpoints, and a sensible provider decision tree. Its weaknesses are inlined detail that belongs in reference files (SKILL.md should be an overview) and duplicated content across the intro, "What this solves", and workflow sections.

Suggestions

Move the per-command cookbook (workflows A-H and provider setup detail) into a reference file such as references/workflows.md, keeping SKILL.md as an overview with well-signaled one-level-deep links.

Cut duplication: drop or merge the intro capability bullet list and "What this solves" into the decision tree, and have workflow A reference the provider-setup commands instead of repeating them verbatim.

Replace the masked "+155****0000" example in workflow E with a valid E.164 placeholder like "+15551230000" so the command is copy-paste ready, and add a brief fix-and-retry note for common failures (e.g. twilio-buy rejected on a trial account).

DimensionReasoningScore

Conciseness

The body is command-focused with no concept-teaching padding, but contains real duplication: the intro capability bullet list and "What this solves" both preview the decision tree, workflow A repeats provider-setup commands verbatim, and section E lists hosting options twice — matching anchor 3 ("mostly efficient but could be tightened") rather than anchor 2, since nothing explains things Claude already knows.

3 / 5

Actionability

Every workflow ships copy-paste-ready commands with realistic placeholders — e.g. `python "$SCRIPT" twilio-buy "+17025551234" --save-env`, `twilio-send-sms ... --media-url`, and a fully specified `ai-call` prompt with provider, voice, and max-duration flags — covering the common cases, matching anchor 5 (only blemish: the masked "+155****0000" in workflow E).

5 / 5

Workflow Clarity

Sequences are clear (7-step agent procedure, numbered workflows A-H, decision tree for provider routing) with explicit checkpoints — "If SCRIPT is empty, the skill is not installed yet", `diagnose` before resuming, a 7-item verification checklist, and mandatory pre-dial/text confirmation — but fix-and-retry loops for API failures are only hinted at in "Pitfalls", matching anchor 4 rather than anchor 5's explicit error-recovery feedback loops.

4 / 5

Progressive Disclosure

Section headers make the 400-line body navigable and the sole bundle file (scripts/telephony.py) is referenced correctly and exists, but all detail is inlined — 200+ lines of per-command cookbook and provider setup that belongs in a separate reference file sit directly in SKILL.md, matching anchor 3 ("content that should be separate is inline") rather than anchor 4.

3 / 5

Total

15

/

20

Passed

Description

70%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 concise, distinct description with good specificity and strong trigger keywords, but it omits any explicit "Use when..." trigger guidance, capping its completeness at the anchor-3 level. Adding a when-to-use clause and natural synonyms like "text" or "phone call" would raise it to top-tier quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to send texts, make phone calls, or buy and manage an agent-owned phone number."

Include natural synonyms such as "text", "texting", "phone calls", and "phone number" so users phrasing requests conversationally still match the skill.

Mention inbound SMS polling (e.g. "check texts received later") to round out capability coverage beyond provisioning and outbound actions.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "Provision Twilio numbers", "SMS/MMS", "AI outbound calls" — going beyond 1-2 actions, but coverage has gaps (no inbound SMS polling, direct TwiML calls, or IVR digit navigation), matching anchor 4 rather than the comprehensive anchor 5.

4 / 5

Completeness

The "what" is clear ("Provision Twilio numbers, SMS/MMS, and AI outbound calls") but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3; it cannot score 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Terms "Twilio", "SMS", "MMS", and "AI outbound calls" give good natural keyword coverage including the provider name, but common synonyms like "text", "texting", "phone number", and "voice call" are missing, which fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Twilio numbers", "SMS/MMS", and "AI outbound calls" define a clear telephony niche with provider-specific triggers and minimal overlap risk with other skills, matching anchor 5 exactly.

5 / 5

Total

16

/

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_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

NousResearch/hermes-agent

Path

optional-skills/productivity/telephony/SKILL.md

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.