New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Debug Dashboard

by BlackBeltTechnology in BlackBeltTechnology/pi-agent-dashboard

Diagnose problems in the running pi-agent-dashboard system: server.log, /api/health, bridge WebSocket connectivity, vitest triage, known-issue FAQ entries.

MITAuto-check passedBackend & APIs

Install Debug Dashboard

skills CLI
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill debug-dashboard -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install BlackBeltTechnology/pi-agent-dashboard debug-dashboard --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.pi/skills/debug-dashboard .claude/skills/debug-dashboard && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
debug-dashboard
GitHub stars
316
Token cost
~1.6k tokens
SKILL.md length
583 words
Files
19 (incl. scripts, references)
Skills in repo
66
Repo updated
First seen
Licence
MIT

At a glance

Diagnose problems in the running pi-agent-dashboard system: server.log, /api/health, bridge WebSocket connectivity, vitest triage, known-issue FAQ entries.

  • The server seems hung
  • SKILL.md covers First moves — always run these, When the server is up but…, When tests fail mysteriously and When the UI is the problem, plus 4 more sections
  • Runs TypeScript scripts from its folder; calls npx, node and npm
  • A pi session wont connect

What it does

Debug Dashboard is an agent skill from BlackBeltTechnology/pi-agent-dashboard. Diagnose problems in the running pi-agent-dashboard system: server.log, /api/health, bridge WebSocket connectivity, vitest triage, known-issue FAQ entries. Routes UI/visual issues to the browser skill. Use when the server seems hung, a pi session won't connect, tests fail mysteriously, the dashboard shows a blank page, restart loops, port conflicts, or any "why isn't X working" question.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 20 other files, including scripts and reference files (for example `SKILL.md.AGENTS.md`, `references/isolated-verification.md` and `references/known-issues.md`).

It sits in Backend & APIs, covering Realtime and WebSockets, Unit testing and Help center and FAQ content. It works with Vitest. The repository describes itself as: Real-time web dashboard for pi coding-agent sessions. Multi-session view, live chat mirroring, integrated terminal, diff viewer, pi-flows execution, and mobile-first remote… The licence is MIT.

When your agent uses it

  • The server seems hung
  • A pi session wont connect
  • Tests fail mysteriously
  • The dashboard shows a blank page

Example prompts

  • “why isn”
  • “/debug-dashboard”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit e23e533. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 8 files in scripts/ (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • npx
    • node
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Debug Dashboard loads about 1.6k tokens when it runs, and up to ~8.4k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 583 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from BlackBeltTechnology/pi-agent-dashboard at commit e23e533, republished under its MIT licence (© BlackBeltTechnology). 583 words, ~1,558 tokens.

Download SKILL.mdSave it as .claude/skills/debug-dashboard/SKILL.md (or your agent's skills folder). This skill also uses 18 other files; get the full folder from GitHub.
name
debug-dashboard
description
Diagnose problems in the running pi-agent-dashboard system: server.log, /api/health, bridge WebSocket connectivity, vitest triage, known-issue FAQ entries. Routes UI/visual issues to the browser skill. Use when the server seems hung, a pi session won't connect, tests fail mysteriously, the dashboard shows a blank page, restart loops, port conflicts, or any "why isn't X working" question.

Debug Dashboard

System-level debugging for the running pi-agent-dashboard. Three layers:

mermaid
flowchart TD
  L1["Layer 1 - Is the server alive?<br/>npx tsx ./scripts/health-probe.ts<br/>npx tsx ./scripts/tail-server-log.ts"]
  L2["Layer 2 - Are the bridges connecting?<br/>npx tsx ./scripts/list-sessions.ts<br/>npx tsx ./scripts/tail-server-log.ts --errors"]
  L3["Layer 3 - Is the UI rendering?<br/>(use the browser skill)"]
  L1 --> L2 --> L3

First moves — always run these

bash
npx tsx ./scripts/health-probe.ts        # mode + uptime + version, or "not-running"
npx tsx ./scripts/tail-server-log.ts     # last 50 lines of current run
npx tsx ./scripts/list-sessions.ts       # connected pi sessions via REST

Scripts are TypeScript (cross-platform). All invocations use npx tsx so they work on Linux, macOS, and Windows. tsx is already a project dep.

If health-probe says "not-running" → server isn't up. Check server.log for the most recent start banner ([bootstrap] ready ...) and what came after. The log appends with timestamped headers per start, so the last banner block is the relevant one.

When the server is up but misbehaving

SymptomLikely causeWhere to look
Restart loopsStale port held by zombie, or restart racing with bridge auto-startlsof -i :8000, then pi-dashboard stop (kills owned port holders, not just PID; --force is a dangerous last resort, see known-issues.md)
EADDRINUSE on startConcurrent spawn from multiple pi sessionsHarmless — losing process exits silently. Check log.
Bridge connects then disconnectsserver_restarting broadcast active, or version skewgrep server_restarting in server.log; check /api/health for version
Blank page in browserVite not running in dev mode (silent fallback to prod build); or auth blockingCheck /api/health.mode; check auth settings
New session won't start / yellow spawn_register_timeout, no cardpi crashed at startup (bad extension) OR host overloadSee references/known-issues.md → "New session won't start" — manual pi --mode rpc run splits crash vs overload
Cannot connect to dashboard server on Electron bootlaunchDashboardServer fell back to process.execPath (Electron GUI binary)See references/known-issues.md → "Electron Node bin selection"
Fastify crashes immediatelyBad Node version (22.0–22.17.x or 24.1–24.2.x per nodejs/node#58515)node --version — must be ≥ 22.18.0

Full known-issue catalogue: references/known-issues.md.

When tests fail mysteriously

Use the tee→grep pattern. Never rerun to inspect — capture once, grep forever:

bash
npx tsx ./scripts/run-tests-triage.ts                 # all tests, tee to OS tmpdir, summarize failures
npx tsx ./scripts/run-tests-triage.ts packages/server # restrict to one package's vitest
npx tsx ./scripts/run-tests-triage.ts -t 'my test'    # by test name

After it finishes, the log lives at:

  • Linux/macOS: /tmp/pi-test.log
  • Windows: %TEMP%\pi-test.log

You can re-grep / re-read with custom patterns; the script prints the absolute path on each run.

Patterns + per-package vitest configs + watch mode are documented in references/test-failure-triage.md.

When the UI is the problem

This skill stops at "the server says X but the UI shows Y". For visual debugging — verifying layouts, screenshotting, hunting console errors, testing responsive breakpoints — switch to the browser skill (shipped by the dashboard bridge extension to every session). Quick pointer: see references/ui-debug.md.

Show full SKILL.md (227 more words)Show less

When you must verify a change without touching the live server

The live :8000 server runs MAIN-repo code — /api/restart never loads worktree edits, and a careless npm run build leaks into packages/client/dist (what live serves). To verify a UI/worktree change or serve a review mockup in full isolation (temp HOME, non-8000 ports, PI_DASHBOARD_NO_MDNS=1), see references/isolated-verification.md.

Log file locations

All log + config files. Worth bookmarking. See references/log-locations.md for the full map.

PathContents
~/.pi/dashboard/server.logDaemon stdout/stderr, append mode, timestamped headers per start
~/.pi/dashboard/server.pidPID file (may be stale; use lsof -i :8000 to confirm)
~/.pi/dashboard/config.jsonLive config (port, piPort, auth, tunnel, plugins)
~/.pi/dashboard/zrok.pidTunnel PID file
~/.pi/dashboard/model-proxy.jsonlModel proxy request log (50 MB rotation)
~/.pi/dashboard/tool-overrides.jsonTool registry overrides
/tmp/pi-test.logLast test run (when you used the tee→grep pattern)
~/.pi/agent/sessions/Per-session pi state

STOP — docs-first gate

Before answering any "how do I X" / "why does Y happen" question:

bash
grep -ni '<keyword>' docs/faq.md docs/*.md README.md

The FAQ already documents most recurring symptoms (Electron Node bin, Fastify crash range, tunnel watchdog, port conflicts). Reading source before grepping docs wastes tokens and risks wrong answers. Per AGENTS.md "STOP — Docs-First Gate".

  • browser — UI/visual issues, screenshots, console errors, responsive testing (Electron + web)
  • implement — back to implementing once the bug is identified
  • pi-dashboard — interact with the dashboard via REST (list sessions, send prompts, abort)
  • ci-troubleshoot — when the problem only shows up in CI
  • code-review — review the fix before committing

© BlackBeltTechnology, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 18 other files (scripts, references) in .pi/skills/debug-dashboard of BlackBeltTechnology/pi-agent-dashboard.

  • SKILL.md
  • SKILL.md.AGENTS.md
  • references/isolated-verification.md
  • references/known-issues.md
  • references/known-issues.md.AGENTS.md
  • references/log-locations.md
  • references/log-locations.md.AGENTS.md
  • references/test-failure-triage.md
  • references/test-failure-triage.md.AGENTS.md
  • references/ui-debug.md
  • references/ui-debug.md.AGENTS.md
  • scripts/health-probe.ts
  • scripts/health-probe.ts.AGENTS.md
  • scripts/list-sessions.ts
  • scripts/list-sessions.ts.AGENTS.md
  • scripts/run-tests-triage.ts
  • scripts/run-tests-triage.ts.AGENTS.md
  • scripts/tail-server-log.ts
  • scripts/tail-server-log.ts.AGENTS.md

Open the folder on GitHubat commit e23e533

Compare with similar skills

Debug Dashboard next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Debug Dashboard compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Debug Dashboard this skillBlackBeltTechnology/pi-agent-dashboard316—~1.6kAutomated safety check: PassMIT
Durable Objectshodgef/apiker1274 repos~1.5kAutomated safety check: PassMIT
Tinystruct Patternsaffaan-m/ECC274k1 repos~3kAutomated safety check: PassMIT
System Bridge Testing Workflowtimmo001/system-bridge356—~843Automated safety check: PassApache-2.0
Coverage CheckAI-Unified-Process/marketplace140—~2.7kAutomated safety check: PassApache-2.0
Olore Msw Latestolorehq/olore103—~460Automated safety check: PassMIT

Similar skills

  • Durable Objects

    hodgef/apiker

    Create and review Cloudflare Durable Objects. An agent skill from hodgef/apiker.

    127 GitHub starsUsed in 4 repos~1.5k tokens
    Backend & APIsAuto-check passed

  • Tinystruct Patterns

    affaan-m/ECC

    Expert guidance for developing with the tinystruct Java framework.

    274k GitHub starsUsed in 1 repo~3k tokens
    Backend & APIsAuto-check passed

  • System Bridge Testing Workflow

    timmo001/system-bridge

    How to test System Bridge - Go table-driven tests and commands, web-client quality checks (lint/typecheck/format, no unit tests), the Chrome DevTools MCP interactive test loop for UI and WebSocket…

    356 GitHub stars~843 tokensUpdated today
    Testing & QAAuto-check passed

  • Coverage Check

    AI-Unified-Process/marketplace

    Audits an already-written use case (UC-XXX) or test case (TC-XXX) against its specification and reports a coverage matrix: which main success scenario steps, alternative flows, business rules…

    140 GitHub stars~2.7k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Olore Msw Latest

    olorehq/olore

    Local MSW (Mock Service Worker) documentation reference (latest).

    103 GitHub stars~460 tokensUpdated today
    Backend & APIsAuto-check passed

  • Test Writing Workflow

    iOfficeAI/AionUi

    Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.

    33k GitHub starsUsed in 1 repo~1.2k tokens
    Testing & QAAuto-check passed

More from BlackBeltTechnology/pi-agent-dashboard

All 66 skills in this repo

  • Browser

    BlackBeltTechnology/pi-agent-dashboard

    Browser automation via the agent-browser CLI. An agent skill from BlackBeltTechnology/pi-agent-dashboard.

    316 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • CI Troubleshoot

    BlackBeltTechnology/pi-agent-dashboard

    Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 11-file workflow taxonomy, affected-test selection, the release pipeline, known failure modes, and how to read gh run logs and…

    316 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Implement

    BlackBeltTechnology/pi-agent-dashboard

    Disciplined implementation in pi-agent-dashboard: the rebuild matrix (extension→reload, server→restart, client→build+restart, openspec-apply→full rebuild) plus the project's code discipline rules.

    316 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Pi Dashboard

    BlackBeltTechnology/pi-agent-dashboard

    Monitor and control the pi-dashboard server. An agent skill from BlackBeltTechnology/pi-agent-dashboard.

    316 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Session To Guideline

    BlackBeltTechnology/pi-agent-dashboard

    Turn a pi session into a Markdown "how-we-did-it" collaboration guideline: reads the session's JSONL transcript and synthesizes a reusable playbook of which prompts worked, what had to be steered…

    316 GitHub stars~3.2k tokensUpdated today
    Auto-check passed

  • Bpmn Package Explorer

    BlackBeltTechnology/pi-agent-dashboard

    Generate, validate and view BPMN 2.0 process packages from a prose description, and render existing .bpmn / .dmn files.

    316 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Debug Dashboard

What does Debug Dashboard do?

Diagnose problems in the running pi-agent-dashboard system: server.log, /api/health, bridge WebSocket connectivity, vitest triage, known-issue FAQ entries. Debug Dashboard is an agent skill from BlackBeltTechnology/pi-agent-dashboard.log, /api/health, bridge WebSocket connectivity, vitest triage, known-issue FAQ entries.

When should I use Debug Dashboard?

Debug Dashboard fits situations like: the server seems hung; A pi session wont connect; tests fail mysteriously; the dashboard shows a blank page.

How do I install Debug Dashboard in Claude Code?

Run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill debug-dashboard -a claude-code`. Or copy the skill folder (.pi/skills/debug-dashboard in BlackBeltTechnology/pi-agent-dashboard) into .claude/skills/debug-dashboard in your project. Claude Code loads it when a task matches its description.

How do I install Debug Dashboard in Codex?

Run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill debug-dashboard -a codex`. Or copy the skill folder (.pi/skills/debug-dashboard in BlackBeltTechnology/pi-agent-dashboard) into .agents/skills/debug-dashboard in your project. Codex loads it when a task matches its description.

Can I use Debug Dashboard in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill debug-dashboard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug-dashboard, .gemini/skills/debug-dashboard, .github/skills/debug-dashboard and .opencode/skills/debug-dashboard in your project.

What does Debug Dashboard need to run?

Going by SKILL.md and its folder, Debug Dashboard needs TypeScript for the scripts in its folder and the command-line tools its instructions call (npx, node and npm). Our summary lists: Node.js.

Does Debug Dashboard access the network?

SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Debug Dashboard safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Debug Dashboard use?

Debug Dashboard is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Debug Dashboard use?

About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.8k tokens, read only when the agent opens those files.

What are the alternatives to Debug Dashboard?

Skills that share tags, products or a category with Debug Dashboard: Durable Objects (hodgef/apiker, 127 stars), Tinystruct Patterns (affaan-m/ECC, 274k stars), System Bridge Testing Workflow (timmo001/system-bridge, 356 stars) and Coverage Check (AI-Unified-Process/marketplace, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debug Dashboard?

BlackBeltTechnology (a GitHub organization) maintains it in BlackBeltTechnology/pi-agent-dashboard, which has 316 GitHub stars. The repository holds 66 skills in this directory. The repository was last updated on October 6, 2026.

Source: BlackBeltTechnology/pi-agent-dashboard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.