[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79XARAH2SP3VFFXNBQF84VN":3,"skill-same:01M79XARAH2SP3VFFXNBQF84VN":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":38,"updatedAt":39,"install":40,"resources":52},"01M79XARAH2SP3VFFXNBQF84VN","dashboard",null,"Real-time harness observability dashboard. Reads campaigns, fleet sessions, telemetry, and pending queues to present a snapshot of harness state at a glance. Invoked by \u002Fdashboard, \u002Fdo status, or phrases like \"what's happening\" and \"show activity\".","mayankjain1815-commits\u002FCITADEL","mayankjain1815-commits","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F234472344?v=4","01M79X9599EWEQTD62DMNTEG7X","Mayank jain","01M79X95AA0KDFTN1Z1A6DQTX1",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits\u002FCITADEL\u002Fblob\u002Fmain\u002Fskills\u002Fdashboard\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dashboard\nlicense: MIT\ndescription: >-\n  Real-time harness observability dashboard. Reads campaigns, fleet sessions,\n  telemetry, and pending queues to present a snapshot of harness state at a\n  glance. Invoked by \u002Fdashboard, \u002Fdo status, or phrases like \"what's happening\"\n  and \"show activity\".\nuser-invocable: true\nauto-trigger: false\ntrigger_keywords:\n  - dashboard\n  - what's happening\n  - what's going on\n  - show activity\n  - harness state\n  - show me status\nlast-updated: 2026-03-26\n---\n\n# \u002Fdashboard — Harness Observability Dashboard\n\n## When to Use\n\n- \"What's happening?\" \u002F \"Status?\" \u002F \"What's going on?\"\n- \"Show activity\" \u002F \"Show me the dashboard\"\n- After returning to a project after time away\n- When \u002Fdo routes \"status\", \"dashboard\", \"what's happening\", \"what's going on\", \"show activity\"\n- Directly: `\u002Fdashboard`\n\n## Inputs\n\nNone required. Works with whatever state exists on disk.\n\n## Protocol\n\n### Step 0: RUN DASHBOARD IMPLEMENTATION\n\nRun the local dashboard implementation from the project root:\n\n```bash\nnode scripts\u002Fdashboard.js\n```\n\nIf the package scripts are available, this equivalent command is also valid:\n\n```bash\nnpm run dashboard\n```\n\nThe script is read-only. It renders a user-facing control-plane snapshot from\n`.planning\u002F`, telemetry, hook config, coordination state, worktrees, and cost\ndata. Use the manual collection protocol below only as a fallback if the script\nis missing or fails in the current project.\n\n### Step 1: COLLECT STATE\n\nRead the following sources. Each is optional — if a file or directory doesn't\nexist, treat it as empty. Never crash on missing state.\n\n**Campaigns:**\n- Glob `.planning\u002Fcampaigns\u002F*.md`\n- For each file, read the first 40 lines to extract:\n  - `Status:` field\n  - `Direction:` field (truncate to 60 chars)\n  - Phase progress (search for `Phase N of M` or `## Phase` headings)\n  - Most recent line starting with `- [` from the Decision Log\n- If all phases are complete but status is still active, report\n  `needs-completion` and show:\n  `node scripts\u002Fcampaign.js complete \u003Cslug> --archive`\n- If a campaign is marked completed but still lives in `.planning\u002Fcampaigns\u002F`,\n  report `needs-archive` and show the same archive command.\n- If prior build\u002Fverify phases are complete but the `review-package` Exit\n  Evidence row is still pending, missing, or points at a missing local package,\n  report a repair before campaign completion:\n  `node scripts\u002Fpackage-delivery.js \u003Cslug>`\n\n**Cost Data (two sources, prefer real):**\n\n- Primary: run `node scripts\u002Fsession-tokens.js --today` and `--all` — reads Claude Code's native session JSONL for exact token counts\n- Fallback: read `.planning\u002Ftelemetry\u002Fsession-costs.jsonl`; cost priority `real_cost` > `override_cost` > `estimated_cost`; group by `campaign_slug`, sum cost\u002Fagents\u002Fminutes, compute grand total\n- Live session: read `.planning\u002Ftelemetry\u002Fcost-tracker-state.json` for burn rate\n- Label real data \"(real)\" and estimates \"(est)\"\n\n**Fleet Sessions:**\n- Glob `.planning\u002Ffleet\u002Fsession-*.md`\n- For each file, read the first 30 lines to extract:\n  - `status:` field\n  - `wave:` or wave number\n  - `agents:` or agent count\n\n**Recent Telemetry:**\n- Read last 50 lines of `.planning\u002Ftelemetry\u002Fhook-timing.jsonl` (if it exists)\n- Read last 50 lines of `.planning\u002Ftelemetry\u002Faudit.jsonl` (if it exists)\n- Merge and sort by timestamp (descending). Take the 10 most recent entries.\n- For each entry: extract `ts` (or `timestamp`), `hook` (or `event`), and a\n  short description field. Format as relative time.\n\n**Recent Hook Activity (separate from general telemetry):**\n- Read last 20 lines of `.planning\u002Ftelemetry\u002Fhook-timing.jsonl`\n- For `event: \"timing\"` entries: extract `hook`, `duration_ms`, `timestamp` (relative), and `outcome` (pass if no matching error in hook-errors.jsonl within 1s; block if a block entry exists)\n- For `event: \"counter\"` entries: extract metric name as the \"event\" column with count context\n\n**Hook Overhead (timing percentiles):**\n- Read all of `.planning\u002Ftelemetry\u002Fhook-timing.jsonl` (if it exists)\n- Keep only entries with a numeric `duration_ms`; group by `hook`\n- Per hook compute: count, p50, p95, max (nearest-rank percentile over the sorted durations)\n- Sort rows by p95 descending\n- If the file is missing or contains no timed entries, render the one-line note instead\n\n**Routine Quota (account-wide 15 runs \u002F 24h cap):**\n- Read `.planning\u002Ftelemetry\u002Froutine-runs.jsonl` (if it exists)\n- Expected JSONL shape, one record per quota-consuming run:\n  `{\"ts\": \"\u003CISO timestamp>\", \"kind\": \"RemoteTrigger\" | \"CronCreate\" | \"ScheduleWakeup\"}`\n- Count records with `ts` inside the last 24 hours; compare against the cap of 15\n- Warn when the count exceeds 12 (hitting the cap pauses every routine on the\n  account; see `docs\u002FROUTINE-QUOTA.md`)\n- The harness does not write this file automatically yet — remote-run logging\n  populates it when a routine mechanism is actually used. Local runners\n  (`local-watch.js`, `local-daemon.js`, `local-schedule.js`) never consume quota\n  and must not be counted.\n\n**Pending Queues:**\n- Count actionable entries in `.planning\u002Ftelemetry\u002Fdoc-sync-queue.jsonl` where `status` is `pending` or `needs-review` (or 0 if missing)\n- Count lines in `.planning\u002Ftelemetry\u002Fmerge-check-queue.jsonl` (or 0 if missing)\n- Count files in `.planning\u002Fintake\u002F` (or 0 if missing)\n\n**Hook Value Data (for HOOKS VALUE section):**\n- Read `.planning\u002Ftelemetry\u002Fhook-errors.jsonl` (if it exists, last 200 lines)\n  - Count entries where `hook` = \"protect-files\" (blocked file access)\n  - Count entries where `hook` = \"external-action-gate\" (gated external actions)\n  - Count entries where `hook` = \"quality-gate\" (quality violations)\n- Read `.planning\u002Ftelemetry\u002Fhook-timing.jsonl` (if it exists, last 200 lines)\n  - Count entries where `hook` = \"circuit-breaker\" and `metric` = \"trips\"\n  - Count total entries from today (entries containing today's ISO date prefix)\n- Read `.planning\u002Ftelemetry\u002Faudit.jsonl` (if it exists, last 200 lines)\n  - Count entries mentioning \"circuit-breaker\" or \"circuit_breaker\"\n\n**Hook Problem Taxonomy:**\n- Read last 100 entries from `.planning\u002Ftelemetry\u002Fhook-errors.jsonl`.\n- Classify `protect-files` blocks and hard `external-action-gate` blocks as\n  `safety-block` with `info` severity; they prove protection fired and do not\n  create a repair action by themselves.\n- Classify `error` and `parse-fail` actions as `hook-failure` with `high`\n  severity; these are actionable.\n- Classify `blocked-restricted` as `restricted-scope-block` with `high`\n  severity; this is actionable.\n- Classify `first-encounter` and `consent-block` from `external-action-gate` as\n  `approval-needed` with `medium` severity; this is actionable.\n- If an `external-action-gate` approval entry has a later matching\n  `tool-call` entry in `audit.jsonl`, classify it as `resolved-approval` with\n  `info` severity; it should not create a repair action. Treat `git push -u`\n  and `git push` as equivalent for the same branch, and allow a small\n  near-simultaneous timestamp skew between hook and tool-call entries.\n- If an unresolved external approval entry is older than 15 minutes, classify\n  it as `stale-approval` with `low` severity; it should not create a current\n  repair action.\n- Classify entries older than 24 hours as `stale` with `low` severity and do\n  not create a repair action from stale entries.\n- The `\u002Ftelemetry` repair action should appear only when actionable entries are\n  present. Safety blocks remain visible in PROBLEMS and HOOKS VALUE.\n\n**Health:**\n- Count circuit breaker entries from audit.jsonl (from hook value data above)\n- Count total lines in `.planning\u002Ftelemetry\u002Faudit.jsonl` written today\n- Count entries in `hooks` array of `.claude\u002Fhooks-template.json` (or\n  `.claude\u002Fhooks.json` if template not present); use 0 if neither exists\n- Read `.claude\u002Fharness.json` → `trust` object:\n  - `sessions_completed`, `campaigns_completed` counters\n  - Compute level: novice (sessions \u003C 5), familiar (5-19), trusted (20+ with 2+ campaigns)\n  - If `trust.override` is set, use that and note \"(override)\"\n\n### Step 2: FORMAT RELATIVE TIMESTAMPS\n\nConvert ISO timestamps: \u003C60s → \"just now\" | \u003C60min → \"{N} min ago\" | \u003C24h → \"{N} hr ago\" | else → \"{N} days ago\". Display unparseable timestamps as-is.\n\n### Step 3: RENDER DASHBOARD\n\nOutput verbatim, substituting real values. Always show section headers even when content is \"(none active)\".\n\n```\n=== Citadel Dashboard ===\nAs of: {relative timestamp of most recent event, or \"now\"}\n\nNEXT ACTION\n  Command: {exact command}\n  Why: {why this is next}\n  Confidence: {low | medium | high}\n  Repair available: {yes | no}\n  Runbook: {docs or skill path}\n\nREPAIR CONSOLE\n  {repair|review} | {confidence} | {label}\n    command: {exact command}\n    why: {short reason}\n    runbook: {docs or skill path}\n\nCAMPAIGNS\n  {slug}: Phase {N}\u002F{total} — {direction, max 60 chars, ellipsis if truncated}\n  Last event: {most recent telemetry entry for this campaign, or \"no telemetry\"}\n  (none active)\n\nCOSTS\n  This session: ${cost} | {duration} min | ${rate}\u002Fmin | {messages} msgs | {agents} agents\n  Today:        ${today_total} across {today_sessions} sessions\n  All time:     ${all_time_total} across {all_time_sessions} sessions ({data_source})\n\n  By campaign:\n    {slug}: ${total_cost} across {sessions} sessions ({agents} agents, {minutes} min)\n    _unattached: ${total_cost} across {sessions} sessions\n  (no cost data recorded yet)\n\nROUTINE QUOTA\n  Runs (last 24h): {N}\u002F15\n  WARNING: {N} of 15 routine runs used in the last 24h. Hitting the cap pauses every routine on the account. See docs\u002FROUTINE-QUOTA.md.\n  (remote-run logging populates .planning\u002Ftelemetry\u002Froutine-runs.jsonl - local runners do not consume quota)\n\nHOOKS VALUE\n  Circuit breaker: {N} trips (prevented token spirals)\n  Quality gate:    {N} violations caught pre-commit\n  Protect-files:   {N} blocks (path traversal, secrets)\n  External gate:   {N} actions gated\n  Total hook fires today: {N}\n  (raw facts only -- no inflated savings claims)\n\nFLEET SESSIONS\n  {slug}: Wave {N} — {agent count} agents — {status}\n  (none active)\n\nRECENT ACTIVITY (last 10 events)\n  {relative time} | {hook\u002Fevent name} | {description}\n  (no telemetry recorded yet)\n\nHOOK ACTIVITY (last 10 hook fires)\n  {relative time} | {hook name} | {duration_ms}ms | {outcome: pass\u002Fblock\u002Fwarn}\n  (no hook timing recorded yet — set CITADEL_DEBUG=true in settings.json for verbose output)\n\nHOOK OVERHEAD (sorted by p95 descending)\n  hook                        count      p50      p95      max\n  {hook name}                   {N}   {N}ms    {N}ms    {N}ms\n  (no hook timing data recorded yet)\n\nPROBLEMS\n  Actionable: {N} | Safety blocks: {N} | Resolved approvals: {N} | Stale: {N}\n  {relative time} | {severity} | {category} | {hook name} | {description}\n  (none recorded)\n\nPENDING\n  Doc sync:     {N} items queued\n  Merge reviews: {N} items queued\n  Intake items:  {N} in .planning\u002Fintake\u002F\n\nHEALTH\n  Circuit breaker trips this session: {N}\n  Audit entries today:                {N}\n  Hooks installed:                    {N}\n  Operator tier:                      {novice | familiar | trusted} ({N} sessions, {N} campaigns)\n\nQUICK COMMANDS\n  \u002Fdo continue    — resume active campaign\n  \u002Fdo rollback    — restore last checkpoint\n  \u002Ftelemetry      — cost breakdown, hook activity, telemetry settings\n  \u002Ftriage prs     — review open PRs\n  \u002Fpr-watch       — watch PR CI\n  \u002Flearn          — extract patterns from last completed campaign\n```\n\n### Step 4: FRINGE CASE HANDLING\n\n**`.planning\u002F` missing:** All zeros, \"(none active)\"; add \"Run \u002Fdo setup --express to initialize.\"\n**harness.json missing or malformed:** Show \"not configured\" for hooks count; do not crash.\n**Malformed campaign file:** Skip it; note `(N campaign file(s) skipped — malformed)`.\n**Large telemetry files:** Read last 50 lines only.\n**Missing timestamps:** Fall back to file modification time; display entry without timestamp if unavailable.\n**All campaigns completed:** Note \"No active campaigns\" at top of CAMPAIGNS section.\n**Completed campaign still active:** Show the exact `node scripts\u002Fcampaign.js complete \u003Cslug> --archive` repair command; suggesting `\u002Fdo continue` here is wrong because the campaign is already finished.\n**Campaign ready for review package:** Show the exact `node scripts\u002Fpackage-delivery.js \u003Cslug>` repair command before showing campaign completion.\n**All fleet sessions idle:** Note \"No active fleet sessions\" under FLEET SESSIONS.\n**routine-runs.jsonl missing or no runs in window:** Show `Runs (last 24h): 0\u002F15` plus the one-line population hint; only show the WARNING line when more than 12 runs are counted.\n**Mixed state:** Proceed with whatever state exists; note each missing directory inline.\n**Doc-sync backlog:** Surface `\u002Flearn --doc-sync` as a repair action with `skills\u002Flearn\u002FSKILL.md` as runbook.\n**Dirty worktree:** Surface `git status --short` as a review action; do not suggest destructive cleanup.\n**Only safety blocks recorded:** Show them in PROBLEMS and HOOKS VALUE, but do not surface `\u002Ftelemetry` as NEXT ACTION.\n**Actionable hook problem recorded:** Surface `\u002Ftelemetry` as repair action with `skills\u002Ftelemetry\u002FSKILL.md` as runbook.\n\n## Contextual Gates\n\n**Disclosure:** \"Displaying harness dashboard. No files modified.\"\n**Reversibility:** green — read-only; no files modified\n**Trust gates:**\n- Any: view the full dashboard\n\n## Quality Gates\n\n- Dashboard must render even when all state files are missing\n- Never display raw JSON to the user — always parse and format\n- Relative timestamps required — never show raw ISO strings in output\n- Campaign direction truncated to 60 chars with \"...\" if longer\n- NEXT ACTION must include command, why, confidence, repair availability, and runbook when known\n- REPAIR CONSOLE must list actionable repairs before raw activity logs\n- Safety blocks must not be treated as urgent repairs unless paired with an actionable hook failure, approval, or restricted-scope block\n- Total output must be skimmable in under 30 seconds\n\n## Exit Protocol\n\n\u002Fdashboard does not produce a HANDOFF block. It is a read-only observability\ntool. After displaying the dashboard, wait for the next user command.\n","# \u002Fdashboard — Harness Observability Dashboard\n\n## When to Use\n\n- \"What's happening?\" \u002F \"Status?\" \u002F \"What's going on?\"\n- \"Show activity\" \u002F \"Show me the dashboard\"\n- After returning to a project after time away\n- When \u002Fdo routes \"status\", \"dashboard\", \"what's happening\", \"what's going on\", \"show activity\"\n- Directly: `\u002Fdashboard`\n\n## Inputs\n\nNone required. Works with whatever state exists on disk.\n\n## Protocol\n\n### Step 0: RUN DASHBOARD IMPLEMENTATION\n\nRun the local dashboard implementation from the project root:\n\n```bash\nnode scripts\u002Fdashboard.js\n```\n\nIf the package scripts are available, this equivalent command is also valid:\n\n```bash\nnpm run dashboard\n```\n\nThe script is read-only. It renders a user-facing control-plane snapshot from\n`.planning\u002F`, telemetry, hook config, coordination state, worktrees, and cost\ndata. Use the manual collection protocol below only as a fallback if the script\nis missing or fails in the current project.\n\n### Step 1: COLLECT STATE\n\nRead the following sources. Each is optional — if a file or directory doesn't\nexist, treat it as empty. Never crash on missing state.\n\n**Campaigns:**\n- Glob `.planning\u002Fcampaigns\u002F*.md`\n- For each file, read the first 40 lines to extract:\n  - `Status:` field\n  - `Direction:` field (truncate to 60 chars)\n  - Phase progress (search for `Phase N of M` or `## Phase` headings)\n  - Most recent line starting with `- [` from the Decision Log\n- If all phases are complete but status is still active, report\n  `needs-completion` and show:\n  `node scripts\u002Fcampaign.js complete \u003Cslug> --archive`\n- If a campaign is marked completed but still lives in `.planning\u002Fcampaigns\u002F`,\n  report `needs-archive` and show the same archive command.\n- If prior build\u002Fverify phases are complete but the `review-package` Exit\n  Evidence row is still pending, missing, or points at a missing local package,\n  report a repair before campaign completion:\n  `node scripts\u002Fpackage-delivery.js \u003Cslug>`\n\n**Cost Data (two sources, prefer real):**\n\n- Primary: run `node scripts\u002Fsession-tokens.js --today` and `--all` — reads Claude Code's native session JSONL for exact token counts\n- Fallback: read `.planning\u002Ftelemetry\u002Fsession-costs.jsonl`; cost priority `real_cost` > `override_cost` > `estimated_cost`; group by `campaign_slug`, sum cost\u002Fagents\u002Fminutes, compute grand total\n- Live session: read `.planning\u002Ftelemetry\u002Fcost-tracker-state.json` for burn rate\n- Label real data \"(real)\" and estimates \"(est)\"\n\n**Fleet Sessions:**\n- Glob `.planning\u002Ffleet\u002Fsession-*.md`\n- For each file, read the first 30 lines to extract:\n  - `status:` field\n  - `wave:` or wave number\n  - `agents:` or agent count\n\n**Recent Telemetry:**\n- Read last 50 lines of `.planning\u002Ftelemetry\u002Fhook-timing.jsonl` (if it exists)\n- Read last 50 lines of `.planning\u002Ftelemetry\u002Faudit.jsonl` (if it exists)\n- Merge and sort by timestamp (descending). Take the 10 most recent entries.\n- For each entry: extract `ts` (or `timestamp`), `hook` (or `event`), and a\n  short description field. Format as relative time.\n\n**Recent Hook Activity (separate from general telemetry):**\n- Read last 20 lines of `.planning\u002Ftelemetry\u002Fhook-timing.jsonl`\n- For `event: \"timing\"` entries: extract `hook`, `duration_ms`, `timestamp` (relative), and `outcome` (pass if no matching error in hook-errors.jsonl within 1s; block if a block entry exists)\n- For `event: \"counter\"` entries: extract metric name as the \"event\" column with count context\n\n**Hook Overhead (timing percentiles):**\n- Read all of `.planning\u002Ftelemetry\u002Fhook-timing.jsonl` (if it exists)\n- Keep only entries with a numeric `duration_ms`; group by `hook`\n- Per hook compute: count, p50, p95, max (nearest-rank percentile over the sorted durations)\n- Sort rows by p95 descending\n- If the file is missing or contains no timed entries, render the one-line note instead\n\n**Routine Quota (account-wide 15 runs \u002F 24h cap):**\n- Read `.planning\u002Ftelemetry\u002Froutine-runs.jsonl` (if it exists)\n- Expected JSONL shape, one record per quota-consuming run:\n  `{\"ts\": \"\u003CISO timestamp>\", \"kind\": \"RemoteTrigger\" | \"CronCreate\" | \"ScheduleWakeup\"}`\n- Count records with `ts` inside the last 24 hours; compare against the cap of 15\n- Warn when the count exceeds 12 (hitting the cap pauses every routine on the\n  account; see `docs\u002FROUTINE-QUOTA.md`)\n- The harness does not write this file automatically yet — remote-run logging\n  populates it when a routine mechanism is actually used. Local runners\n  (`local-watch.js`, `local-daemon.js`, `local-schedule.js`) never consume quota\n  and must not be counted.\n\n**Pending Queues:**\n- Count actionable entries in `.planning\u002Ftelemetry\u002Fdoc-sync-queue.jsonl` where `status` is `pending` or `needs-review` (or 0 if missing)\n- Count lines in `.planning\u002Ftelemetry\u002Fmerge-check-queue.jsonl` (or 0 if missing)\n- Count files in `.planning\u002Fintake\u002F` (or 0 if missing)\n\n**Hook Value Data (for HOOKS VALUE section):**\n- Read `.planning\u002Ftelemetry\u002Fhook-errors.jsonl` (if it exists, last 200 lines)\n  - Count entries where `hook` = \"protect-files\" (blocked file access)\n  - Count entries where `hook` = \"external-action-gate\" (gated external actions)\n  - Count entries where `hook` = \"quality-gate\" (quality violations)\n- Read `.planning\u002Ftelemetry\u002Fhook-timing.jsonl` (if it exists, last 200 lines)\n  - Count entries where `hook` = \"circuit-breaker\" and `metric` = \"trips\"\n  - Count total entries from today (entries containing today's ISO date prefix)\n- Read `.planning\u002Ftelemetry\u002Faudit.jsonl` (if it exists, last 200 lines)\n  - Count entries mentioning \"circuit-breaker\" or \"circuit_breaker\"\n\n**Hook Problem Taxonomy:**\n- Read last 100 entries from `.planning\u002Ftelemetry\u002Fhook-errors.jsonl`.\n- Classify `protect-files` blocks and hard `external-action-gate` blocks as\n  `safety-block` with `info` severity; they prove protection fired and do not\n  create a repair action by themselves.\n- Classify `error` and `parse-fail` actions as `hook-failure` with `high`\n  severity; these are actionable.\n- Classify `blocked-restricted` as `restricted-scope-block` with `high`\n  severity; this is actionable.\n- Classify `first-encounter` and `consent-block` from `external-action-gate` as\n  `approval-needed` with `medium` severity; this is actionable.\n- If an `external-action-gate` approval entry has a later matching\n  `tool-call` entry in `audit.jsonl`, classify it as `resolved-approval` with\n  `info` severity; it should not create a repair action. Treat `git push -u`\n  and `git push` as equivalent for the same branch, and allow a small\n  near-simultaneous timestamp skew between hook and tool-call entries.\n- If an unresolved external approval entry is older than 15 minutes, classify\n  it as `stale-approval` with `low` severity; it should not create a current\n  repair action.\n- Classify entries older than 24 hours as `stale` with `low` severity and do\n  not create a repair action from stale entries.\n- The `\u002Ftelemetry` repair action should appear only when actionable entries are\n  present. Safety blocks remain visible in PROBLEMS and HOOKS VALUE.\n\n**Health:**\n- Count circuit breaker entries from audit.jsonl (from hook value data above)\n- Count total lines in `.planning\u002Ftelemetry\u002Faudit.jsonl` written today\n- Count entries in `hooks` array of `.claude\u002Fhooks-template.json` (or\n  `.claude\u002Fhooks.json` if template not present); use 0 if neither exists\n- Read `.claude\u002Fharness.json` → `trust` object:\n  - `sessions_completed`, `campaigns_completed` counters\n  - Compute level: novice (sessions \u003C 5), familiar (5-19), trusted (20+ with 2+ campaigns)\n  - If `trust.override` is set, use that and note \"(override)\"\n\n### Step 2: FORMAT RELATIVE TIMESTAMPS\n\nConvert ISO timestamps: \u003C60s → \"just now\" | \u003C60min → \"{N} min ago\" | \u003C24h → \"{N} hr ago\" | else → \"{N} days ago\". Display unparseable timestamps as-is.\n\n### Step 3: RENDER DASHBOARD\n\nOutput verbatim, substituting real values. Always show section headers even when content is \"(none active)\".\n\n```\n=== Citadel Dashboard ===\nAs of: {relative timestamp of most recent event, or \"now\"}\n\nNEXT ACTION\n  Command: {exact command}\n  Why: {why this is next}\n  Confidence: {low | medium | high}\n  Repair available: {yes | no}\n  Runbook: {docs or skill path}\n\nREPAIR CONSOLE\n  {repair|review} | {confidence} | {label}\n    command: {exact command}\n    why: {short reason}\n    runbook: {docs or skill path}\n\nCAMPAIGNS\n  {slug}: Phase {N}\u002F{total} — {direction, max 60 chars, ellipsis if truncated}\n  Last event: {most recent telemetry entry for this campaign, or \"no telemetry\"}\n  (none active)\n\nCOSTS\n  This session: ${cost} | {duration} min | ${rate}\u002Fmin | {messages} msgs | {agents} agents\n  Today:        ${today_total} across {today_sessions} sessions\n  All time:     ${all_time_total} across {all_time_sessions} sessions ({data_source})\n\n  By campaign:\n    {slug}: ${total_cost} across {sessions} sessions ({agents} agents, {minutes} min)\n    _unattached: ${total_cost} across {sessions} sessions\n  (no cost data recorded yet)\n\nROUTINE QUOTA\n  Runs (last 24h): {N}\u002F15\n  WARNING: {N} of 15 routine runs used in the last 24h. Hitting the cap pauses every routine on the account. See docs\u002FROUTINE-QUOTA.md.\n  (remote-run logging populates .planning\u002Ftelemetry\u002Froutine-runs.jsonl - local runners do not consume quota)\n\nHOOKS VALUE\n  Circuit breaker: {N} trips (prevented token spirals)\n  Quality gate:    {N} violations caught pre-commit\n  Protect-files:   {N} blocks (path traversal, secrets)\n  External gate:   {N} actions gated\n  Total hook fires today: {N}\n  (raw facts only -- no inflated savings claims)\n\nFLEET SESSIONS\n  {slug}: Wave {N} — {agent count} agents — {status}\n  (none active)\n\nRECENT ACTIVITY (last 10 events)\n  {relative time} | {hook\u002Fevent name} | {description}\n  (no telemetry recorded yet)\n\nHOOK ACTIVITY (last 10 hook fires)\n  {relative time} | {hook name} | {duration_ms}ms | {outcome: pass\u002Fblock\u002Fwarn}\n  (no hook timing recorded yet — set CITADEL_DEBUG=true in settings.json for verbose output)\n\nHOOK OVERHEAD (sorted by p95 descending)\n  hook                        count      p50      p95      max\n  {hook name}                   {N}   {N}ms    {N}ms    {N}ms\n  (no hook timing data recorded yet)\n\nPROBLEMS\n  Actionable: {N} | Safety blocks: {N} | Resolved approvals: {N} | Stale: {N}\n  {relative time} | {severity} | {category} | {hook name} | {description}\n  (none recorded)\n\nPENDING\n  Doc sync:     {N} items queued\n  Merge reviews: {N} items queued\n  Intake items:  {N} in .planning\u002Fintake\u002F\n\nHEALTH\n  Circuit breaker trips this session: {N}\n  Audit entries today:                {N}\n  Hooks installed:                    {N}\n  Operator tier:                      {novice | familiar | trusted} ({N} sessions, {N} campaigns)\n\nQUICK COMMANDS\n  \u002Fdo continue    — resume active campaign\n  \u002Fdo rollback    — restore last checkpoint\n  \u002Ftelemetry      — cost breakdown, hook activity, telemetry settings\n  \u002Ftriage prs     — review open PRs\n  \u002Fpr-watch       — watch PR CI\n  \u002Flearn          — extract patterns from last completed campaign\n```\n\n### Step 4: FRINGE CASE HANDLING\n\n**`.planning\u002F` missing:** All zeros, \"(none active)\"; add \"Run \u002Fdo setup --express to initialize.\"\n**harness.json missing or malformed:** Show \"not configured\" for hooks count; do not crash.\n**Malformed campaign file:** Skip it; note `(N campaign file(s) skipped — malformed)`.\n**Large telemetry files:** Read last 50 lines only.\n**Missing timestamps:** Fall back to file modification time; display entry without timestamp if unavailable.\n**All campaigns completed:** Note \"No active campaigns\" at top of CAMPAIGNS section.\n**Completed campaign still active:** Show the exact `node scripts\u002Fcampaign.js complete \u003Cslug> --archive` repair command; suggesting `\u002Fdo continue` here is wrong because the campaign is already finished.\n**Campaign ready for review package:** Show the exact `node scripts\u002Fpackage-delivery.js \u003Cslug>` repair command before showing campaign completion.\n**All fleet sessions idle:** Note \"No active fleet sessions\" under FLEET SESSIONS.\n**routine-runs.jsonl missing or no runs in window:** Show `Runs (last 24h): 0\u002F15` plus the one-line population hint; only show the WARNING line when more than 12 runs are counted.\n**Mixed state:** Proceed with whatever state exists; note each missing directory inline.\n**Doc-sync backlog:** Surface `\u002Flearn --doc-sync` as a repair action with `skills\u002Flearn\u002FSKILL.md` as runbook.\n**Dirty worktree:** Surface `git status --short` as a review action; do not suggest destructive cleanup.\n**Only safety blocks recorded:** Show them in PROBLEMS and HOOKS VALUE, but do not surface `\u002Ftelemetry` as NEXT ACTION.\n**Actionable hook problem recorded:** Surface `\u002Ftelemetry` as repair action with `skills\u002Ftelemetry\u002FSKILL.md` as runbook.\n\n## Contextual Gates\n\n**Disclosure:** \"Displaying harness dashboard. No files modified.\"\n**Reversibility:** green — read-only; no files modified\n**Trust gates:**\n- Any: view the full dashboard\n\n## Quality Gates\n\n- Dashboard must render even when all state files are missing\n- Never display raw JSON to the user — always parse and format\n- Relative timestamps required — never show raw ISO strings in output\n- Campaign direction truncated to 60 chars with \"...\" if longer\n- NEXT ACTION must include command, why, confidence, repair availability, and runbook when known\n- REPAIR CONSOLE must list actionable repairs before raw activity logs\n- Safety blocks must not be treated as urgent repairs unless paired with an actionable hook failure, approval, or restricted-scope block\n- Total output must be skimmable in under 30 seconds\n\n## Exit Protocol\n\n\u002Fdashboard does not produce a HANDOFF block. It is a read-only observability\ntool. After displaying the dashboard, wait for the next user command.\n",{"name":5,"license":15,"description":7,"auto-trigger":20,"last-updated":24,"user-invocable":25,"trigger_keywords":26},1774483200000,true,[5,27,28,29,30,31],"what's happening","what's going on","show activity","harness state","show me status","main","49119fa06efc769f502bede04ad99746ac20f021","skills\u002Fdashboard",0,"https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits\u002FCITADEL","https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits","2nd-yr EEE 📍 Bangalore | Python, C, Java, C# | ML, NLP & Flask backends | Building AI tools that ship 🚀 | Open to hackathons & collabs","2026-11-14 14:46:28",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":25},[42,45,48],{"tool":43,"command":44},"npx","npx skills add mayankjain1815-commits\u002FCITADEL --skill dashboard",{"tool":46,"command":47},"bunx","bunx skills add mayankjain1815-commits\u002FCITADEL --skill dashboard",{"tool":49,"command":50},"pnpm","pnpm dlx skills add mayankjain1815-commits\u002FCITADEL --skill dashboard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits\u002FCITADEL\u002Fblob\u002Fmain\u002Fskills\u002Fdashboard\u002FSKILL.md",[53,59,63],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"__benchmarks__\u002Factive-campaign.md","REFERENCE","参考文档",833,"https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits\u002FCITADEL\u002Fblob\u002Fmain\u002Fskills\u002Fdashboard\u002F__benchmarks__\u002Factive-campaign.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"__benchmarks__\u002Fno-planning-dir.md",977,"https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits\u002FCITADEL\u002Fblob\u002Fmain\u002Fskills\u002Fdashboard\u002F__benchmarks__\u002Fno-planning-dir.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"__benchmarks__\u002Fvague-status-phrase.md",817,"https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits\u002FCITADEL\u002Fblob\u002Fmain\u002Fskills\u002Fdashboard\u002F__benchmarks__\u002Fvague-status-phrase.md",[68,75,82,89,96,103],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79XH1DBMXQEF9N0Q6NW7Q5P","workspace","Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.","https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits\u002FCITADEL\u002Fblob\u002Fmain\u002Fskills\u002Fworkspace\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79XGWJJHSKNTH78TNVX09VK","wiki","Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to ~400K words.","https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits\u002FCITADEL\u002Fblob\u002Fmain\u002Fskills\u002Fwiki\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79XGNW2YTFHVMEZGZDEDN43","watch","File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through \u002Fdo. Use for automatic reactions to file changes; do NOT use for one-off inspection or tasks needing human judgment per file.","https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits\u002FCITADEL\u002Fblob\u002Fmain\u002Fskills\u002Fwatch\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79XGHZ0028HDW7SDT186D6Q","verify","Self-test the Citadel hook pipeline from within a live session. Exercises real tool calls (Write, Edit, Bash, Read) and checks that hooks fired, telemetry accumulated, and no errors occurred. Reports HOOK HEALTH: PASS or HOOK HEALTH: FAIL with a per-hook breakdown.","https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits\u002FCITADEL\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M79XGDKHMADJXC27T0FMQAN3","unharness","Remove Citadel from a project. Exports valuable state (campaigns, postmortems, research, backlog, discoveries) to docs\u002Fcitadel\u002F as human-readable markdown, then removes all harness files and hooks. The archive is detected by \u002Fdo setup on re-install and offered for restore.","https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits\u002FCITADEL\u002Fblob\u002Fmain\u002Fskills\u002Funharness\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M79XG81A3RHP2TKKBT5WYEY2","triage","GitHub issue and PR investigator. Pulls open issues\u002FPRs, classifies them, searches the codebase for root cause or reviews contributed code, proposes fixes with file:line references, and optionally implements fixes. Use for investigating GitHub issues and reviewing PRs; do NOT use for general code review unrelated to GitHub issues.","https:\u002F\u002Fgithub.com\u002Fmayankjain1815-commits\u002FCITADEL\u002Fblob\u002Fmain\u002Fskills\u002Ftriage\u002FSKILL.md",[],[]]