nostra124

Operate the `snapshot` per-service backup orchestrator — enable / list / take / restore / push / pull backups for file trees, postgres databases, wireguard configs, and (filed) filesystem-level snapshots. Trigger when the user wants to schedule backups, restore from a prior snapshot, sync backups across accounts, or learn the per-service plugin model.

Build a `.cpk/` container package, declare a host that runs it, and bind that host to a machine in the fleet inventory. Trigger when the user wants to package a service for deployment, set up a new host on a machine in the inventory, or learn the container / hosts / machines separation.

Bring up, move, recover, and tear down container packages running on a fleet of machines. Trigger when the user wants to deploy a host, migrate it between machines or providers, fail over to a replica, snapshot/restore data, walk the fleet dependency graph, or troubleshoot a running deployment.

Drive a fleet upgrade end-to-end: clone production to dev, apply the change, replay in staging against real data, run tests, get user sign-off, promote staging to production, with automatic disaster recovery on failure. Trigger when the user says "upgrade my nextcloud" / "bump postgres to 17" / "test this change against real data before deploying it" / any phrasing that maps to the dev → staging → production pipeline.

The development workflow for rpk packages — the four-directory model, rpk init effects, and when to use stage vs install vs update. Trigger when a coding agent is developing an rpk-packaged project, when asking "where do I edit files?", "how do I test my changes?", or "what does rpk init do?". Use this BEFORE rpk-author when starting development on an existing package.

Turn a git repository into an rpk package by scaffolding the .rpk/ directory. Trigger when the user wants to package a project for rpk, convert a GitHub clone into an rpk package, "make this an rpk package", or add/edit the .rpk/ folder of a repo. Also trigger when the user is inspecting an unfamiliar .rpk/ directory and wants guidance.

Operate the `account` identity foundation — create / inspect / configure system + remote accounts, manage their SSH and GPG keys, query remote endpoints, check online status. Trigger when the user wants to add an identity, share a public key, set up SSH access between accounts, or learn how the `→ account` foundation direction shapes the whole collection.

Operate the `user` system-user manager and per-user sub-service frontend — create/delete/add system users, run sub-services (git, srv, mails, api, shell) per user, install dotfiles/shell config. Trigger when the user wants to add a system user, run a script as another user, or set up shell/dotfiles.

Operate the `config` admin tool — inspect, edit, get, set config files for sibling scripts in the collection. Trigger when the user wants to view or change a script's configuration, reset to defaults, or learn the foundation pattern (each script reads its own config; config is the user-facing front-end).

Operate the `event` scheduler — create, list, fire, and inspect events run by the `eventd` daemon. Events trigger on cron schedules, fixed intervals, file changes (inotify), boot, or manual emit. Trigger when the user wants to schedule a recurring task, react to file changes, run a handler on demand, or inspect the logs of past runs.

Move files into long-term storage with `archive` — date-prefixed filenames, hidden rec-format sidecars carrying sha256 + EXIF + (optional) Bitcoin block- height stamps, deduplication by hash, recutils-based search verbs, and account-scoped sync. Trigger when the user wants to archive scans / receipts / signed PDFs / photos / ebooks, dedup an existing pile, run a reverse-hash lookup, or sync archives across machines.

Compose check files for the `check` infrastructure-as-code tool. Trigger when the user wants to check or fix system state — files, users, services, packages, network, kernel — or learn how the design (educational, functional, decentralized, simple) maps onto a CM idea (ansible, sparrow, mitamae). Use this skill when the user says "write a check", "check that X", "make sure X is true on this host", or asks how to author a `.check` file.

Operate the `repo` personal-git-hosting orchestrator — init / stage / push / pull / sync repository identities across account peers. Trigger when the user wants to create a personal git repo, set up peer sync between machines, work with one of the four repo types (bare / stage / child / clone), or resolve cross-peer conflicts.

Operate the `snapshot` per-service backup orchestrator — enable / list / take / restore / push / pull backups for file trees, postgres databases, wireguard configs, and (filed) filesystem-level snapshots. Trigger when the user wants to schedule backups, restore from a prior snapshot, sync backups across accounts, or learn the per-service plugin model.

Operate the `services` multi-backend supervision frontend — create / start / stop / restart / status / monitor services across daemontools, runit, systemd-user, and launchd. Trigger when the user wants to add a long-running daemon, manage user-mode services, debug a flaky supervisor entry, or learn the shared-run-script abstraction.

Operate the `msync` snapshot-based bidirectional sync tool — sync two paths between machines using a three-way merge. Trigger when the user wants to keep a notes / docs / config directory in sync across two accounts, recover from a sync conflict, or learn the three-way-merge model.