Transcribe audio files via OpenRouter using audio-capable models

Transcribe audio files via OpenRouter using audio-capable models (Gemini, GPT-4o-audio, etc).

This skill appears to do what it says (convert audio and call OpenRouter), but there are documentation/metadata inconsistencies you should resolve before use. Specifically: (1) the script requires OPENROUTER_API_KEY — ensure the registry metadata advertises this and you provide a key you trust; (2) SKILL.md mentions storing the key in ~/.clawdbot/clawdbot.json but the script does not read that file — do not assume the key will be read from disk; (3) the script sends X-Title and an HTTP-Referer header (defaulting to 'Clawdbot' and https://clawdbot.com) which will appear in your OpenRouter dashboard — change or remove these defaults if you don't want identifying metadata sent; (4) inspect and (if needed) run the script in an isolated environment first to confirm it behaves as expected and to test large-file handling; and (5) ask the skill author/maintainer to fix the metadata vs. code discrepancies (registry declarations, SKILL.md vs actual behavior) before trusting it with real credentials.

Type: OpenClaw Skill Name: openrouter-transcribe Version: 1.0.0 The skill bundle is benign. It transparently uses standard system binaries (ffmpeg, base64, jq, curl) to convert audio, encode it, and send it to the OpenRouter API for transcription. The `OPENROUTER_API_KEY` is read from the environment and used for authentication with the legitimate `openrouter.ai` endpoint, which is the stated purpose. There is no evidence of data exfiltration beyond the necessary API key, malicious execution, persistence mechanisms, or prompt injection attempts against the OpenClaw agent. All operations are clearly defined and aligned with the skill's description.