senseaudio-conversation-rehearsal
by @kikidouloveme79
Use when a user wants to rehearse a high-pressure conversation such as a performance review, reporting meeting, promotion defense, difficult manager conversa...
clawhub install senseaudio-conversation-rehearsal📖 About This Skill
name: senseaudio-conversation-rehearsal description: Use when a user wants to rehearse a high-pressure conversation such as a performance review, reporting meeting, promotion defense, difficult manager conversation, or stakeholder alignment session, using AudioClaw ASR for spoken rehearsal intake, AudioClaw TTS or an authorized cloned voice for the counterpart, and transcript-based debriefing on tone, structure, and communication risk.
AudioClaw Conversation Rehearsal
What this skill is for
This skill is for realistic conversation rehearsal in high-pressure situations:
It is designed to simulate the other person speaking back, not just generate a script.
Default stance
Use two voice modes:
proxy_voiceauthorized_clonevoice_id
- A prepared cloned voice id commonly looks like vc-..., and can be passed directly with --prepared-clone-voice-idDo not default to cloning a real person's voice without clear permission.
Workflow
1. Define the rehearsal:
- scenario
- counterpart role
- relationship
- talk topic
- desired outcome
- fear triggers
- difficulty
2. Run scripts/build_rehearsal_blueprint.py.
3. Decide voice mode:
- proxy voice
- authorized clone
4. Run the live loop in your agent stack:
- counterpart turn via TTS
- user spoken reply via ASR
- if you want faster perceived intake, enable stream ASR
- agent judges tone, structure, and progress
- use scripts/build_counterpart_turn.py to generate the next counterpart reply
- use scripts/senseaudio_counterpart_tts.py to synthesize that reply
- official clone chain: prepare the clone on the AudioClaw platform first and pass the resulting voice_id
- if that voice_id is a clone id like vc-..., counterpart TTS now auto-routes to SenseAudio-TTS-1.5
- optional experimental path: if an authorized platform token is available, use scripts/senseaudio_clone_workspace.py to inspect clone slots or attempt a rehearsal-only clone from an authorized sample
- if the user wants to actually hear the counterpart turns in Feishu or AudioClaw, use --send-feishu-audio or run scripts/send_rehearsal_counterparts_to_feishu.py
5. After the session, run scripts/analyze_rehearsal_transcript.py.
6. Produce a debrief:
- weak openings
- over-explaining
- vague asks
- missing evidence
- apologetic or defensive tone
- better rewrites
AudioClaw Trigger Pattern
Use this skill as a structured multi-turn rehearsal mode.
Recommended user trigger:
开始演练,用 $senseaudio-conversation-rehearsal。
场景:manager_update
对方身份:strict_manager
主题:项目延期说明
目标:获得补救方案认可
害怕点:被打断,被质疑执行力
难度:medium
prepared clone voice_id:your_clone_voice_id
后面我发语音,和我进行多轮演练,最后给我复盘。
The agent should:
1. Collect the rehearsal slots first.
2. Build the blueprint.
3. Enter rehearsal mode, with reply mode defaulting to voice.
4. Start the scene with the opening counterpart turn as voice, not text.
5. For every later rehearsal turn:
- transcribe with scripts/senseaudio_asr.py
- generate the next counterpart turn
- synthesize that turn with proxy voice or the prepared clone voice_id
- in ongoing rehearsal mode, default to --send-feishu-audio so the counterpart turns are sent as Feishu audio messages without needing the user to repeat that request
- only fall back to text-first replies if the user explicitly asks for text-only output or the channel cannot play voice
6. End with scripts/analyze_rehearsal_transcript.py and return a concrete debrief.
Rehearsal mode should be sticky inside the same session:
voice_idIf the user asks to "use the cloned voice", interpret that as:
voice_id when availablevoice_id or fall back to proxy_voiceDesign rules
API key lookup
For this skill, use SENSEAUDIO_API_KEY as the default API key source again.
Practical rule:
scripts/run_live_rehearsal_session.py, scripts/run_complete_rehearsal_service.py, and scripts/senseaudio_counterpart_tts.py now default to SENSEAUDIO_API_KEYSENSEAUDIO_API_KEY as a login token such as v2.public..., the shared bootstrap replaces it with the real sk-... value from ~/.audioclaw/workspace/state/senseaudio_credentials.json before the rehearsal call startsResources
scripts/build_rehearsal_blueprint.pyscripts/build_counterpart_turn.pyscripts/senseaudio_asr.pyscripts/senseaudio_counterpart_tts.pyscripts/run_live_rehearsal_session.py--stream-asr and --send-feishu-audio
scripts/send_rehearsal_counterparts_to_feishu.pyscripts/senseaudio_clone_workspace.pyscripts/senseaudio_platform_token.pyscripts/run_complete_rehearsal_service.pyvoice_id or attempts experimental workspace clone automation, runs the live rehearsal session, and writes a summary bundle
- Supports --send-feishu-audio so the rehearsal counterpart can proactively send voice turns to Feishu or AudioClaw-linked chats
scripts/analyze_rehearsal_transcript.pyreferences/live_rehearsal_loop.mdreferences/rehearsal_design.md