Menu
Create a revision-0 Zigrix Task and bind its spawned orchestrator through the bootstrap composition flow.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Main-agent-only guide for Zigrix Task creation, orchestrator binding, lifecycle handoff, dashboard, and path resolution. Never use this skill as orchestrator/worker runtime instruction.
Shared guidance for Zigrix authority, lifecycle commands, output modes, path resolution, and safety.
Inspect authoritative Zigrix Task metadata, pending recovery, requests, assignments, and result decisions.
Execute an exact bound Zigrix assignment and submit an immutable unit result.
Official OpenClaw Zigrix entrypoint. Force Zigrix delegation when a message starts with `/oz`, and semantically route plain-language requests to hand work off, assign it, or have Zigrix take it instead of doing the work directly.
Inspect Zigrix environment readiness and OpenClaw integration prerequisites.
| name | zigrix-task-create |
| version | 0.4.0 |
| description | Create a revision-0 Zigrix Task and bind its spawned orchestrator through the bootstrap composition flow. |
| metadata | {"openclaw":{"requires":{"bins":["zigrix"]},"cliHelp":"zigrix task create-task --help"}} |
CREATE_TASK is the lifecycle entrypoint. It publishes an authoritative revision-0 OPEN metadata snapshot, immutable audit record, and index projection through the same recoverable pending-commit protocol used by later commands.
Use the stable command name:
zigrix task create-task
Transport-specific flags are intentionally not assumed here. Supply the typed command payload required by the active integration and prefer its JSON result for downstream automation. Resolved paths returned by the integration (specPath, metaPath, projectDir) must be reused rather than reconstructed from config keys.
Creation alone grants no caller authority over later Task transitions.
CREATE_TASK.agentId, sessionKey, and sessionId.zigrix task bind-orchestrator / BIND_ORCHESTRATOR.bindingEpoch as part of the stored orchestrator identity.START and every later top-level transition.After binding, caller role strings and local agent configuration do not confer authority. Only an exact match to the current stored orchestrator agent/session/sessionId/binding epoch may start, block, resume, finalize, report, prepare/register workers, decide submissions, expire assignments, or reassign work.