Find insights across many sessions

Turn a set of recorded sessions into a few well-evidenced insight cards. The server's analyzer counts known signals cheaply. This skill reads whole sessions with models, so it can find behavior nobody wrote a counter for, and it can read the agent's code to suggest why.

Cards are leads, not verdicts. Every card says what was read, how sessions were picked, and how sure the finding is. A human confirms a behavior later through kitaru-investigation.

Read the relevant reference

• Read insight-method.md before choosing a level, sampling, grouping notes, measuring a pattern, or wording a card.
• Read subagent-briefs.md before fanning out to subagents or choosing their model. It holds the exact briefs and the note formats they write.
• Read kitaru-operations.md before any Kitaru CLI or MCP call. It lists exact commands, limits, and known gaps.
• Read insight-contract.md before drafting, checking, writing, or replacing cards.

Use the helper scripts in scripts/ as each reference directs. They use only the Python standard library, read files already exported to the run folder, and never contact Kitaru.

Keep these rules