CtrlK
BlogDocsLog inGet started
Tessl Logo

voice-call

Start voice calls via the OpenClaw voice-call plugin.

Install with Tessl CLI

npx tessl i github:Hung-Reo/hungreo-openclaw --skill voice-call
What are skills?

60

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

Discovery

32%

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 description is too minimal to effectively guide skill selection. While it identifies the core capability (starting voice calls via a specific plugin), it lacks explicit trigger guidance, comprehensive action coverage, and natural user language variations. The absence of a 'Use when...' clause significantly limits its utility for skill selection.

Suggestions

Add a 'Use when...' clause with trigger terms like 'call', 'phone', 'dial', 'ring someone', 'make a call', 'start a call'

Expand the action list to include other voice call operations if supported (e.g., 'Start, manage, and end voice calls')

Include natural language variations users might say: 'voice call', 'phone call', 'call someone', 'dial a number'

DimensionReasoningScore

Specificity

Names the domain (voice calls) and one action (start), but lacks comprehensive actions like end calls, transfer, mute, or other voice call operations.

2 / 3

Completeness

Describes what it does (start voice calls) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.

1 / 3

Trigger Term Quality

Includes 'voice calls' and 'voice-call' which are relevant, but misses common variations users might say like 'phone call', 'call someone', 'dial', 'ring', or 'make a call'.

2 / 3

Distinctiveness Conflict Risk

The OpenClaw plugin reference adds some distinctiveness, but 'voice calls' is somewhat generic and could overlap with other communication or telephony skills.

2 / 3

Total

7

/

12

Passed

Implementation

72%

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

This skill is admirably concise and well-organized, respecting Claude's intelligence by not over-explaining voice call concepts. However, it would benefit from concrete tool usage examples showing actual parameter values and a clearer workflow sequence for multi-step call operations (initiate, speak, end).

Suggestions

Add a concrete tool usage example showing a complete call flow: initiate_call with actual parameters, then speak_to_user, then end_call

Include a brief workflow sequence showing the typical call lifecycle and how to check status between actions

DimensionReasoningScore

Conciseness

Extremely lean and efficient. No unnecessary explanations of what voice calls are or how Twilio works. Every line provides actionable configuration or command information.

3 / 3

Actionability

CLI commands are copy-paste ready, but the tool actions lack concrete examples showing actual usage with parameters. The config notes describe what's needed but don't show executable examples.

2 / 3

Workflow Clarity

Actions are listed but there's no clear workflow showing the sequence (initiate -> speak -> end). No validation steps for checking if calls succeeded or error handling guidance.

2 / 3

Progressive Disclosure

For a simple, focused skill under 50 lines, the structure is appropriate. Clear sections for CLI vs Tool usage, with config notes organized as bullet points. No need for external references.

3 / 3

Total

10

/

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

9

/

11

Passed

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.