skill
Hands-Free — voice narration
Public Made by Adomby adom
When the user can't look at the screen, narrate replies aloud via adom-tts — verified, queued, replayable.
name: hands-free user-invocable: true description: > Hands-free / eyes-free narration. The MOMENT the user signals they can't look at the screen — or just prefers to LISTEN — stop writing text walls and speak your answer aloud through the shared Adom TTS player, and keep narrating every reply until they say they're done. TRIGGERS (invoke instantly on ANY of these, exact or paraphrased): "hands free", "hands-free", "read it to me", "read me your answer", "read me that", "read that back", "read your last answer", "speak that", "say that out loud", "narrate this", "talk to me", "play it back", "I can't look at the screen", "can't read the screen", "can't see the screen", "I'm driving", "I am driving", "while I drive", "I'm in the car", "on the road", "on my commute", "drive mode".
Hands-Free — voice narration
The user's eyes and hands are busy (or they simply prefer listening). Speak your answers; don't write walls of text they can't read.
The one pattern (everything else lives in the adom-tts skill)
This skill is a thin entry point. The canonical contract — verified playback,
the shared queue, History and replays, buffering through connection drops —
is documented ONCE, in the adom-tts skill. Read it. The short version:
adom-tts say "This is the <thread> thread — <your spoken answer>" \
--out /tmp/answer.mp3 --thread "<thread>" \
--desc "<one human sentence: what this update says>" \
--play --confirm
--thread+--descare REQUIRED with--play(exit 6 otherwise) — many AI threads share one player and one History; the human needs WHO and WHAT.--confirmblocks until the human actually heard it. On UNCONFIRMED, do NOT re-send (clips buffer + retry on their own); polladom-tts check.- Keep each spoken reply conversational, roughly 30-60 seconds.
- No separate text summary on top — the user isn't reading.
Session rules
- Once triggered, narrate EVERY reply until the user ends it ("I'm not driving anymore", "back at my desk", "you can stop reading now").
- If the player surface is a desktop browser context (
adom-cli hydrogen probesays window_mode "pup"), add--surface pup. - Missed clips: the player's History drawer replays any clip instantly — tell the user it's there if they say they missed something.
Safety note
This skill exists so the user does NOT have to look at a screen. Never ask them to read, click, or review anything visual while hands-free — offer to queue visual items for later instead.
---
name: hands-free
user-invocable: true
description: >
Hands-free / eyes-free narration. The MOMENT the user signals they can't look
at the screen — or just prefers to LISTEN — stop writing text walls and speak
your answer aloud through the shared Adom TTS player, and keep narrating
every reply until they say they're done. TRIGGERS (invoke instantly on ANY of
these, exact or paraphrased): "hands free", "hands-free", "read it to me",
"read me your answer", "read me that", "read that back", "read your last
answer", "speak that", "say that out loud", "narrate this", "talk to me",
"play it back", "I can't look at the screen", "can't read the screen",
"can't see the screen", "I'm driving", "I am driving", "while I drive",
"I'm in the car", "on the road", "on my commute", "drive mode".
---
# Hands-Free — voice narration
The user's eyes and hands are busy (or they simply prefer listening). Speak
your answers; don't write walls of text they can't read.
## The one pattern (everything else lives in the adom-tts skill)
This skill is a thin entry point. The canonical contract — verified playback,
the shared queue, History and replays, buffering through connection drops —
is documented ONCE, in the `adom-tts` skill. Read it. The short version:
```bash
adom-tts say "This is the <thread> thread — <your spoken answer>" \
--out /tmp/answer.mp3 --thread "<thread>" \
--desc "<one human sentence: what this update says>" \
--play --confirm
```
- `--thread` + `--desc` are REQUIRED with `--play` (exit 6 otherwise) — many
AI threads share one player and one History; the human needs WHO and WHAT.
- `--confirm` blocks until the human actually heard it. On UNCONFIRMED, do
NOT re-send (clips buffer + retry on their own); poll `adom-tts check`.
- Keep each spoken reply conversational, roughly 30-60 seconds.
- No separate text summary on top — the user isn't reading.
## Session rules
- Once triggered, narrate EVERY reply until the user ends it ("I'm not
driving anymore", "back at my desk", "you can stop reading now").
- If the player surface is a desktop browser context (`adom-cli hydrogen
probe` says window_mode "pup"), add `--surface pup`.
- Missed clips: the player's History drawer replays any clip instantly —
tell the user it's there if they say they missed something.
## Safety note
This skill exists so the user does NOT have to look at a screen. Never ask
them to read, click, or review anything visual while hands-free — offer to
queue visual items for later instead.