Always-on agent machine
Say first: "I'll check this machine read-only and prepare any change for you to
run. I won't use sudo, change settings or print secret values."
This skill turns the Main Branch machine guide into jobs an agent can run and
check. The guide is the human document; the references below point to its
sections instead of copying them:
Machine Setup.
No business repo is needed.
Run mb machine doctor first for the current account's read-only baseline.
Use mb machine doctor --json when structured results are needed. Exit 3 means
incomplete verification, not failed verification. Exit 1 means a failed check;
exit 2 means no verdict. Report NOT VERIFIED rows and their reasons. This first
release reads a machine manifest from /etc/mainbranch/machine.json, or the
file given with --manifest. A manifest from --manifest is reported as
caller-selected, so its trust is not verified. Without a manifest the run says
so. Either way, doctor still exits 3 at best, so a run cannot establish full
machine health.
The maintenance rows below still cover checks outside doctor's current scope.
Pick the job
| The operator wants to |
Read |
| Pick hardware, install the OS, finish the first week, move to a new host |
references/setup.md |
| Know what to check today, this week or this month |
references/maintenance.md |
| Add a business, a standing role, a data collector or storage |
references/extension.md |
| Harden the box, or decide on containers, VMs or a second machine |
references/hardening.md |
Read only the reference for the job. If the request spans two, finish one job
and its done-checks before starting the next.
Principles
- The owner steers. You prepare each command and explain it; the owner
reads it and runs anything that needs root, a sign-in or a payment. Never
run
sudo, never complete a sign-in, never change the machine yourself.
- One box for the agents. Agent sessions start on the always-on box. The
laptop and phone only view and steer. If closing the laptop stops work, the
setup isn't finished.
- Isolation by Unix user. One business per Unix user. Several
roles may share one business's account. A hook or rule inside the same user is advisory, not a security
boundary. Accounts reach each other only through the owner until a
reviewed gate exists.
- Backups you've restored. A backup counts only after a restore drill
from it passed. Until then, report backups as NOT VERIFIED.
- Requirements, not commands, for isolation controls. Firewalls, network
fences, process hiding, sandboxes and gates are written as requirements and
expected results. Their commands come from the owner's security reviewer,
never from this skill.
- Start at Checkpoint 1; graduate only on a recorded trigger. One Linux
user per business is the first checkpoint. Containers, VMs or a second
machine come only when a trigger in the hardening reference is recorded
with its evidence.
- Unknown is never a pass. A check you can't run, a reading that is stale
and an owner's word are all NOT VERIFIED. Say which, and why.
Done-checks
Every job ends with a report, one row per check:
| Check |
Result |
Evidence |
Next step |
| Agent account has no admin group |
PASS |
id lists only its own group |
none |
| Restore drill this month |
NOT VERIFIED |
no dated drill in the machine record |
owner runs a drill |
- Result is PASS, FAIL or NOT VERIFIED. Write "NOT VERIFIED (owner
attested)" when only the owner's word supports it.
- Evidence is what you read, summarized: a status word, a mode, a date.
Never paste tokens, keys, passwords, recovery codes or full config files.
- Done for each job means:
- Setup: every first-week step in setup.md is PASS, including the reboot
and lid-closed tests, and the restore test passed before business data
went on the box.
- Maintenance: the daily rows are fresh (read today), weekly and monthly
rows carry dates inside their window, and every FAIL has a next step.
- Extension: the new account, role, collector or drive has its own row in
the machine record and its checks are PASS.
- Hardening: all 14 Checkpoint 1 lines are PASS after a reboot, with the
run dated, or each failing line names its owner and next step.
Run checks as the account they describe: operator-level checks from the
owner's admin session without sudo, and per-account checks as that account.
If a check needs root, prepare it for the owner and report NOT VERIFIED until
they share the result.
The machine record
Keep one record per machine, owned by the admin account and outside every
business repo: the tool index, the restart table, backup layers and drill
dates, collectors, Checkpoint 1 run dates and any recorded graduation trigger.
If it doesn't exist yet, offer to draft it; the owner decides where it lives.
What this skill never does
- Run
sudo, change settings, install software or reboot the machine.
- Write firewall, network-fence, process-hiding, sandbox or gate recipes.
- Read or print secret values, key files, browser profiles or clipboard
history files.
- Read another account's home folder or business data.
- Treat a missing, failed, stale or attested check as a pass.
- Publish the report or send it anywhere. The owner shares it if they want.
1---2name: mb-homelab-machine3description: "Set up, maintain, harden or extend an always-on machine that runs your agents (a mini PC, Mac mini or homelab box). Use whenever the operator asks about picking hardware, installing Ubuntu or Omarchy for agents, the first week on a new box, what to check daily, weekly or monthly, backups and restore drills, disk health, quota or tool checks, adding a business account, a standing agent role, a data collector or a backup drive, Checkpoint 1 hardening, or whether to move to containers, VMs or a second machine. Read-only checks; the owner runs root steps."4loops: [sense, decide, ship]5metadata:6 source: https://skillmd.com/skills/dmthepm/mb-homelab-machine7---89# Always-on agent machine1011Say first: "I'll check this machine read-only and prepare any change for you to12run. I won't use sudo, change settings or print secret values."1314This skill turns the Main Branch machine guide into jobs an agent can run and15check. The guide is the human document; the references below point to its16sections instead of copying them:17[Machine Setup](https://github.com/dmthepm/mainbranch/blob/main/docs/machine-setup.md#part-1-concepts).18No business repo is needed.1920Run `mb machine doctor` first for the current account's read-only baseline.21Use `mb machine doctor --json` when structured results are needed. Exit 3 means22incomplete verification, not failed verification. Exit 1 means a failed check;23exit 2 means no verdict. Report NOT VERIFIED rows and their reasons. This first24release reads a machine manifest from `/etc/mainbranch/machine.json`, or the25file given with `--manifest`. A manifest from `--manifest` is reported as26caller-selected, so its trust is not verified. Without a manifest the run says27so. Either way, doctor still exits 3 at best, so a run cannot establish full28machine health.29The maintenance rows below still cover checks outside doctor's current scope.3031## Pick the job3233| The operator wants to | Read |34| --- | --- |35| Pick hardware, install the OS, finish the first week, move to a new host | [references/setup.md](references/setup.md) |36| Know what to check today, this week or this month | [references/maintenance.md](references/maintenance.md) |37| Add a business, a standing role, a data collector or storage | [references/extension.md](references/extension.md) |38| Harden the box, or decide on containers, VMs or a second machine | [references/hardening.md](references/hardening.md) |3940Read only the reference for the job. If the request spans two, finish one job41and its done-checks before starting the next.4243## Principles44451. **The owner steers.** You prepare each command and explain it; the owner46 reads it and runs anything that needs root, a sign-in or a payment. Never47 run `sudo`, never complete a sign-in, never change the machine yourself.482. **One box for the agents.** Agent sessions start on the always-on box. The49 laptop and phone only view and steer. If closing the laptop stops work, the50 setup isn't finished.513. **Isolation by Unix user.** One business per Unix user. Several52 roles may share one business's account. A hook or rule inside the same user is advisory, not a security53 boundary. Accounts reach each other only through the owner until a54 reviewed gate exists.554. **Backups you've restored.** A backup counts only after a restore drill56 from it passed. Until then, report backups as NOT VERIFIED.575. **Requirements, not commands, for isolation controls.** Firewalls, network58 fences, process hiding, sandboxes and gates are written as requirements and59 expected results. Their commands come from the owner's security reviewer,60 never from this skill.616. **Start at Checkpoint 1; graduate only on a recorded trigger.** One Linux62 user per business is the first checkpoint. Containers, VMs or a second63 machine come only when a trigger in the hardening reference is recorded64 with its evidence.657. **Unknown is never a pass.** A check you can't run, a reading that is stale66 and an owner's word are all NOT VERIFIED. Say which, and why.6768## Done-checks6970Every job ends with a report, one row per check:7172| Check | Result | Evidence | Next step |73| --- | --- | --- | --- |74| Agent account has no admin group | PASS | `id` lists only its own group | none |75| Restore drill this month | NOT VERIFIED | no dated drill in the machine record | owner runs a drill |7677- **Result** is PASS, FAIL or NOT VERIFIED. Write "NOT VERIFIED (owner78 attested)" when only the owner's word supports it.79- **Evidence** is what you read, summarized: a status word, a mode, a date.80 Never paste tokens, keys, passwords, recovery codes or full config files.81- Done for each job means:82 - **Setup:** every first-week step in setup.md is PASS, including the reboot83 and lid-closed tests, and the restore test passed before business data84 went on the box.85 - **Maintenance:** the daily rows are fresh (read today), weekly and monthly86 rows carry dates inside their window, and every FAIL has a next step.87 - **Extension:** the new account, role, collector or drive has its own row in88 the machine record and its checks are PASS.89 - **Hardening:** all 14 Checkpoint 1 lines are PASS after a reboot, with the90 run dated, or each failing line names its owner and next step.9192Run checks as the account they describe: operator-level checks from the93owner's admin session without `sudo`, and per-account checks as that account.94If a check needs root, prepare it for the owner and report NOT VERIFIED until95they share the result.9697## The machine record9899Keep one record per machine, owned by the admin account and outside every100business repo: the tool index, the restart table, backup layers and drill101dates, collectors, Checkpoint 1 run dates and any recorded graduation trigger.102If it doesn't exist yet, offer to draft it; the owner decides where it lives.103104## What this skill never does105106- Run `sudo`, change settings, install software or reboot the machine.107- Write firewall, network-fence, process-hiding, sandbox or gate recipes.108- Read or print secret values, key files, browser profiles or clipboard109 history files.110- Read another account's home folder or business data.111- Treat a missing, failed, stale or attested check as a pass.112- Publish the report or send it anywhere. The owner shares it if they want.