CtrlK
BlogDocsLog inGet started
Tessl Logo

openai-whisper

Local speech-to-text with the Whisper CLI (no API key).

81

0.91x
Quality

76%

Does it follow best practices?

Impact

91%

0.91x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/openai-whisper/SKILL.md

The canonical home for this skill is openai-whisper in openclaw/openclaw

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 exemplary minimal skill: two executable commands covering the core cases, plus only the non-obvious install-specific facts Claude couldn't infer. It fully exploits the rubric's simple-skill exceptions for workflow clarity and progressive disclosure. No changes needed.

DimensionReasoningScore

Conciseness

The ~10-line body contains only a runnable command pair and install-specific facts ("Models download to ~/.cache/whisper on first run", "--model defaults to turbo on this install") that Claude could not know. Every token earns its place with zero padding or explanation of known concepts.

5 / 5

Actionability

Two copy-paste-ready commands ("whisper /path/audio.mp3 --model medium --output_format txt --output_dir ." and "whisper /path/audio.m4a --task translate --output_format srt") are fully executable and cover the two common cases, transcription and translation, with explicit flags.

5 / 5

Workflow Clarity

This is a simple single-purpose skill where the single action is unambiguous, so the rubric's simple-skill exception applies. Transcription is neither destructive nor a batch operation, so no validation checkpoint is required.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and the 'Quick start' / 'Notes' sections are well organized. No references or scripts exist in the bundle, so nothing is dangling or over-inlined.

5 / 5

Total

20

/

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 states a clear, honest 'what' with a distinctive local/no-API-key angle, but it omits any 'when to use' trigger guidance and most of the natural vocabulary (transcribe, transcription, subtitles, audio formats) users would actually say. Adding a Use-when clause and a couple of concrete capabilities would move it from adequate to strong.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to transcribe or translate an audio/video file locally, mentions Whisper, or wants subtitles (srt/vtt) from a recording."

Name the concrete capabilities so the 'what' is comprehensive: transcribing audio to text, translating speech to English, and outputting txt/srt/vtt/json formats.

Include natural synonyms and file formats users would mention — "transcribe", "transcription", "audio", ".mp3", ".m4a", "subtitles" — to improve trigger routing.

DimensionReasoningScore

Specificity

"Local speech-to-text" names the domain and one implicit action, and "(no API key)" adds a useful constraint, but there are no concrete action verbs like transcribe, translate, or generate subtitles. It sits just above 'names the domain but actions are minimal' and below 'several specific actions'.

3 / 5

Completeness

The 'what' is clear (local speech-to-text via the Whisper CLI), but there is no 'Use when...' clause or equivalent trigger guidance. Per the rubric guideline, a missing 'when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

"speech-to-text" and "Whisper" are natural terms users would say, but the common phrasings users actually use — "transcribe", "transcription", "audio", "subtitles", file extensions like .mp3 — are missing. This matches 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

"Whisper CLI (no API key)" carves a fairly distinct local-transcription niche with minimal overlap risk against other skills. Not 5 because without trigger phrases, a generic 'transcribe this audio' request would not reliably route to this skill over similar ones.

4 / 5

Total

13

/

20

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 — 13 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

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.