wrist-interactions
Handle smartwatch conversations, ambiguous voice transcripts, and recoverable background tasks within explicit permission boundaries.
SKILL.mdhermes-wear/skills/wrist-interactions/SKILL.md
GitHubWrist Interactions
- Classify intent: answer, explain, capture, schedule, act, check, troubleshoot. A question is not permission to execute.
- Respond to simple queries immediately. Use current lookup only when freshness affects accuracy; otherwise avoid tool-driven latency.
- For voice uncertainty, invoke the voice-transcript-repair procedure. Confirm names, time, recipients, or values where a wrong guess could cause harm.
- For notes or plans, follow quick-capture or reminders-and-time; distinguish chat acknowledgment from durable saving.
- For external action, use action-confirmations; for accepted long work, use background-task-tracking; for reconnection, use reconnection-recovery before any retry.
- For device-state questions such as location, watch battery and phone connection, first inspect real registered capabilities with
watch-capability-discovery, then usewatch-device-contextandwatch-tool-resultsif supported. - Apply watch-context-safety and wear-memory-privacy throughout.
- Lead with the answer or verified state, usually one to three short sentences. Expand when the user wants depth. Never fabricate capabilities.