voice-call
Start voice calls via the OpenClaw voice-call plugin.
64
Quality
47%
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
22%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. It lacks specific capabilities beyond starting calls, provides no explicit trigger guidance for when Claude should use it, and misses natural language variations users would employ when requesting voice call functionality.
Suggestions
Add a 'Use when...' clause with trigger terms like 'call', 'phone', 'dial', 'make a call', 'voice chat', 'ring'
Expand the capabilities beyond just 'start' - include actions like ending calls, managing call settings, or checking call status if applicable
Include natural language variations users would say: 'phone call', 'call someone', 'dial a number', 'voice conversation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions one vague action 'Start voice calls' without detailing what capabilities exist (e.g., call management, recording, conferencing, etc.). It names a domain but provides no concrete actions beyond initiating calls. | 1 / 3 |
Completeness | The description only weakly addresses 'what' (start voice calls) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains 'voice calls' which is a natural term users might say, but misses common variations like 'phone call', 'dial', 'call someone', 'make a call', or 'audio call'. The plugin name 'OpenClaw' is technical jargon users wouldn't naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'OpenClaw voice-call plugin' provides some specificity that distinguishes it from generic communication skills, but 'voice calls' alone could overlap with other telephony or communication skills. | 2 / 3 |
Total | 6 / 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 concise and well-structured, respecting token efficiency while covering CLI and tool interfaces. However, it lacks concrete usage examples for the tool actions and doesn't provide a clear workflow for multi-step call operations (initiate, speak, end). Adding one complete example and a basic workflow sequence would significantly improve actionability.
Suggestions
Add a concrete tool usage example showing a complete call flow: initiate_call -> speak_to_user -> end_call with actual parameter values
Include a brief workflow sequence showing the typical order of operations for making a call
Add an example configuration snippet for at least one provider (e.g., Twilio) to make setup more actionable
| Dimension | Reasoning | Score |
|---|---|---|
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 example configurations. | 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 handling failures. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (CLI, Tool, Notes). No need for external references 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
8763418
- 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.