CtrlK
BlogDocsLog inGet started
Tessl Logo

telephony

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

63

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

88%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 content is highly actionable with executable commands for every workflow, a clear decision tree, and explicit safety/verification checkpoints appropriate to a cost-incurring telephony skill. Minor tightening of rationale prose and splitting per-command reference detail would lift the two 4-scored dimensions.

DimensionReasoningScore

Conciseness

The body is action-oriented and largely tight command blocks with minimal concept-over-explanation, though a few rationale/decision-tree prose blocks ('Why:' lists, the TTS note) could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready 'python "$SCRIPT" ...' commands for every common case, all verified to map to real subcommands in scripts/telephony.py (save-twilio, twilio-buy, twilio-call, ai-call, etc.).

5 / 5

Workflow Clarity

Clear decision tree followed by a 'diagnose first' checkpoint, numbered workflows A-H, an explicit 'Confirm with the user before dialing or texting' safety checkpoint for the destructive/cost-incurring operations, and a verification checklist.

5 / 5

Progressive Disclosure

Well-organized into clear sections with the single helper script explicitly located and referenced one level deep; no nested references. The per-command detail bulk is inlined rather than split into a reference file, leaving minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

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

The description is specific and clearly distinguishable, but it lacks an explicit 'when to use' trigger clause and could include more natural synonyms users would actually say. Adding a 'Use when...' clause and terms like 'texts' or 'phone calls' would raise the weaker dimensions.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when sending texts or making outbound phone calls, provisioning a Twilio number, or polling inbound SMS.'

Include natural synonyms users would say, such as 'texts', 'texting', 'phone calls', and 'calling', alongside 'SMS/MMS'.

Reframe the capability list as concrete verbs (e.g. 'Buy, send, and poll texts; place AI and direct Twilio calls') to lift specificity above a domain-only listing.

DimensionReasoningScore

Specificity

Names the telephony domain and three concrete capability areas ('Provision Twilio numbers, SMS/MMS, and AI outbound calls'), but these are categories rather than enumerated action verbs, and coverage is not comprehensive.

3 / 5

Completeness

Clearly states 'what' the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes solid natural keywords ('Twilio', 'SMS', 'MMS', 'AI outbound calls', 'numbers') a user might say, though common synonyms like 'texts', 'texting', 'phone calls', or '2FA/OTP' are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear, niche telephony domain (Twilio numbers, SMS/MMS, AI outbound calls) with distinct triggers and minimal overlap with related skills like maps or agentmail.

5 / 5

Total

15

/

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.

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
NousResearch/hermes-agent
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.