voice-call

Start voice calls via the Bitterbot voice-call plugin.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/voice-call/SKILL.md

Quality

Content

86%Weight 40%Scale 1-5

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

The body is an efficient, actionable reference: concrete CLI commands, parameterized tool actions, and precise provider config keys with no padding. The only gaps are minor — a tool-invocation example and lifecycle sequencing (initiate → check status → end) are left implicit.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — "Use the voice-call plugin to start or inspect calls (Twilio, Telnyx, Plivo, or mock)" followed by commands, action signatures, and config keys, with no explanation of concepts Claude already knows. Every token earns its place.	5 / 5
Actionability	The CLI block is copy-paste ready with real argument values ("--to \"+15555550123\""), and tool actions list their parameters, but there is no example of an actual voice_call tool invocation and the mode? parameter is never explained. Mostly executable with minor gaps — anchor 4, not 5.	4 / 5
Workflow Clarity	The two entry points (CLI and tool) are clearly separated and each action is unambiguous, but there is no guidance on when to prefer CLI vs tool and no sequencing or status-check feedback for the call lifecycle (initiate → continue → end). Not 5 because checkpoints like checking status after initiating are only implicit; not 3 because the operations are single-shot and non-destructive.	4 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, with well-organized sections (CLI, Tool, Notes) and no bundle files needed — the simple-skill exception applies and the content is appropriately self-contained.	5 / 5
	Total	18 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 names a concrete capability with a clearly identifiable niche, but it is incomplete: it never says when the skill should be used and omits the inspect/status capability and common synonyms like "phone call" or "dial". It sits at the midpoint of the rubric across most dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to make or check a phone/voice call via Bitterbot" — this would raise completeness from 3 to 4-5.

Mention the inspect/status capability ("start or inspect voice calls") so the description covers what the skill actually does.

Include natural synonyms such as "phone call" or "dial" so the description matches how users actually phrase the request.

Dimension	Reasoning	Score
Specificity	"Start voice calls via the Bitterbot voice-call plugin" names the domain and one concrete action (starting calls), but the body shows it also inspects calls — coverage is not comprehensive. It is not a 2 because the action is concrete rather than generic, and not a 4 because only a single action is named.	3 / 5
Completeness	The "what" is clear (start voice calls via the plugin) but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline. It is not a 4 because the "when" is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	"voice calls" and "start" are relevant natural keywords, but common variations like "phone call", "make a call", or "dial" are absent. Matches anchor 3 (some relevant keywords, missing common variations).	3 / 5
Distinctiveness Conflict Risk	"Bitterbot voice-call plugin" carves out a clear niche with distinct triggers, but the generic phrase "voice calls" could overlap with other telephony or calling skills. Mostly distinct with minor overlap risk — anchor 4, not 5.	4 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: Bitterbot-AI/bitterbot-desktop
Path: skills/voice-call/SKILL.md
Commit: 1c7dc1b

Reviewed: 20 hours ago

Table of Contents

Discovery Implementation Validation

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.