Skip to main content
zombiectl install --from <path> is how you bring an agent up. It reads SKILL.md and TRIGGER.md from the directory you point at, validates them, and uploads to your active workspace. Install is the deploy — there’s no separate up step. 
zombiectl install --from ~/.config/usezombie/samples/platform-ops

✓ platform-ops-agent is live.
  Zombie ID: zmb_2041
  Webhook URLs (register on the upstream provider):
    github: https://api.usezombie.com/v1/webhooks/zmb_2041/github
One URL is printed per declared webhook trigger in TRIGGER.md, keyed by triggers[].source. The host-agent install skill consumes this map and registers each URL on the upstream provider via the user’s own gh (or equivalent) CLI — no paste-into-GitHub step. See Quickstart for the guided flow, or Webhooks if you maintain the upstream hook by hand. Re-running against the same workspace is safe — running it twice has the same effect as running it once. Your edits to SKILL.md / TRIGGER.md replace the previous version on the next event.

​
Two ways to invoke

Most users don’t run zombiectl install --from directly. They drive the install from a host agent (Claude Code, Amp, Codex CLI, OpenCode) via the /usezombie-install-platform-ops slash command. Add the skills with npx skills add usezombie/skills, which symlinks /usezombie-* into every supported host’s skill directory it detects. Then invoke the slash command in your host agent: 
/usezombie-install-platform-ops
No global install? curl -fsSL https://usezombie.sh | bash installs zombiectl and the skill together in one command (requires Node — it runs npm under the hood). Run curl -fsSL https://usezombie.sh without | bash to read it first.
The slash command asks three gating questions (Slack channel, production branch glob, optional cron schedule), registers the webhook via your existing gh CLI, and prints a per-trigger registration summary at the end. See Quickstart for the full walkthrough. Power users and scripted setups call zombiectl install --from <path> directly — the same flow as the slash command, minus the gating questions and the auto-registration. For the self-managed provider posture, see zombiectl tenant provider.

​
Exit codes

CodeMeaning
0Installed (or updated).
1No workspace selected, or API error.
2Missing --from, invalid path, or schema rejection.

​
See also