Run owned terminal coding-agent workflows with Zero
Use Zero to run local, scriptable coding-agent sessions with operator-controlled models, permissions, tools, skills, MCP servers, and durable transcripts.
npx skills add agentskillexchange/skills --skill run-owned-terminal-coding-agent-workflows-with-zero
Use Zero when an operator needs a local terminal coding agent that can inspect a repository, edit files, run commands, use browser or terminal helpers, and keep durable sessions while the operator controls the model provider and permission policy. The agent can run interactively through the TUI or non-interactively with zero exec for repeatable code changes, failing-test fixes, JSON or stream-JSON automation, isolated worktrees, spec-first runs, MCP servers, skills, plugins, hooks, and specialist subagents. Invoke it instead of using a hosted coding product normally when the workflow needs local session state, reviewable command execution, provider choice, explicit sandbox/permission boundaries, and automation-friendly exits inside a repository. The scope boundary is the owned terminal coding-agent workflow around Zero’s CLI, tools, permissions, sessions, and integrations; it is not a generic model SDK, provider gateway, or broad product listing.
What this skill actually does
Inputs and prerequisites: Zero CLI, npm or a GitHub Release binary, a supported LLM provider credential or local model, Git, and a target repository.
Setup notes: Install with npm install -g @gitlawb/zero, then run zero for the TUI or zero exec “fix the failing test in ./pkg” for a scripted run. Operators can also install from the documented GitHub Release or source paths and configure providers with zero setup, zero providers list, zero models list, and zero doctor.
Source and verification boundary: use https://github.com/Twigpine/zero and https://zero.gitlawb.com as the canonical references before running the workflow; keep model credentials, shell permissions, file writes, MCP tools, and generated code changes reviewable against the local repository and Zero’s documented permission model.
Framework fit: publish this as a Multi-Framework workflow because Zero is intentionally provider-, model-, skill-, MCP-, and agent-runtime-agnostic while still exposing a concrete operator workflow through the Zero CLI.