voice-call
Start voice calls via the OpenClaw voice-call plugin.
70
56%
Does it follow best practices?
Impact
100%
1.17xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./openclaw/skills/voice-call/SKILL.mdQuality
Discovery
40%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 very brief and identifies a narrow, distinctive capability (starting voice calls via a specific plugin), which helps with distinctiveness. However, it lacks a 'Use when...' clause, provides only a single action, and misses common user trigger terms like 'phone call', 'dial', or 'call someone', significantly weakening its utility for skill selection.
Suggestions
Add a 'Use when...' clause with natural trigger phrases such as 'Use when the user asks to make a call, phone someone, dial a number, or start a voice conversation'.
Expand the capability description to include additional actions if applicable, e.g., 'Start, manage, or end voice calls' or mention supported features like conference calls, call transfers, etc.
Include common user-facing synonyms and variations like 'phone call', 'dial', 'ring', 'call someone' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (voice calls) and one action (start), but does not list multiple concrete actions or elaborate on capabilities beyond initiating calls. | 2 / 3 |
Completeness | Describes what it does (start voice calls) but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also quite thin, bringing this to a 1. | 1 / 3 |
Trigger Term Quality | Includes 'voice calls' and 'voice-call' which are relevant keywords, but misses common variations users might say like 'phone call', 'call someone', 'dial', or 'make a call'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'OpenClaw voice-call plugin' is highly specific and distinctive, making it very unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 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 is a lean, well-structured skill that efficiently communicates how to use the voice-call plugin. Its main weaknesses are the lack of concrete tool invocation examples (only parameter signatures are listed) and the absence of an explicit workflow sequence or error-handling guidance for the multi-step call lifecycle.
Suggestions
Add a concrete tool invocation example showing a full initiate_call → get_status → end_call sequence with actual parameter values.
Document what values 'mode' accepts and what 'to' defaults to when omitted.
Add a brief workflow note: 'After initiate_call, check get_status to confirm connection before proceeding with speak_to_user or continue_call.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose—no explanation of what voice calls are, no unnecessary context about Twilio/Telnyx/Plivo. The config notes are terse but informative, listing only what's needed. | 3 / 3 |
Actionability | The CLI examples are concrete and copy-paste ready, but the tool actions only list parameter names without showing actual tool invocation examples (e.g., a JSON call or code snippet). Key details like what 'mode' accepts or what 'to' defaults to are missing. | 2 / 3 |
Workflow Clarity | The actions imply a workflow (initiate → continue/speak → end), but the sequence is not explicitly stated. There's no validation checkpoint—e.g., checking status after initiating, or handling failure cases when a call doesn't connect. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized into clear sections (CLI, Tool, Notes) without unnecessary nesting or monolithic blocks. No external references are needed given the scope. | 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- trpc-group/trpc-agent-go
- Commit
09cce3e
- 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.