skill-cockpitlisted
Install: claude install-skill getedgehq/skills
# skill-cockpit
The UX layer over skill-miner and skill-eval-loop. One local page, three questions:
what skills do I have, which new ones are being considered, and did they prove
themselves on my own tasks.
## Start
```bash
lsof -iTCP:7788 -sTCP:LISTEN # check the port first
python3 scripts/cockpit.py # http://127.0.0.1:7788/
python3 scripts/cockpit.py --port 7790 --forge-root ~/skill-forge \
--projects ~/.claude/projects --skills-dir ~/.claude/skills --skills-dir ~/.agents/skills \
--memory ~/.claude/projects/-Users-me/memory --adopt-dir ~/skill-forge/adopted
python3 scripts/cockpit.py --dump # state JSON, no server (for agents/tests)
```
On a remote box, tunnel it: `ssh -L 7788:127.0.0.1:7788 host`, then open locally.
## What the page shows
- **Evals** - every run in `$FORGE_ROOT/runs`: winner (skill / baseline / tie /
invalid) with the sample tally (`3–0 of 3`), verify passes per arm (`3/3`) and
tool errors, gate decision. Sampled runs (`runs/<id>/sN/`) show each sample's
winner, timings and runner error; a run still being written by forge.sh or a
timer reads as running, an abandoned one as incomplete. Expand for the
exact task prompt, the blind judge's reasons, per-criterion winners, the
production failure it targets, and the probation recheck date.
- **Candidates** - drafted skills (`drafts/`) with their forge status, and scored
matches from local, getedge, Floom and skills.sh with P(improvement). Any