CtrlK
BlogDocsLog inGet started
Tessl Logo

voice-call

Start voice calls via the Bitterbot voice-call plugin.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/voice-call/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%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, fully executable reference with excellent conciseness, actionability, and organization. Its only notable gap is the absence of a sequenced workflow with a verification step for a consequential external action.

Suggestions

Add a short sequenced workflow that pairs initiate_call with get_status so Claude verifies the call connected before proceeding.

Include a pre-flight check reminding Claude to confirm the recipient number (and consent) before placing an outbound call to a real person, since this is a hard-to-reverse external action.

DimensionReasoningScore

Conciseness

The body is lean reference material with no concept over-explanation; the CLI examples, action list, and provider-config notes each earn their tokens and assume Claude's competence.

5 / 5

Actionability

The CLI block gives copy-paste-ready commands with concrete example values, the Tool section lists each action with its parameter signature, and the Notes give exact config keys per provider.

5 / 5

Workflow Clarity

The content is organized as reference rather than a sequenced workflow, and it lacks any verification checkpoint (e.g., call get_status after initiate_call, or confirm the recipient number) for the consequential, outward-facing act of placing a real outbound call, capping the score at 3.

3 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external bundle files, and is organized into clearly-labeled CLI, Tool, and Notes sections, satisfying the simple-skill exception for progressive disclosure.

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 specific plugin and concrete action, but it omits any explicit trigger guidance and offers only a single action with no synonyms. It is distinct yet incomplete on the when-to-use axis.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user asks to place, check on, or end a voice/phone call') to lift completeness above the 3 cap.

Expand specificity by listing the concrete operations the skill supports (start, inspect/continue, end, and check status of calls) rather than only 'Start voice calls'.

Add natural trigger synonyms such as 'phone call', 'dial', or 'outbound call' so the description surfaces for the phrasings users actually say.

DimensionReasoningScore

Specificity

"Start voice calls via the Bitterbot voice-call plugin" names one concrete action ("Start voice calls") and the specific tool, fitting the 1-2 concrete actions anchor without being comprehensive.

3 / 5

Completeness

A clear "what" is present (start voice calls via the plugin) but there is no "Use when..." trigger clause, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

"voice calls" / "voice-call" are natural terms a user would say, but the description lacks common synonyms like "phone call", "dial", or "outbound call", matching the some-keywords-missing-variations anchor.

3 / 5

Distinctiveness Conflict Risk

Naming the specific "Bitterbot voice-call plugin" plus the narrow voice-call function gives a clear niche with only minor overlap risk, fitting the mostly-distinct anchor rather than the fully-explicit 5.

4 / 5

Total

13

/

20

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
Bitterbot-AI/bitterbot-desktop
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.