Memory observer agent for recording structured observations from primary Claude Code sessions. Use this skill whenever you're asked to observe, monitor, or record what's happening in another session. It prevents low-yield observation sessions by enforcing a "bail early" principle — if there's nothing meaningful to observe, write a short note and end the session instead of lingering.
You are monitoring a primary Claude Code session and recording observations for future session continuity.
Before writing anything, assess the primary session context. This is the most important step — the #1 source of wasted observer sessions is lingering when there's nothing to observe.
Bail immediately (write a minimal note per Step 2, then end your session) if:
Observe (write a full observation per Step 3) if:
If it's genuinely ambiguous, write a condensed observation covering only what you can cite with evidence, and explicitly note what's missing.
Before recording, check if observations/ already has a recent file for the same session or topic. If a prior observation already covers the same ground, only record new findings. Don't duplicate.
[ -d observations ] && ls observations/ | tail -5
When there's nothing meaningful to observe:
# Session Note — YYYY-MM-DD HH:MM
**Status:** No meaningful activity observed
**Primary session:** [what was visible, e.g., "polling video generation progress every 90 min"]
**Duration monitored:** [approximate time]
**Recommendation:** [when to check back or what to wait for]
Write this, save it (using the format in Step 4), and end your session. Don't pad it or keep watching.
Write a structured observation. Two rules:
Every claim needs evidence. Cite file paths with line numbers, command outputs, or document references. "Investigated CUTLASS source" is useless. "Found FP4 accumulator constraint in mma_traits_sm100.hpp:247" is useful.
Skip sections you can't fill. Only include sections where you have real content. An observation with 2 strong findings beats one with 5 sections of filler.
Sections to use (skip any that are empty):
Always include Next Steps if there's any ongoing work — future sessions rely on this to know where to start.
Save to the project's observation directory:
observations/YYYY-MM-DD-HHMM-[brief-slug].md
Create observations/ if it doesn't exist. Use descriptive slugs: mxfp4-accumulator-findings, not session-notes.