Menu
Inspect authoritative Zigrix Task metadata, pending recovery, requests, assignments, and result decisions.
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ê.
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.
Create a revision-0 Zigrix Task and bind its spawned orchestrator through the bootstrap composition flow.
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.
Baseado na classificação ocupacional SOC
| name | zigrix-task-status |
| version | 0.3.0 |
| description | Inspect authoritative Zigrix Task metadata, pending recovery, requests, assignments, and result decisions. |
| metadata | {"openclaw":{"requires":{"bins":["zigrix"]},"cliHelp":"zigrix task status --help"}} |
Use this skill only for read-only inspection.
zigrix task list --json
zigrix task status TASK-20260713-001 --json
zigrix task events TASK-20260713-001 --json
tasks/<taskId>.meta.json is the authoritative Task snapshot. Status output exposes that metadata plus resolved paths such as specPath, metaPath, and projectDir. Use the returned paths; do not construct paths from symbolic config keys.
tasks.jsonl is a typed audit diagnostic and index.json is a rebuildable projection. Neither overrides or reconstructs metadata. A stale index may be rebuilt, but a status mismatch must be resolved from the metadata snapshot.
Check all of these before deciding what can happen next:
status, schema version, and current revisionagentId, sessionKey, sessionId, and bindingEpochpendingCommit, command id, payload digest, expected revision, recovery stage, and any recoverable_in_doubt receiptBLOCK_REQUEST or STALE_DETECTED records and orchestrator_action_requiredPREPARED, ACTIVE, EXPIRED, or SUPERSEDED stateA submitted result is not an approved result. Only an immutable APPROVE_UNIT_RESULT decision by the exact stored orchestrator makes that unit eligible for FINALIZE. Rejection preserves evidence history; a valid resubmission receives the next ordinal on the same active assignment epoch.
If pendingCommit exists, do not infer that the snapshot is unchanged. Once snapshot rename was attempted, the result is in-doubt and recovery must retry the same deterministic command id with the identical payload. Do not issue a different command, edit metadata/audit/evidence/index, or reset state around it.
BLOCK_REQUEST and STALE_DETECTED are request-only records. They do not change status or revision. Only the stored orchestrator can acknowledge/reject the block request and commit a top-level transition. If it is unavailable, leave the unresolved request visible for operator diagnosis.
This skill does not grant permission to call START, BLOCK, RESUME, FINALIZE, REPORT, assignment mutation, or result-decision commands.