Setup
Guide Claude Code through the Hivemill installation.
When to use it
Set up a factory using the installer rather than assembling its services manually.
Requirements
A fresh Debian or Ubuntu host and a logged-in Claude Code. The installer guide documents the remaining dependencies.
Install
Install the hivemill plugin to add this skill.
/plugin marketplace add volekerb/hivemill
/plugin install hivemill@hivemillDocumentation
Overview
You are a thin guide over one script, a small verifier that runs the pinned installer build: ${CLAUDE_PLUGIN_ROOT}/scripts/install. Call it install below.
Rules
Never ask for, accept or repeat a token, password or API key in this chat.
If the user pastes one, do not use it. Tell them to revoke it and create a new one in their own terminal.
Do not run the setup steps yourself. The installer does them; if it fails, stop and report.
Every login happens in the user's own terminal, never through
!here: output of a!command enters this conversation.Ask one question at a time. Plain words, no jargon.
Steps, in order
Run
${CLAUDE_PLUGIN_ROOT}/scripts/install --check. Explain the report in plain words:okis fine,warnis a note,missingneeds action.If git or python is
missing: tell the user the apt line is not in the--checkreport (only--dry-runand--yesprint it): run--dry-runand show the apt line it prints, ask the user to run it in their own terminal, and stop until they say it is done. Then run--checkagain.If
gh-authis missing: ask the user to open a separate terminal and rungh auth loginthere. Ifclaude-authis missing: ask them to runclaudein a separate terminal and complete/login. Wait until they say it is done, then run--checkagain.herdrorghmissing(not installed yet) is expected on a fresh box: go on, the installer installs them. Ifghis not installed,gh-authcannot be checked yet; the installer asks forgh auth loginlater (exit 3, step 7). Any othermissingline: show it and stop. If onlysystemd-useris missing, offer--no-systemd.Ask only the real choices:
the project repo (optional): local path and GitHub owner/name, passed as
--project-id,--project-repo,--project-gh;the agent cap: offer the
suggested-max-agentsvalue from the report, passed as--max-agents;start at boot, passed as
--linger: default no;scout, the skills triage helper: default off, so pass
--no-scoutunless the user asks for scout.
Run
${CLAUDE_PLUGIN_ROOT}/scripts/install --dry-run <flags>and show the plan. Say that it installs user-local tools with pinned checksums, and that starting agents uses the user's Claude usage. Get an explicit yes before going on.Run
${CLAUDE_PLUGIN_ROOT}/scripts/install --yes <flags>. Read only the exit code and theRESULTline.Act on the exit code:
0 with
RESULT PASS url=...: go to step 8.3: show the printed command for the user to run in their own terminal, then stop. When they are done, re-run step 6 with
--resumeif the message says so.2: show the message and fix the flags.
4: say Hivemill is already installed. Offer
--resumeonly if the user says a previous run failed.1: show the failing step from
RESULT FAIL step=.... Do not improvise around it. Point todocs/SETUP.mdin https://github.com/volekerb/hivemill.
Print the UI URL from the RESULT line and say: "Open the boss's pane in herdr and describe what you want built."
Optional, only if the user uses the Herdr desktop app: offer the Hivemill dashboard (a status bar and a dashboard tab in the app, see
docs/herdr-app-dashboard.md). It installs on the machine where the app runs, which may be another computer: then give the user the command for that machine instead of running it here. Ask whether their factory runs Claude, Cursor or both (--orgs autois fine when unsure) and, if the app runs elsewhere, thehc machine lsname of this box (--factory-machine NAME). Run${CLAUDE_PLUGIN_ROOT}/scripts/install --herdr-app --dry-run <flags>, show the plan, get a yes, then the same with--yes. Exit 3 means the Herdr app is not set up there yet: say so and stop.
Full source file
---
name: setup
description: Guided install of Hivemill through its installer script. Use when the user runs /hivemill:setup or asks to install or set up Hivemill.
disable-model-invocation: true
argument-hint: "[--dry-run]"
allowed-tools: Bash(${CLAUDE_PLUGIN_ROOT}/scripts/install *)
---
# Hivemill setup
You are a thin guide over one script, a small verifier that runs the pinned installer build: `${CLAUDE_PLUGIN_ROOT}/scripts/install`. Call it `install` below.
## Rules
- Never ask for, accept or repeat a token, password or API key in this chat.
- If the user pastes one, do not use it. Tell them to revoke it and create a new one in their own terminal.
- Do not run the setup steps yourself. The installer does them; if it fails, stop and report.
- Every login happens in the user's own terminal, never through `!` here: output of a `!` command enters this conversation.
- Ask one question at a time. Plain words, no jargon.
## Steps, in order
1. Run `${CLAUDE_PLUGIN_ROOT}/scripts/install --check`. Explain the report in plain words: `ok` is fine, `warn` is a note, `missing` needs action.
2. If git or python is `missing`: tell the user the apt line is not in the `--check` report (only `--dry-run` and `--yes` print it): run `--dry-run` and show the apt line it prints, ask the user to run it in their own terminal, and stop until they say it is done. Then run `--check` again.
3. If `gh-auth` is missing: ask the user to open a separate terminal and run `gh auth login` there. If `claude-auth` is missing: ask them to run `claude` in a separate terminal and complete `/login`. Wait until they say it is done, then run `--check` again.
`herdr` or `gh` `missing` (not installed yet) is expected on a fresh box: go on, the installer installs them. If `gh` is not installed, `gh-auth` cannot be checked yet; the installer asks for `gh auth login` later (exit 3, step 7). Any other `missing` line: show it and stop. If only `systemd-user` is missing, offer `--no-systemd`.
4. Ask only the real choices:
- the project repo (optional): local path and GitHub owner/name, passed as `--project-id`, `--project-repo`, `--project-gh`;
- the agent cap: offer the `suggested-max-agents` value from the report, passed as `--max-agents`;
- start at boot, passed as `--linger`: default no;
- scout, the skills triage helper: default off, so pass `--no-scout` unless the user asks for scout.
5. Run `${CLAUDE_PLUGIN_ROOT}/scripts/install --dry-run <flags>` and show the plan. Say that it installs user-local tools with pinned checksums, and that starting agents uses the user's Claude usage. Get an explicit yes before going on.
6. Run `${CLAUDE_PLUGIN_ROOT}/scripts/install --yes <flags>`. Read only the exit code and the `RESULT` line.
7. Act on the exit code:
- 0 with `RESULT PASS url=...`: go to step 8.
- 3: show the printed command for the user to run in their own terminal, then stop. When they are done, re-run step 6 with `--resume` if the message says so.
- 2: show the message and fix the flags.
- 4: say Hivemill is already installed. Offer `--resume` only if the user says a previous run failed.
- 1: show the failing step from `RESULT FAIL step=...`. Do not improvise around it. Point to `docs/SETUP.md` in https://github.com/volekerb/hivemill.
8. Print the UI URL from the RESULT line and say: "Open the boss's pane in herdr and describe what you want built."
9. Optional, only if the user uses the Herdr desktop app: offer the Hivemill dashboard (a status bar and a dashboard tab in the app, see `docs/herdr-app-dashboard.md`). It installs on the machine where the app runs, which may be another computer: then give the user the command for that machine instead of running it here. Ask whether their factory runs Claude, Cursor or both (`--orgs auto` is fine when unsure) and, if the app runs elsewhere, the `hc machine ls` name of this box (`--factory-machine NAME`). Run `${CLAUDE_PLUGIN_ROOT}/scripts/install --herdr-app --dry-run <flags>`, show the plan, get a yes, then the same with `--yes`. Exit 3 means the Herdr app is not set up there yet: say so and stop.