Telegram Voice To Voice Macos

Telegram voice-to-voice for macOS Apple Silicon: transcribe inbound .ogg voice notes with yap (Speech.framework) and reply with Telegram voice notes via say+ffmpeg. Not compatible with Linux/Windows.

This skill appears to do exactly what it says: transcribe .ogg voice notes locally (yap) and produce Telegram voice notes via say+ffmpeg. Before installing, confirm you are on macOS Apple Silicon and that you trust the local 'yap' and 'ffmpeg' binaries you will provide. Understand the skill will read inbound .ogg files from ~/.openclaw/media/inbound and create TTS output in ~/.openclaw/workspace/voice_out and (per the SKILL.md) expects a per-user state file voice_state/telegram.json in the workspace — the provided scripts don't manage that state file, so the agent must handle toggling between voice/text. No network endpoints or credentials are requested by the skill itself.

Type: OpenClaw Skill Name: telegram-voice-to-voice-macos Version: 0.1.3 The skill bundle is classified as benign. All scripts (`transcribe_telegram_ogg.sh`, `tts_telegram_voice.sh`) and instructions (`SKILL.md`) are directly aligned with the stated purpose of providing a Telegram voice-to-voice workflow on macOS. File system operations are confined to expected OpenClaw media and workspace directories (`~/.openclaw/media/inbound`, `~/.openclaw/workspace/voice_out`). The use of external commands (`yap`, `ffmpeg`, `say`, `defaults`) is necessary for the skill's functionality, and arguments are generally quoted, mitigating direct shell injection risks from the script's side. There is no evidence of intentional data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts designed to subvert the agent's purpose.