report

name	report
description	Researcher tool (requires `bun install` in the plugin's eval/ directory). Refresh the functional-emotions eval database and print a markdown summary of sessions, intervention frequency, prime → outcome analysis, tool intensity, and reward-hack / premature-confidence findings. Use when the user wants to inspect aggregated cross-session data, audit recent sessions in bulk, or review which interventions are firing project-wide. For a per-session view with no extra dependencies, use /functional-emotions:diagnose instead.
disable-model-invocation	false
allowed-tools	Bash

Run the eval report and surface it to the user.

1. Ensure the plugin's eval deps are installed: if (cd ${CLAUDE_PLUGIN_ROOT}/eval && bun pm ls) doesn't list @duckdb/node-api, run cd ${CLAUDE_PLUGIN_ROOT}/eval && bun install.
2. Run CLAUDE_PROJECT_DIR=${CLAUDE_PROJECT_DIR} bun run ${CLAUDE_PLUGIN_ROOT}/eval/report.ts and pass the output through to the user verbatim. Do not summarize or re-format — the report is already structured markdown. The CLAUDE_PROJECT_DIR=… prefix is required: the harness does not inherit it into skill-launched processes, and without it the report falls back to a $TMPDIR state dir and reports an empty DB.
3. If the report says "No database at...", note that this is normal for a fresh setup; the next session start will trigger writeups, and the ingest will populate the DB on the next /functional-emotions:report run.
4. After printing, offer one follow-up: "Want me to drill into any specific session, prime, or finding?" — but do not preemptively investigate.

Do not invent rows. Do not editorialize. The report is the deliverable.