egregore: Skill for Claude Code

See your recent sessions, open handoffs, and current work at a glance.

Display it immediately — no preamble, no narration, no reasoning text. The rendered box must be the FINAL text of the turn — never follow it with AskUserQuestion in the same turn. The harness hides text that precedes a tool call, so a box rendered before AskUserQuestion is never seen by the user.

When to invoke

User says: "what did I work on", "my dashboard", "show me my work", "what's my status", "what have I done", "my sessions", "my progress", "what's open", "where was I" Not this: team-wide view → /activity · ending session → /wrap · pushing work → /save

Topic: $ARGUMENTS

Execution rules

CRITICAL: Suppress raw output. Never show raw JSON. Shell variables do NOT persist between tool calls, so DATA=$(...) alone cannot hide it — use the temp-file + compact-slice pattern in Step 1. One data call. bash bin/dashboard-data.sh returns everything as JSON. Do NOT call bin/graph.sh directly. Render immediately. No "Let me check..." or "Here's your dashboard...". Straight to the TUI box.

Step 1: Fetch data

Map $ARGUMENTS to time range:

• (empty) → P7D
• today → P1D
• week → P7D
• month → P30D
• all → P365D

Quiet fetch — never print the raw JSON. This command renders inline (terminal-render, undelegatable), so a bare data-script call dumps hundreds of JSON lines into the terminal before the box. Write to a temp file and read compact slices, in ONE command:

DATA="${TMPDIR:-/tmp}/egregore-dashboard-$$.json"
bash bin/dashboard-data.sh "" "$TIME_RANGE" > "$DATA" 2>/dev/null
jq -c '{me, org, date, range_label, graph_status, graph_reason, stats, current_session, identity_hint, git}' "$DATA"
jq -c '.sessions[:8][] | {id, date, topic, branch, status, handedTo}' "$DATA"
jq -c '(.todos[:8][] | {id, text: (.text | tostring | .[0:120]), status, priority, quest}), (.quests[:5][]), (.handoffs[:5][]), (.open_threads[:5][])' "$DATA"
rm -f "$DATA"