openai-whisper-api
Transcribe audio via OpenAI Audio Transcriptions API (Whisper).
76
70%
Does it follow best practices?
Impact
91%
2.27xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./openclaw/skills/openai-whisper-api/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 clearly identifies a specific technology (OpenAI Whisper API) and a distinct task (audio transcription), giving it good distinctiveness. However, it is too terse—it lacks a 'Use when...' clause, lists only one action, and misses common user-facing trigger terms like 'speech-to-text' or audio file extensions.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to transcribe audio files, convert speech to text, or mentions Whisper, .mp3, .wav, or voice recordings.'
Include additional natural trigger terms users might say, such as 'speech-to-text', 'convert audio to text', 'voice recording', '.mp3', '.wav', '.m4a'.
List more specific capabilities if applicable, such as 'supports multiple audio formats, language detection, and timestamp generation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (audio transcription) and the specific tool (OpenAI Audio Transcriptions API / Whisper), but only describes a single action ('transcribe audio') without listing additional concrete capabilities like format handling, timestamp extraction, or language detection. | 2 / 3 |
Completeness | Describes what it does (transcribe audio via Whisper) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and since the 'what' is also minimal, a score of 1 is appropriate. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'transcribe', 'audio', 'OpenAI', and 'Whisper', but misses common user variations such as 'speech-to-text', 'convert audio to text', 'voice recording', or file extensions like '.mp3', '.wav'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to a specific niche—audio transcription via the OpenAI Whisper API—which is unlikely to conflict with other skills. The mention of the specific API and technology makes it highly distinguishable. | 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, concise skill that does exactly what it needs to. It provides immediately actionable commands, covers common use cases with flag examples, and includes API key configuration—all without a single wasted token. The structure is clean and appropriate for the skill's simplicity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose. No unnecessary explanations of what Whisper is, what audio transcription means, or how APIs work. Lean and efficient. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands with real flags and file paths. Multiple usage examples cover common scenarios (language, prompt, JSON output, custom output path). | 3 / 3 |
Workflow Clarity | This is a simple single-task skill (run a script to transcribe audio). The single action is unambiguous with clear defaults stated and flag variations shown. No multi-step or destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a single purpose, the content is well-organized into logical sections (quick start, flags, API key config) without needing external references. Clear and easy to navigate. | 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
af8bd5f
- 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.