openai-whisper-api

Transcribe audio via OpenAI Audio Transcriptions API (Whisper).

2.27x

Quality

75%

Does it follow best practices?

Impact

91%

2.27x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

The canonical home for this skill is openai-whisper-api in Hung-Reo/hungreo-openclaw

Quality

Content

93%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 content is an exemplar of a lean, single-purpose skill: concise, fully executable, and well-structured with a real referenced script. The only minor gap is the lack of an explicit post-run verification or error-handling note for the transcription output.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it jumps straight to a quick-start command, flag examples, and API-key setup with no padding or explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.	5 / 5
Actionability	It provides fully executable, copy-paste-ready commands referencing a real script (scripts/transcribe.sh, verified present and runnable) with concrete flag examples covering the common cases, matching the 'fully executable; specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	The single action (run the script with an audio file) is unambiguous and well-sequenced via flags, but the body offers no explicit verification that transcription succeeded or error-recovery guidance, leaving a minor checkpoint gap just below the top anchor.	4 / 5
Progressive Disclosure	The skill is under 50 lines with well-organized sections (Quick start, Useful flags, API key) and a single one-level-deep bundle reference (scripts/transcribe.sh) that is real and clearly signaled, satisfying the simple-skill exception for the top anchor.	5 / 5
	Total	19 / 20 Passed

Description

57%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 is specific and highly distinct, pinpointing the OpenAI Whisper transcription API with minimal conflict risk. Its main weakness is the absence of any explicit 'when to use' trigger guidance, which caps completeness and limits natural trigger-term coverage.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user wants to transcribe audio, convert speech to text, or mentions Whisper / speech-to-text.'

Add common synonyms and file extensions to broaden trigger-term coverage (e.g. 'speech-to-text', '.mp3', '.m4a', '.wav').

Optionally mention a second concrete capability (e.g. optional language hint or prompt-based speaker naming) to lift specificity beyond a single action.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action ("Transcribe audio via OpenAI Audio Transcriptions API") but offers only a single capability rather than comprehensive coverage, matching the anchor for '1-2 concrete actions, but not comprehensive'.	3 / 5
Completeness	It clearly answers 'what' (transcribe audio via the OpenAI API) but provides no 'when' / 'Use when...' trigger guidance, so per the rubric guideline a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	It includes relevant natural terms ("transcribe audio", "Whisper") but omits common synonyms and variations users might say, such as "speech-to-text" or audio file extensions, fitting the anchor for 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific "OpenAI Audio Transcriptions API (Whisper)" carves out a clear, distinct niche with minimal overlap risk against other skills, matching the anchor for 'clear niche with distinct triggers; minimal conflict risk'.	5 / 5
	Total	14 / 20 Passed

Validation

81%

Warnings & errors only

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

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	13 / 16 Passed

Repository: trpc-group/trpc-agent-go
Path: openclaw/skills/openai-whisper-api/SKILL.md
Commit: ba4a78e

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.