Start and open the live drydock board (localhost:8642). Use when asked "/drydock:board", "open the board", "show the drydock board", "board status", or "stop the board".
Installs into .claude/skills of the current project.
Are you the author of Board?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/phspagiari-board)
---
name: board
description: Start and open the live drydock board (localhost:8642). Use when asked "/drydock:board", "open the board", "show the drydock board", "board status", or "stop the board".
---
# /drydock:board — dashboard control
> **PLUGIN_HOME**: resolve once per invocation as `realpath <this skill's
> base dir>/../..` (the plugin package root — `board/` lives there).
> **STATE_HOME**: `~/.drydock`, or `$DRYDOCK_STATE_HOME` if set — the queue
> the board reads.
The board is `<PLUGIN_HOME>/board/server.py serve --root <STATE_HOME>` on
`http://localhost:8642` — localhost-only, reads the queue from disk per
request, nothing to regenerate and nothing published. Normally the
orchestrator keeps it alive; this skill is for direct control from any
session.
## Default (`/drydock:board`, "open the board")
1. `curl -sf localhost:8642/healthz` — if it answers `ok`, skip to 3.
2. Down → start it as a background Bash task:
`<PLUGIN_HOME>/board/server.py serve --root <STATE_HOME>`. Re-check
healthz (retry ~2s); if still down, read the task output and report the
error instead of opening a dead page.
3. `open http://localhost:8642` and report one line: board state + queue
counts from `curl -s localhost:8642/api/state` (blocked / ready / active /
inbox).
## `/drydock:board status`
Healthz + the counts line. Don't open the browser.
## `/drydock:board stop`
Find the listener (`lsof -ti :8642`) and kill that PID only — never a broader
`pkill`. Confirm the port is free afterwards. Note that the orchestrator's
housekeeping will restart it on a future tick unless that loop is paused too.
