← ClaudeAtlas

oatda-transcribe-audiolisted

Use when the user wants to transcribe audio to text using OATDA's unified audio API. Supports speech-to-text (STT), meetings, podcasts, voice notes, Whisper-style transcription, and the transcribe_audio MCP capability.
devcsde/oatda-skills · ★ 0 · AI & Automation · score 70
Install: claude install-skill devcsde/oatda-skills
# OATDA Audio Transcription Transcribe audio files to text through OATDA's unified audio API. ## When to Use Use this skill when the user wants to: - Transcribe meetings, podcasts, interviews, or voice notes - Convert speech audio to written text - Create subtitles or timestamped transcripts - Use Whisper-style speech-to-text models through OATDA - Use the OATDA `transcribe_audio` capability ## Prerequisites The user needs an OATDA API key. Check in this order: 1. `$OATDA_API_KEY` environment variable 2. `~/.oatda/credentials.json` config file If neither exists, tell the user: > You need an OATDA API key. Get one at https://oatda.com, then set it: > `export OATDA_API_KEY=your_key_here` ## Step-by-Step Instructions ### 1. Resolve the API key ```bash # Check env var first; if empty, auto-load from credentials file if [[ -z "$OATDA_API_KEY" ]]; then export OATDA_API_KEY=$(cat ~/.oatda/credentials.json 2>/dev/null | jq -r '.profiles[.defaultProfile].apiKey' 2>/dev/null) fi # Verify key exists (show first 8 chars only) echo "${OATDA_API_KEY:0:8}" ``` If the output is empty or `null`, stop and ask the user to configure their API key. **IMPORTANT**: - Never print the full API key. Only show the first 8 characters for verification. - The key resolution script and subsequent `curl` commands **must run in the same shell session**. Each separate bash/terminal invocation starts with an isolated environment where previously exported variables are lost. Either run all command