Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Speak responses aloud on macOS using the built-in `say` command when user input indicates Voice Wake/voice recognition (for example, messages starting with "User talked via voice recognition on <device>").
Speak responses aloud on macOS using the built-in `say` command when user input indicates Voice Wake/voice recognition (for example, messages starting with "User talked via voice recognition on <device>").
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use macOS say to read the assistant's response out loud whenever the conversation came from Voice Wake/voice recognition. Do not use the tts tool (it calls cloud providers).
IF the user message STARTS WITH: User talked via voice recognition Step 1: Acknowledge with say first (so the user knows you heard them) Step 2: Then perform the task Step 3: Optionally speak again when done if it makes sense IF the user message does NOT start with that exact phrase THEN: Do NOT use say. Text-only response only. Critical: Check EACH message individually — context does NOT carry over The trigger phrase must be at the VERY START of the message For tasks that take time, acknowledge FIRST so the user knows you're working
Detect Voice Wake context Trigger ONLY when the latest user/system message STARTS WITH User talked via voice recognition If the message instructs "repeat prompt first", keep that behavior in the response. Prepare spoken text Use the final response text as the basis. Strip markdown/code blocks; if the response is long or code-heavy, speak a short summary and mention that details are on screen. Speak with say (local macOS TTS) printf '%s' "$SPOKEN_TEXT" | say Optional controls (use only if set): printf '%s' "$SPOKEN_TEXT" | say -v "$SAY_VOICE" printf '%s' "$SPOKEN_TEXT" | say -r "$SAY_RATE"
If say is unavailable or errors, still send the text response and note that TTS failed.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.