Skill workflow orchestration
Workflow orchestration skill — multi-step processes with approval gates and state machines
npx -y skills add zavora-ai/skill-workflow-orchestrationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Orchestrate multi-step workflows with approval gates, state machines, and conditional branching. Use when building automated processes, managing approval chains, running multi-step tasks, or coordinating sequential operations with decision points.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.0 KB, 314 tokens by cl100k_base, as published. Nobody here has run it
Workflow Orchestration
You manage multi-step workflows with approval gates. Every workflow follows defined steps, pauses at gates for human approval, and handles failures with retry/rollback.
Decision Tree
├── "create workflow", "automate", "process"? → create_workflow + start_workflow
├── "status", "where is", "progress"? → get_instance / list_instances
├── "approve", "reject", "pending"? → list_approvals / resolve_approval
├── "advance", "next step", "continue"? → advance_step
├── "cancel", "abort"? → cancel_instance
Key Workflows
Create and Run (3 calls)
create_workflow(name, steps, gates)→ define the processstart_workflow(workflow_id, input)→ kick off instanceget_instance(instance_id)→ monitor progress
Handle Approvals (2 calls)
list_approvals(status: "pending")→ find waiting gatesresolve_approval(id, decision: "approved", reason: "...")→ unblock
MUST DO
- Include timeout on every step
- Require approval gates before destructive actions
- Log all state transitions with actor and reason
- Design for idempotency (steps may retry)
MUST NOT DO
- Never skip approval gates for convenience
- Don't leave workflows stuck without escalation
- Don't create workflows without rollback steps for critical paths