AudioClaw Skills Voice Reply

When to use

Use this skill when AudioClaw already has the final reply text and now needs a voice version that can change on demand.

Common triggers:

• - A chat bot should answer in different tones such as calm, warm, cheerful, serious, or promo.
• The caller wants to switch voice_id or voice_family in a single request without editing code.
• The same AudioClaw workflow should support both free voices and paid or custom voices.
• The runtime should keep working even when a requested voice is not available to the current key.
• A user has already said "以后一直给我发语音", and AudioClaw should remember that preference for future turns.
• AudioClaw needs a workspace-local file plus a stable way to deliver it as a Feishu audio message.
• The caller already has a cloned AudioClaw voice_id such as vc-... and wants the runtime to use it directly without falling back first.

Do not use this skill for ASR intake or long-form digest generation.

Workflow

1. 1. Start from the final user-facing text. Do not pass hidden reasoning or raw markdown tables.
2. Build an AudioClaw voice request with:

- text - optional scene - optional voice_id - optional voice_family - optional emotion - optional speed, pitch, volume

1. 3. Run scripts/openclaw_voice_switchboard.py.

- For AudioClaw on Feishu or Lark, prefer scripts/picoclaw_voice_reply.py.

1. 4. Let the script resolve the request in this order:

- exact voice_id - voice_family plus matching emotion variant - scene plus emotion preset - validated fallback voice - Important: if the exact voice_id is a clone-style id such as vc-..., this skill now tries that id directly first, even if it is not part of the built-in official voice catalog.

1. 5. If preference_key is present, the script can remember:

- reply_mode - default voice_id - default emotion - default scene

1. 6. If the result should be sent through AudioClaw media upload, pass:

- --out inside the AudioClaw workspace - --openclaw-workspace-root pointing at the workspace root - --delivery-profile feishu_voice when the downstream channel prefers .ogg/.opus - optional --chmod 644 if you want to be explicit, though this skill now defaults to 0644 - if --openclaw-workspace-root is set and --out is omitted, this skill now writes to workspace/state/audio/ automatically

1. 7. Use the returned JSON manifest in AudioClaw to:

- prefer scripts/picoclaw_voice_reply.py for AudioClaw on Feishu - let the wrapper send the Feishu audio message directly - do not send the local path or the MEDIA:... line through the message tool - only use send_file when you intentionally opt out of direct Feishu sending - log trace_id - persist the resolved voice choice for the next turn if desired

1. 8. If the requested voice is not available to the current key, let the fallback stand unless the user explicitly requires strict failure.
2. If you want AudioClaw to remember a clone voice, either:

- set it as the user's default voice with --set-default-voice-id vc-... - or register it explicitly with INLINECODE43

Voice discovery

When AudioClaw needs to find a usable voice or confirm a voice_id, use this order:

1. 1. Check the local catalog first:

- run python3 scripts/openclaw_voice_switchboard.py --list-voices - use this for fast lookup of built-in voices, known emotion variants, and clone voices already registered locally

1. 2. If the user asks for the official public voice list, package availability, or a voice not found locally, check the official voice page:

- https://senseaudio.cn/docs/voice_api - page title: API 音色服务说明

1. 3. Prefer the official page when AudioClaw needs to confirm:

- whether a voice_id is a free, VIP, or SVIP voice - whether a named speaker has multiple emotion variants - whether the request likely needs selected-voice purchase or custom voice authorization

1. 4. After finding a likely voice_id, still let the runtime validate access at synthesis time, because account permissions can differ by key.

Practical rule:

• - Local --list-voices is the first-stop runtime catalog.
• INLINECODE51 is the canonical fallback reference for official voice names, voice_id, and package tier notes.

AudioClaw rule

When this skill is used inside AudioClaw for Feishu or Lark voice replies:

1. 1. Run scripts/picoclaw_voice_reply.py.
2. Let the wrapper upload the generated .ogg/.opus file to Feishu and send it as msg_type=audio.
3. Do not call the send_file tool for that audio unless you explicitly passed --skip-direct-send.
4. Do not call the message tool with the local path or the MEDIA:... reference. AudioClaw will send them as plain text.
5. After the audio is sent, prefer no extra text confirmation.
6. If the host runtime still requires one final assistant message to finish the turn, send one short natural Chinese line such as 我已经用语音回复你了。 instead of leaving the turn empty.
7. Use media_reference only as debug metadata or future AudioClaw compatibility data.

This rule matters because this AudioClaw environment does not render MEDIA:... as media, and the generic send_file tool sends Feishu voice notes as plain files instead of audio messages. The reliable path here is direct Feishu upload plus msg_type=audio.

Runtime model

The official public TTS API exposes:

• - INLINECODE66
• INLINECODE67
• INLINECODE68
• INLINECODE69
• INLINECODE70
• INLINECODE71
• one HTTP endpoint with two modes:

- non-stream with stream=false
- SSE with INLINECODE73

Important constraint:

• - The public TTS API docs do not expose a standalone emotion request field.
• Emotion switching is therefore handled by choosing a matching voice_id when one exists, or by keeping the voice and shaping speed / pitch / vol.
• This skill requests final-file TTS in non-stream mode by default, because AudioClaw only needs the completed file and this avoids stream assembly edge cases.
• For this server-side HTTP TTS path, the official docs still use Authorization: Bearer API_KEY. The generated Public Key is not required by this skill.
• If the requested voice_id looks like a clone id such as vc-..., this skill now auto-routes TTS to SenseAudio-TTS-1.5 and records audio.model_used in the manifest.

API key lookup

This skill now treats SENSEAUDIO_API_KEY as the default API key source again.

Runtime rules:

• - If the host app injects SENSEAUDIO_API_KEY as an AudioClaw login token such as v2.public..., the shared bootstrap will replace it with the real sk-... value from ~/.audioclaw/workspace/state/senseaudio_credentials.json before TTS starts.
• INLINECODE88 still works, but the default runtime path is SENSEAUDIO_API_KEY.

If you need the exact same speaker timbre across many emotions, use a purchased multi-variant voice family or an authorized custom voice. Otherwise this skill will approximate the requested emotion with the best available voice and tuning.

Request contract

Minimal JSON request:

CODEBLOCK0

Full request:

CODEBLOCK1

Clone voice example:

CODEBLOCK2

Supported emotion presets:

• - INLINECODE90
• INLINECODE91
• INLINECODE92
• INLINECODE93
• INLINECODE94
• INLINECODE95
• INLINECODE96
• INLINECODE97
• INLINECODE98

Supported scene hints:

• - INLINECODE99
• INLINECODE100
• INLINECODE101
• INLINECODE102
• INLINECODE103
• INLINECODE104
• INLINECODE105
• INLINECODE106
• INLINECODE107

AudioClaw integration pattern

Recommended handoff:

1. 1. AudioClaw generates final reply text.
2. AudioClaw decides whether this turn should speak and what mood it wants.
3. AudioClaw calls scripts/openclaw_voice_switchboard.py with a request JSON.
4. The script returns a manifest with:

- requested voice - resolved voice - emotion strategy - effective speed / pitch / volume - delivery profile and file mode - local audio path - AudioClaw-friendly media reference when the output is under a workspace root - trace_id

1. 5. AudioClaw uploads the resulting file to Feishu or any downstream channel, or lets the AudioClaw wrapper do that directly for Feishu.

Operational rules:

• - Cache by resolved voice plus text plus audio settings.
• If a paid voice is unavailable, allow fallback unless the request is marked strict.
• Always log the resolved voice and trace_id.
• Force generated audio files to mode 0644 so the AudioClaw sender can read them reliably.
• When --openclaw-workspace-root is set and --out stays inside that root, expose delivery.openclaw_media_reference.
• When --delivery-profile feishu_voice is enabled, synthesize with AudioClaw first and then transcode to ogg/opus with system ffmpeg or imageio-ffmpeg.
• This publishable skill intentionally does not bundle ffmpeg. Install ffmpeg or run python3 -m pip install imageio-ffmpeg on the target machine.
• Avoid ad-hoc temp filenames under the workspace root. Prefer workspace/state/audio/, which this skill will now use automatically when --openclaw-workspace-root is given without --out.
• For AudioClaw on Feishu, scripts/picoclaw_voice_reply.py now uses the local Feishu app credentials from ~/.audioclaw/config.json, uploads the audio through the official /open-apis/im/v1/files endpoint, and sends it as msg_type=audio.
• The wrapper infers the active Feishu chat_id from the latest agent_main_feishu_direct_*.jsonl session log unless you pass --chat-id explicitly.

Commands

List voices:

CODEBLOCK3

Check the official voice catalog page:

CODEBLOCK4

List emotion presets:

CODEBLOCK5

Enable permanent voice reply for one user:

CODEBLOCK6

Enable permanent cloned-voice reply for one user:

CODEBLOCK7

Register a prepared clone voice so the runtime can list and reuse it:

CODEBLOCK8

Show registered clone voices:

CODEBLOCK9

Show current voice preference:

CODEBLOCK10

Generate one AudioClaw turn from a JSON request:

CODEBLOCK11

Direct CLI example:

CODEBLOCK12

AudioClaw Feishu one-step example:

CODEBLOCK13

Only generate, do not send:

CODEBLOCK14

Resources

• - INLINECODE133

- Small importable client for https://api.senseaudio.cn/v1/t2a_v2 - Handles SSE chunks and writes audio bytes

• - INLINECODE135

- TTS capability summary plus the official voice catalog reference at https://senseaudio.cn/docs/voice_api

• - INLINECODE137

- Main runtime for AudioClaw - Resolves voice, emotion, fallback, caching, and output manifest

• - INLINECODE138

- AudioClaw-first wrapper - Generates audio and, by default, sends it to Feishu as a real audio message

• - INLINECODE140

- Direct Feishu sender for .ogg/.opus - Uses ~/.audioclaw/config.json app credentials by default, infers the active chat, uploads the file, and sends msg_type=audio

• - INLINECODE144

- Official docs summary, request examples, and AudioClaw capability boundaries