CtrlK
BlogDocsLog inGet started
Tessl Logo

voice-call

Start voice calls via the OpenClaw voice-call plugin.

82

1.17x
Quality

Does it follow best practices?

Impact

100%

1.17x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, actionable reference: executable CLI examples, a clear tool action list with parameters, and concrete per-provider configuration notes, all well-organized and free of fluff. It earns top marks as a simple skill that assumes Claude's competence and requires no external file references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — executable CLI commands, a compact action list, and terse config notes with no padding or explanation of concepts Claude already knows. Not a 2 because nothing reads as unnecessary or in need of tightening; every token earns its place.

3 / 3

Actionability

It provides copy-paste-ready CLI commands with real arguments ("--to '+15555550123' --message ..."), a concrete tool action list with parameters, and specific per-provider config keys. Not a 2 because the guidance is executable rather than pseudocode; not below 3 because key details (args, config paths) are present.

3 / 3

Workflow Clarity

This is a simple single-purpose skill (start/inspect a call); the actions are unambiguous and clearly separated into CLI and Tool sections, so per the simple-skills note workflow clarity can score 3. Not a 2 because there is no unclear or missing sequence; the operations are not destructive/batch and thus need no validation checkpoints.

3 / 3

Progressive Disclosure

The body is under 50 lines with no external references needed and is well-organized into clearly labeled ## CLI, ## Tool, and Notes sections, meeting the simple-skills exception for a 3. Not a 2 because content is appropriately inline and well-signaled rather than disorganized; no nested or deep references exist to penalize it.

3 / 3

Total

12

/

12

Passed

Description

50%

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 concise and third-person with a concrete action and a natural keyword, but it states only what the skill does without any "when to use it" trigger and offers just a single action with limited keyword coverage. Adding an explicit "Use when..." clause and broader trigger terms would raise it across all dimensions.

Suggestions

Add an explicit "Use when..." trigger clause, e.g. "Use when the user asks to start or check on a phone/voice call through OpenClaw."

Broaden trigger terms to natural phrasings users actually say, such as "phone call", "make a call", or "call someone".

Name additional concrete actions in the description (e.g. "start, continue, inspect, and end voice calls") to lift specificity and distinctiveness.

DimensionReasoningScore

Specificity

"Start voice calls" names the domain and one concrete action, but does not list multiple specific actions, matching the anchor that names domain and some actions yet is not comprehensive. Not a 1 because the action is concrete rather than vague; not a 3 because only a single action is given.

2 / 3

Completeness

The description clearly states what the skill does ("Start voice calls via the OpenClaw voice-call plugin") but provides no "Use when..." trigger for when to use it, which per the guidelines caps completeness at 2. Not a 1 because the "what" is clearly answered; not a 3 because the "when" is entirely missing rather than explicit.

2 / 3

Trigger Term Quality

"voice calls" is a natural term a user might say, but the description omits common variations like "phone call" or "make a call" and leans on the technical "OpenClaw voice-call plugin." Not a 1 because a real natural keyword is present; not a 3 because coverage of natural terms is thin.

2 / 3

Distinctiveness Conflict Risk

Voice calls via a specific plugin is a recognizable niche, but without explicit distinct triggers it could still overlap with other communication/calling skills. Not a 1 because it is not generic; not a 3 because there are no distinct triggers that would reliably prevent mis-selection.

2 / 3

Total

8

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 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

Total

14

/

16

Passed

Repository
trpc-group/trpc-agent-go
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.