start-board
Skill0 starsChanged 3 months agoMITView on GitHub
Use when the user asks to start, open, stop, or restart the Werkbank board ("starte das Board", "mach das Board auf", "Board neu starten"), or when server code changed and needs a restart.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- create-ticketSkill
- creating-skillsSkill
- documentingSkill
- explaining-complexitySkill
- finding-knowledgeSkill
- git-disciplineSkill
- journalingSkill
- werkbank-work-ticketSkill
- work-ticketsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Stop: systemctl --user stop werkbank-board.service (stays stopped until next login or manual start).
- Very specific: line 23
ALWAYS verify afterwards with curl -s http://127.0.0.1:8765/api/tickets before telling the user anything runs — never claim it unverified.
- Very specific: line 32
Before restarting, finalize any ticket this session holds in in_arbeit (set review) — the startup sweep moves stranded in_arbeit tickets to …
- Very specific: line 43
Do NOT hand-edit host/lan in config.json.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Start the Board
Since WB-34 the board runs as a systemd USER SERVICE (werkbank-board.service,
unit at ~/.config/systemd/user/): it starts at login, restarts itself after
crashes (Restart=always), and binds to the host in config.json
(host, default 127.0.0.1; port default 8765).
Normal operations
- Status:
systemctl --user is-active werkbank-board.service - Start:
systemctl --user start werkbank-board.service - Restart (after changes to server.py/store.py/dispatch.py/config.json):
systemctl --user restart werkbank-board.service— board.html needs NO restart (re-read per GET), reload the page instead. - Stop:
systemctl --user stop werkbank-board.service(stays stopped until next login or manual start). - ALWAYS verify afterwards with
curl -s http://127.0.0.1:8765/api/ticketsbefore telling the user anything runs — never claim it unverified. Logs:journalctl --user -u werkbank-board -n 50(the old /tmp/werkbank-board.log is no longer written).
Restart safety (unchanged rules)
- Dispatched ticket agents must NEVER restart the board (their prompt says so); restarts are for the interactive session only.
- Before restarting, finalize any ticket this session holds in
in_arbeit(set review) — the startup sweep moves stranded in_arbeit tickets to Fehlgeschlagen (handover markers and live chat claims are spared).
Network exposure — user decision only
host: 127.0.0.1 means only this machine. Never open it to the network
without the user's explicit, informed decision: anyone who reaches the board
can read and change tickets, browse folder names, and START AGENT RUNS that
execute commands on this machine. Spell that out first.
Do NOT hand-edit host/lan in config.json. The supported path is
python3 src/werkbank/server.py --set-password and then --lan-on; the board
REFUSES TO START on a network address without a password, so a hand-edit does
not silently expose anything — it just breaks the board's start.
Not on Linux? (macOS, Windows)
systemctl exists only on Linux. The board itself is cross-platform — only the
autostart is not:
- macOS:
python3 src/werkbank/server.pyin a terminal, or alaunchdplist for autostart.setsiddoes not exist there; usenohup python3 src/werkbank/server.py >/tmp/werkbank.log 2>&1 &. - Windows:
py -3 src\werkbank\server.py(orpython). For autostart put a shortcut in the Startup folder (README §6). There is nopython3command and nosetsid.
Everything below about restarting after code changes applies on all three: the
server is one process, board.html is re-read per request (page reload is
enough), server.py / store.py / dispatch.py / config.json need a restart.
Fallback without systemd (unit missing/broken)
(setsid python3 src/werkbank/server.py > /tmp/werkbank-board.log 2>&1 &)
then verify with curl as above.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

