TTS Media Route Fix

Fix and verify OpenClaw TTS media-route behavior in installed dist builds. Use when users report that tts.convert returns unusable audio URLs, media TTS MP3...

This skill appears to do what it says: locate hashed gateway-cli dist files, back them up, apply a minimal patch to the TTS media route, restart the gateway, and verify with an authenticated range request. Before using it: (1) review the exact patch you will apply to the gateway-cli-*.js files—do the edits locally and confirm they only implement the stated checks (filename validation, Bearer auth, proper Content-Type, Range support, TTL cleanup); (2) ensure you have backups and a rollback plan (the SKILL.md emphasizes .bak files); (3) run the workflow in a staging environment first to avoid production downtime; (4) supply bearer tokens only on the local command line and avoid pasting them to untrusted systems; and (5) verify you trust the skill source—manual edits to installed runtime files are powerful and should be done by an operator who can inspect the changes. If you want higher assurance, request an explicit patch diff or an automated patch script that you can review before applying.

Type: OpenClaw Skill Name: tts-media-route-fix Version: 1.0.0 The skill bundle instructs an AI agent to perform live-patching of production application binaries (gateway-cli-*.js) to fix TTS routing issues. While the instructions in SKILL.md include security-conscious guardrails such as path traversal prevention and authentication enforcement, the capability to modify core application logic at runtime is a high-risk behavior. The scripts find_gateway_cli.sh and verify_tts_media_route.sh are functional for the stated purpose but facilitate sensitive file system modifications that could be abused if the agent's instructions were subverted.