CtrlK
BlogDocsLog inGet started
Tessl Logo

openai-whisper

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

80

0.91x
Quality

75%

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

96%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 lean and highly actionable, with copy-paste-ready commands and no token waste, and its simple single-action workflow is unambiguous. The only gap is minor: section labels ("Quick start", "Notes") are plain text rather than proper markdown headers.

Suggestions

Promote the bare-text labels "Quick start" and "Notes" to proper markdown headers (## Quick start, ## Notes) for clearer navigation and rendering.

DimensionReasoningScore

Conciseness

The body is ~14 lines with zero padding: no explanation of what Whisper is, two direct commands, and a tight notes list — every token earns its place and Claude's competence is assumed, matching the lean-and-efficient anchor.

5 / 5

Actionability

Two copy-paste-ready commands cover the common cases (transcription to txt, translation to srt) with concrete flags, fitting the fully-executable anchor that covers the common cases.

5 / 5

Workflow Clarity

This is a simple single-action skill where the single action (run `whisper` with shown flags) is unambiguous; per the simple-skill exception and no destructive/batch validation cap applying, workflow clarity reaches 5.

5 / 5

Progressive Disclosure

The short, well-split body (Quick start + Notes) is appropriately organized with no external references needed, but the section labels are bare text rather than markdown headers (##), a minor organization gap that holds it just below 5.

4 / 5

Total

19

/

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 clearly states what the skill does and is specific to the Whisper niche, but it lacks an explicit "Use when..." trigger clause and omits natural synonyms like "transcribe" and "audio", which cap completeness and trigger quality at 3.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to transcribe or translate audio files locally without an API key."

Include natural synonyms users actually say — "transcribe", "audio", "subtitles" — alongside "speech-to-text".

Optionally mention the translate task to broaden concrete-action coverage beyond transcription.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("speech-to-text") via the Whisper CLI, but lists no further actions (e.g. translation, diarization), so coverage is not comprehensive — matching the anchor for a clear domain plus 1-2 actions.

3 / 5

Completeness

The "what" is clear ("Local speech-to-text with the Whisper CLI (no API key)"), but there is no "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms ("speech-to-text", "Whisper") but omits common variations a user would say like "transcribe", "audio", or "subtitle", fitting the anchor for some relevant keywords with missing synonyms.

3 / 5

Distinctiveness Conflict Risk

"Whisper CLI" with "Local" and "no API key" carve a clear niche that is unlikely to trigger for unrelated skills, but distinct trigger phrases are absent, leaving it just below the score-5 anchor.

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.

Validation13 / 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.