botmaker
Use when creating specialist Hermes bots.
techjanitor · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add techjanitor/botmaker --skill botmakerAbout this skill
name: botmaker description: "Use when creating specialist Hermes bots." version: 0.2.0 author: techjanitor license: MIT platforms: [linux, macos, windows] metadata: hermes: tags: [hermes, bots, profiles, soul] category: autonomous-ai-agents related_skills: [hermes-agent]
Botmaker
Design, scaffold, certify, and document specialist Hermes bots. Load this skill on every in-scope question. You draft; the child earns. Seeding files is not a bot.
Details: references/soul-craft.md (SOUL + human gate), references/process.md (mechanics), references/vault.md (vault conventions). Shared-skill linker: scripts/link_skill_tree.py. Drift tripwire: scripts/drift_check.py.
When to Use
- Your human wants a new specialist bot, or a SOUL drafted for one — in chat, or as a task card assigned to
botmaker(if your fleet dispatches work by kanban). A card carrying a human-signed SOUL spec satisfies the human gate. - An existing specialist bot's identity/job/voice is wrong and needs a SOUL rewrite (human gate)
Bots/in the vault needs a specialist note, roster row, ormaking-bots.mdchangelog- A shared skill is about to be copied into a profile (stop; symlink files instead)
Don't use for: operating the inference server, ComfyUI, or any service; general coding; rewriting default ~/.hermes/SOUL.md; spawning botmaker-2. @hermes is not the bot coordinator — you are.
Prerequisites
- Hermes CLI (
hermes profile create --help) - Canonical skills live under
~/.hermes/skills/(default Hermes home), not$HERMES_HOME/skillswhen you are the botmaker profile - Vault:
<your-vault-path>(seereferences/vault.md) - Human guide, fleet roster, changelog: vault
Bots/making-bots.md(create it on first ship). Method lives here only; fleet state lives there only — patch a lesson's one owner and log one changelog line.
How to Run
- Interview. Refuse to scaffold until job / independence failure / not-list are sharp. See Procedure.
- Draft a one-screen SOUL (
references/soul-craft.md). Stop. Your human signs it. - Scaffold (
references/process.md). Alias preflight first.--no-skills, pin the brain, file-level skill links, USER.md lockstep sentence if the skill is shared. - Kickoff in the child's Bot Chat. Do not babysit its tools. Do not write its
MEMORY.md. - After certification: vault note + roster row (
references/vault.md). Not before.
Quick Reference
| Need | Do |
|---|---|
| New bot | Alias preflight (Procedure C) → Interview → SOUL draft → human sign-off → hermes profile create NAME --no-skills --description "…" |
| Pin a brain | hermes -p NAME config set model.provider … then model.default …. Then unset the copied base_url / api_key (create copies your default profile's model block, whatever it currently is) |
| Shared skill | Canonical ~/.hermes/skills/<cat>/<name>/; profile files via scripts/link_skill_tree.py. Never a directory symlink. Load linked references/ with read_file on the canonical path |
| Vault after cert | Bots/<name>.md (type: bot-reference), roster row on making-bots.md, one line on Home.md |
| Child memory | Child writes it. You do not. |
Procedure
A. Interview (before any profile create)
Ask, and do not proceed until 1–3 are sharp:
- One-sentence job. If "and also," split into two bots. Job may be a CLI, an HTTP API, a GUI sock — ComfyUI counts. "CLI-only" is how we create the profile, not what the specialist is allowed to operate.
- Failure the brain must survive → model pin (if the bot's job lives on a local box, that usually means a hosted provider — the bot must still think when the box is down).
- What it is not.
- Does default Hermes need the same skill? → canonical under
~/.hermes/skills/+ file-level symlinks. - Who is the client to ping (
@hermes, another specialist, nobody). - Voice: inherit vs write. Inheritance is tone, not the model's stock identity — that is costume unless the bot is a persona bot (if your fleet has one).
B. SOUL draft
Write one screen. Identity (job name first), Job, Hard constraints as their own heading, Voice, What you are not, Disagreement. No live pins, no IPs, no last-incident notes, no "helpful assistant," no pasted stock-model # Style block. Full rules in references/soul-craft.md.
Human gate: do not run hermes profile create until your human signs the draft — chat sign-off or a signed spec on the task card (references/soul-craft.md §Human gate). Iterate in the conversation or on the card, not on disk.
C. Scaffold
Full mechanics and the command sequence: references/process.md. The stop points:
Alias preflight — mandatory, before any profile create NAME. The default alias wrapper can destroy a real CLI through a ~/.local/bin symlink:
zsh -lc 'which -a NAME'
# and, even if which is empty:
test -e "$HOME/.local/bin/NAME" || test -L "$HOME/.local/bin/NAME"
If either finds anything: --no-alias (rationale and the landmines: references/process.md §--no-skills).
--no-skills; never--clone/ desktop clone. Pin the brain, then unset the copiedbase_url/api_key;config get modelmust show onlydefault+provider.- Peers + memory provider — check after every create (site-specific; commands and verification:
references/process.md§Independence). The invariant: every rostered profile has every peer it must reach. Do not print keys. - Sibling-profile CLI from this profile: always prefix
HERMES_HOME=$HOME/.hermes. - By default,
SOUL.mdwrites prompt your human (security.protected_instruction_files: true) — that prompt is the human gate materialized. If your fleet disabled it for headless provisioning (seeprofile/config.yamlin this repo), the signature is the only gate: no human-signed draft or signed spec, no write. If a write is blocked anyway, stop — do not sneak it in via the shell. - Never hand-edit
config.yaml—config set