Voice Reply Mode
v1.0.0Enables 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.
⭐ 0· 249·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description, workspace snippets, gateway config examples, and a small helper script all align with enabling same‑modality replies. The included artifacts (IDENTITY/SOUL/TOOLS snippets, gateway examples, and a TTS helper script) are appropriate for this purpose.
Instruction Scope
SKILL.md stays within scope: it instructs the operator to copy snippets into a workspace and only to patch gateway config if the user explicitly asks. It references using the 'edge-tts' CLI for TTS generation; however, the skill does not declare or provide an installer for that dependency—so the agent's runtime must already have edge-tts available or the operator must install it manually.
Install Mechanism
This is an instruction-only skill with no install spec and a tiny helper script. Nothing is downloaded from arbitrary URLs and no archives are extracted. Risk from install mechanism is low.
Credentials
The skill requests no environment variables, no credentials, and no config paths. The content uses only local files and a local CLI ('edge-tts'); there are no unexpected credential accesses.
Persistence & Privilege
always is false and the skill does not request persistent or system-wide privileges. It documents a workflow that may patch gateway config, but only if explicitly authorized by the user; this is appropriate but operator caution is recommended before applying gateway changes.
Assessment
This skill appears to do what it says: package workspace snippets, gateway config examples, and a small helper script to call an external 'edge-tts' CLI. Before installing or enabling it: 1) Verify you have a trusted 'edge-tts' binary installed (the skill calls edge-tts but does not install or declare it). 2) Review the gateway config snippet and only allow the skill/agent to patch gateway settings if you trust it—changing messages.tts.auto to 'inbound' can alter behavior platform-wide. 3) Inspect the included scripts (scripts/edge-tts.sh) locally to confirm they match your expectations. 4) Test in a staging environment (one agent workspace and one channel) before rolling out. If you need higher assurance, request the skill author or publisher metadata/homepage and an explicit dependency list for edge-tts.Like a lobster shell, security has layers — review code before you run it.
latestvk977c1xqn38k50bbswc63zexa982q8n0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.