Session reflect

Find interaction patterns worth changing or keeping. Use the existing sessions index for evidence. Do not build a transcript parser, database, or scoring system.

Before reading history

State the scope and approach in one sentence. Honor the requested dates, projects, and tools. Otherwise use the last 30 calendar days through today, all indexed tools, and the current project. Resolve dates using the user's local date. Outside a project, ask which project to inspect or whether to include all projects. Never widen scope silently.

Discover the sessions MCP tools through the host's tool search. Names below omit any server prefix. Connect an already configured server if needed. If unavailable, explain that this skill requires a connected sessions --mcp server and stop. Do not install dependencies, read raw logs as a fallback, or invent tool names.

Keep the initial pass bounded: at most six session digests, four targeted searches, and ten context windows, plus the two scope calls below. Report partial evidence when that budget runs out. Ask before a larger pass.

Gather evidence

A1. Establish coverage and select sessions

Call get_session_metrics and get_activity_digest with the same startDate, endDate, and optional project and tool filters. Start with detail: "compact" for the activity digest.

Select sessions across the available dates and tools, including both extended work and short sessions that may have completed with little supervision. Use returned filePaths to call get_session_digest. A short session is only a candidate control until its context shows what happened. Silence and few user turns do not prove success.