Skip to main content
A template is a directory with a valid SKILL.md and TRIGGER.md. Pick one, install it, get a working agent. 
zombiectl install --from <path>
The zombiectl package ships sample directories under ~/.config/usezombie/samples/.

​
Catalogue

​
platform-ops

The flagship v2 sample. Wakes on a GitHub Actions deploy failure, gathers evidence from your hosting provider and the failed workflow, and posts an evidenced diagnosis to Slack. Read-only against your infrastructure; the only write path is the channel post.
  • Tools: http_request, memory_recall, memory_store, cron_add, cron_list, cron_remove.
  • Credentials: github (with webhook_secret for signature verification), slack (bot token).
  • Trigger: webhook from GitHub Actions (workflow_run.conclusion=failure).
For the full install walkthrough — host agent, gating questions, webhook wiring — see Quickstart. Don’t duplicate the steps here. More samples land as new flagships ship.

​
Writing your own

A template is just a directory with SKILL.md and TRIGGER.md. See Authoring an agent for the file references; install with: 
zombiectl install --from .

​
Sharing

Templates are markdown — commit my-agent/ to git, clone it on a new machine, zombiectl install --from .. Credentials never live in the template; they live in the workspace vault. Template-safe to share publicly; credentials are not.
A hosted template marketplace (community-contributed agents, one-click install) is on the roadmap. For now, git is the distribution mechanism.