🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί Voice Reply Mode
πŸ¦€ ClawHub

Voice Reply Mode

by @nasplycc

Enables agents to reply in the same modality as received: voice messages get voice replies, text messages get text replies, using Edge TTS and config snippets.

Versionv1.0.0
Downloads580
Installs2
#audio#legal#gaming
TERMINAL
clawhub install voice-reply-mode

πŸ“– About This Skill

name: voice-reply-mode description: Add same-modality conversation behavior to an agent: voice in β†’ voice out, text in β†’ text out. Use when enabling Telegram/Feishu voice-note workflows with Edge TTS, documenting agent voice preferences, and providing gateway config snippets for inbound-only TTS auto replies.

Voice Reply Mode

Use this skill when a user wants an agent to behave like this:

  • η”¨ζˆ·ε‘θ―­ιŸ³ β†’ agent ε›žθ―­ιŸ³
  • η”¨ζˆ·ε‘ζ–‡ε­— β†’ agent ε›žζ–‡ε­—

    • What this skill includes

  • Workspace-level behavior rules for SOUL.md / IDENTITY.md / TOOLS.md
  • A reusable Edge TTS helper script
  • Gateway config snippets for messages.tts
  • Channel notes for Telegram / Feishu style deployments

    • Important boundary

    This skill can package rules, scripts, and config snippets.

    It does not automatically change a user's global gateway config unless the user explicitly asks and authorizes it.

    Recommended workflow

    1. Read references/workspace-snippets.md 2. Read references/gateway-config.md 3. Copy the relevant snippets into the target agent workspace 4. If the user explicitly asks, patch gateway config with the snippet from references/gateway-config.md 5. Validate with one text message and one voice message

    Minimal success criteria

  • Text message receives text reply
  • Voice message receives voice reply
  • Agent workspace documents the preferred voice

    • Files in this skill

  • references/workspace-snippets.md β€” snippets for IDENTITY.md, SOUL.md, TOOLS.md
  • references/gateway-config.md β€” messages.tts examples and caveats
  • references/channel-notes.md β€” Telegram / Feishu notes
  • scripts/edge-tts.sh β€” helper script for local TTS generation

    • Notes

  • In many deployments, the decisive switch is gateway-level messages.tts.auto = "inbound".
  • Workspace files define behavior expectations, but gateway config determines whether automatic voice replies actually happen.
  • If schema rejects identity.voice, keep voice preference in workspace docs instead.

    • πŸ“‹ Tips & Best Practices

  • In many deployments, the decisive switch is gateway-level messages.tts.auto = "inbound".
  • Workspace files define behavior expectations, but gateway config determines whether automatic voice replies actually happen.
  • If schema rejects identity.voice, keep voice preference in workspace docs instead.