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 identifies the basic capability (starting voice calls) and names the specific plugin, but lacks concrete action details, natural trigger terms, and explicit guidance on when to use it. The description would benefit significantly from expansion.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to make a phone call, dial a number, start a voice conversation, or initiate audio communication'
Expand the capability list with specific actions such as 'initiate calls, manage call settings, handle call routing' or whatever the plugin actually supports
Include natural keyword variations users might say: 'phone call', 'dial', 'call someone', 'ring', 'audio call'
| 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). It lacks concrete actions beyond initiating calls. | 1 / 3 |
Completeness | The description answers 'what' minimally (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 | 'Voice calls' is a natural term users might say, but the description misses common variations like 'phone call', 'dial', 'call someone', 'make a call', or 'audio call'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'OpenClaw voice-call plugin' provides some specificity, but 'voice calls' is generic enough to potentially conflict with other communication or telephony 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-organized, respecting token budget while covering multiple providers. However, it lacks concrete tool usage examples and a clear workflow showing the typical call lifecycle (initiate -> interact -> end). The configuration notes are helpful but would benefit from a validation step to verify plugin setup.
Suggestions
Add a concrete tool usage example showing a complete call flow: initiate_call -> speak_to_user -> end_call with actual parameter values
Document what 'mode?' parameter accepts and when to use different modes
Add a brief workflow section showing the typical sequence: 1. Verify plugin enabled, 2. Initiate call, 3. Check status/speak, 4. End call
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what voice calls are or how telephony works. Every line provides actionable configuration or command information. | 3 / 3 |
Actionability | CLI commands are concrete and copy-paste ready, but the tool actions lack executable examples showing actual usage patterns. Parameters like 'to?' and 'mode?' are mentioned but not explained with concrete values or example calls. | 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 the plugin is properly configured before attempting calls, which could lead to silent failures. | 2 / 3 |
Progressive Disclosure | For a simple, focused skill under 50 lines, the structure is appropriate. Clear sections for CLI vs Tool usage, with configuration notes organized by provider. 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
50ef2f3
- 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.