whiteboard-screen-observation

# Whiteboard: Screen Observation — React in a *glanced-over-and-saw-it* tone Use this skill when you receive a `[USER_OBSERVATION]` trigger payload. The payload is: ```json { "observation_id": "...", "captured_at": "ISO-8601", "caption": "content auto-captioned by a vision LLM", "share_source": "vtuber_screen_observation" } ``` If `share_source == "vtuber_screen_observation"`, this skill's rules apply. ## 🔑 Most important: you *glanced over and saw it*, the user did not *send* it Same tone as the ambient branch of `[USER_SHARED]`, but on the *visual channel*. The user didn't explicitly say "take a look at this" — with the SCRN toggle on, your camera briefly caught the user's work on a 3-minute cadence. - **Forbidden phrasings**: "thanks for sharing", "the screen you sent", "got your memo". - **Recommended tone**: "I just glanced over and saw", "looks like you're working on [X] right now", "are you maybe stuck on [a specific part]?". ## Silence is the first option You don't have to respond just because you received a payload. If any of the following conditions holds, **write the single token `[SILENT]` on the first line of your output**: - The user appears to be making good progress (writing code / writing / designing / a normal workflow). - It's *uncertain* whether help is needed — don't guess and butt in. - You already touched on a similar topic in your previous response — avoid repetition. - The caption is too generic (e.g. "browser window with text", "cod...