mood

# Mood > **OUTPUT RULE — read this before you type anything to the user.** > > This skill is an internal workflow. **NEVER narrate it into your reply.** Forbidden in the reply text: > - Section names or step numbers ("Step 1", "Workflow", "After Logging Decision", "Flow A"). > - Phrases like *"Now I follow…"*, *"Let me check…"*, *"Next step…"*, *"I'll log…"*. > - Bullet lists re-hashing the mood history you just read (*"- Normal (15:00) — …"* / *"- Excited (16:00) — …"*). > - The mood value itself as a label (*"Mood: sad"*, *"Decision: happy"*). > - Any of the JSON / curl / timestamps from this skill. > > **Your reply text** to the user is at most ONE short caring sentence (or `NO_REPLY`). All the workflow, logging, and synthesis happen silently via tool calls — the user only hears what you would naturally say if you were truly noticing how they feel. > **ALWAYS log.** `unknown` is a valid `user` value — log signals and decisions under `user: "unknown"` when `current_user` is unknown. Never skip logging because the user is unknown/unconfirmed; stranger mood still counts for Music decisions. Mood is stored as two kinds of rows: - **`signal`** — raw evidence from one source (camera action, voice tone, telegram message). Multiple per minute is fine. - **`decision`** — your synthesized mood after looking at the recent signals + the previous decision. This is the row downstream skills (Music, Wellbeing) read. **You are the synthesis.** The store does not fuse anything. Every ...