openai-whisper
Local speech-to-text with the Whisper CLI (no API key).
76
70%
Does it follow best practices?
Impact
91%
0.91xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./openclaw/skills/openai-whisper/SKILL.mdQuality
Discovery
40%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 identifies a clear and distinct niche (local Whisper CLI speech-to-text without an API key), which makes it unlikely to conflict with other skills. However, it is too terse—lacking specific actions the skill can perform and missing a 'Use when...' clause entirely, which significantly hurts completeness and trigger term coverage.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to transcribe audio files locally, generate subtitles, or convert speech to text without an API key.'
Include natural user trigger terms such as 'transcribe', 'audio', 'transcription', '.mp3', '.wav', 'subtitle', and 'voice-to-text'.
List specific concrete actions the skill performs, e.g., 'Transcribes audio files to text, generates SRT/VTT subtitles, supports multiple languages and audio formats.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (speech-to-text) and the tool (Whisper CLI), and notes a constraint (no API key/local), but doesn't list specific concrete actions like transcribing audio files, generating subtitles, converting formats, etc. | 2 / 3 |
Completeness | Provides a brief 'what' (local speech-to-text with Whisper CLI) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is thin enough to warrant a 1. | 1 / 3 |
Trigger Term Quality | Includes 'speech-to-text', 'Whisper', and 'CLI' which are relevant keywords, but misses common user terms like 'transcribe', 'audio', 'transcription', '.mp3', '.wav', 'subtitle', or 'STT'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Whisper CLI', 'local', and 'no API key' creates a very clear niche that is unlikely to conflict with other skills, even other audio or transcription skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, minimal skill that respects Claude's intelligence and the token budget. It provides immediately actionable CLI commands with just enough context (model defaults, cache location) to be useful. The only minor nit is that the markdown headings for 'Quick start' and 'Notes' aren't formatted as actual headings (missing ##), but the content itself is strong.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean — no unnecessary explanations, no description of what Whisper is or how speech-to-text works. Every line adds value. | 3 / 3 |
Actionability | Provides fully executable, copy-paste-ready CLI commands with realistic flags and file paths. The notes section adds practical details (cache location, default model) without fluff. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (run a CLI command). The single action is unambiguous, and no multi-step or destructive workflow is involved, so no validation checkpoints are needed. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into a quick start and notes section. No unnecessary splitting or nesting required. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 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 |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- trpc-group/trpc-agent-go
- Commit
09cce3e
- 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.