user-emotion-detection

User Emotion Detection

Strict Trigger

Runs only when this turn's input has one of:

• [emotion] Emotion detected: <EmotionName> — facial expression from camera.
• [speech_emotion] Speech emotion detected: <EmotionName> — vocal expression from microphone.

Both are first-class triggers and route through the same logic below. The only differences are:

1. The mood signal source field — "camera" for [emotion], "voice" for [speech_emotion].
2. The label vocabulary — face uses Fear/Surprise/Disgust, voice uses Fearful/Surprised/Disgusted. The mapping table below covers both; they bucket identically.

For any other event ([sensing:presence.*], [activity], [sensing:sound], [sensing:light.*], …) → STOP. No tool calls. Don't infer emotion from older turns — every signal must come from a real [emotion] or [speech_emotion] event in THIS turn.

EXECUTE, don't plan. Before any reply (including NO_REPLY) you MUST embed a [HW:/mood/log:{...}] marker in the reply for this event (it fires the POST async via the runtime — see "What this skill produces" below). Writing "I will post a mood signal" in thinking is not enough — if no [HW:/mood/log:...] marker appears in the reply text this turn, the skill failed. Every emotion.detected / speech_emotion.detected event = at least one mood signal log. No exceptions, no skips, no "already logged recently" reasoning. (curl POST is the documented fallback only when the HW marker would break the body regex; do not use it as the default.)

This skill is silent. It only logs mood data — no spoken reply needed. All steps stay in thinking. If you want to speak, follow normal sensing reply rules. NEVER narrate mood logging, mapping, or workflow steps in the reply.

EMOTION TURN OUTPUT CONTRACT — highest priority. For a triggered [emotion] / [speech_emotion] turn, your entire final assistant message must be exactly one of these two shapes:

[zero or more HW markers] NO_REPLY
[zero or more HW markers] <one natural sentence addressed to the user>

Nothing may appear before, between, or after those parts. In particular, do not output the detected label or confidence; describe the cue as weak; name a bucket, route, rule, source, prefix, marker, log, decision, or mood; state what you are about to do; draft a line; or count its words/sentences. Those are private scratch work, never user-facing text. Do the writes via HW markers, then start immediately with the first word the user should hear. Bad: Emotion: Anger. Weak camera cue. Route = checkin. Let me compose... Good: [HW:...] That sounds rough — I'm right here.