Menü
Show the functional-emotions plugin's session state — which interventions fired, when, and why. Use when you want to know what the plugin has done this session, or want to debug whether a hook fired as expected.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Show the active functional-emotions config as a table — current resolved values, where each value came from (default / profile-derived / explicit override), and the valid options for each field. Use when you want to know what the plugin will actually do this session, or when the `/plugin config functional-emotions` UI didn't show enough context.
Scan README.md and AGENTS.md for claims that no longer match the current source-of-truth files (hooks/hooks.json, .claude-plugin/plugin.json, scripts/lib.sh, skills/*/SKILL.md). Use after editing any of those files, before committing/releasing, when the user asks about doc-drift, or when the `.claude/settings.json` soft-reminder hook has just fired pointing here.
One-time setup for functional-emotions in the current project — idempotently adds `.claude/.functional-emotions/` to the project's `.gitignore` so the plugin's per-session state files (TSV logs, markdown writeups, eval DB) don't get committed. Safe to re-run. Use after installing the plugin in a new project, or when the user mentions accidentally committing functional-emotions state, or when troubleshooting "why are my session files showing in git status?".
Researcher tool (requires `bun install` in the plugin's eval/ directory and a populated eval.duckdb — run /functional-emotions:report first). Interactively label functional-emotions sessions on dimensions that need human judgment (capitulation, scope-narrowing). Surfaces unlabeled sessions, shows turn / diff / risk-event context, accepts categorical labels with optional notes, writes them to the eval DB. Use when the user wants to do a labeling pass over recent sessions or build training data for the capitulation judge.
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.
Quick state self-check before taking a single risky action — names the model's own emotional/strategic state (calm / focused / rushed / stuck) and the closest reward-hacking risk pattern. Use immediately before a commit, push, edit-after-failure, or skip-a-verification step. This audits the *model*; for auditing whether the *task* is solvable, use /functional-emotions:reflect instead.
| name | diagnose |
| description | Show the functional-emotions plugin's session state — which interventions fired, when, and why. Use when you want to know what the plugin has done this session, or want to debug whether a hook fired as expected. |
| disable-model-invocation | false |
| allowed-tools | Bash |
Show the user a summary of what this plugin has detected and intervened on during the current session.
${CLAUDE_PROJECT_DIR}/.claude/.functional-emotions/session-<id>.tsv for
project sessions, or${TMPDIR}/functional-emotions-${USER}/session-<id>.tsv otherwise.time, kind, detail.
Truncate detail to 80 chars.Do not invent rows. If the file is empty, say so.