Transcribe audio via OpenAI Audio Transcriptions API (Whisper).
87
—
Does it follow best practices?
Impact
91%
2.27xAverage score across 3 eval scenarios
Passed
No known issues
Transcribe an audio file via OpenAI’s /v1/audio/transcriptions endpoint.
{baseDir}/scripts/transcribe.sh /path/to/audio.m4aDefaults:
whisper-1<input>.txt{baseDir}/scripts/transcribe.sh /path/to/audio.ogg --model whisper-1 --out /tmp/transcript.txt
{baseDir}/scripts/transcribe.sh /path/to/audio.m4a --language en
{baseDir}/scripts/transcribe.sh /path/to/audio.m4a --prompt "Speaker names: Peter, Daniel"
{baseDir}/scripts/transcribe.sh /path/to/audio.m4a --json --out /tmp/transcript.jsonSet OPENAI_API_KEY, or configure it in ~/.openclaw/openclaw.json:
{
skills: {
"openai-whisper-api": {
apiKey: "OPENAI_KEY_HERE",
},
},
}737835b
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.