Transcribe audio via OpenAI Audio Transcriptions API (Whisper).
Install with Tessl CLI
npx tessl i github:qsimeon/openclaw-engaging --skill openai-whisper-api76
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 91%
↑ 2.27xAgent success when using this skill
Validation for skill structure
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 its specific purpose (audio transcription via Whisper API) and has low conflict risk due to its focused scope. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user keywords and additional capability details.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user wants to convert audio to text, transcribe recordings, or mentions speech-to-text'
Include common user terms and file extensions: 'speech-to-text', 'voice recording', '.mp3', '.wav', '.m4a'
Expand capabilities if applicable: mention supported formats, language detection, or timestamp options
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (audio transcription) and the specific tool (OpenAI Audio Transcriptions API/Whisper), but only describes one action ('transcribe audio') without listing additional capabilities like format options, language detection, or timestamp generation. | 2 / 3 |
Completeness | Answers 'what' (transcribe audio via Whisper API) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'transcribe', 'audio', 'OpenAI', and 'Whisper', but misses common user variations like 'speech-to-text', 'convert audio to text', 'voice recording', or file extensions like '.mp3', '.wav'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on audio transcription via a named API (OpenAI/Whisper), making it unlikely to conflict with other skills like general audio processing or text-to-speech. | 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, well-crafted skill that exemplifies token efficiency and actionability. It provides everything needed to use the Whisper API transcription script without any unnecessary explanation, with clear examples covering the most common use cases.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Whisper is or how audio transcription works. Every line provides actionable information. | 3 / 3 |
Actionability | Provides copy-paste ready commands with concrete examples covering common use cases (different formats, languages, prompts, JSON output). The script path and flag syntax are explicit. | 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. No multi-step process requiring validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (quick start, flags, API key configuration). Clear and navigable. | 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 | |
Table of Contents
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.