Orch Task
Run one ready ticket through its named executor to one accepted result. The unit engine every larger shape composes.
Install
$ agentstack add skill-danmcinerney-orchflows-orch-task ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-danmcinerney-orchflows-orch-task) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Require: one ready [ticket](../../../contracts/work-item.md) — issued by decomposition, or an [ad-hoc ticket](../../../docs/vocabulary.md) the orchestrator writes before claim. Refuse a ticket whose completion test lacks a named oracle with its oracle_class on any criterion, naming the missing part — a request that cannot name one belongs to orch-spec.
Claim the ticket (set claimed_by, claimed_at, status claimed). Derive the item's workspace per the workspace cell of the pack the ticket names — a ticket naming none works at its plain-path write scope — before dispatch. Dispatch exactly one fresh child through orch-delegate — or execute inline under [rules/delegation.md](../../../rules/delegation.md) §2's independence condition; the ladder's cheaper rungs apply inside the child — naming the ticket's executor as the applied skill, with the ticket path plus the derived workspace identity as the packet.
When a criterion's oracle carries authored-here provenance and the ticket's independence reads checker, dispatch orch-check as one further fresh child on the same packet shape, then re-run the completion test through orch-verify at the checked result — its entries supersede what they cover, per [rules/verification.md](../../../rules/verification.md) §10.
Accept the result once through orch-integrate. On suspended — the executor has written its ## Handoff — set status suspended, claim fields kept, for the next claim to resume from it; never the join's reject path. On any other disposition, integrate the result into the run workspace per the ticket's pack workspace cell when one is named — a conflict during integration routes to the cell's conflict binding; derived evidence the cell defines is refreshed at the fixed revision before any lens runs — on needs-verify run orch-verify for exactly the uncovered criteria; on rejected record the blame class. Record the join's terminal status in the ticket.
Never: run two executors for one ticket; accept a result that skipped the join; re-verify evidence the join already accepted.
Return: the completed ticket per [work-item.md](../../../contracts/work-item.md).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: DanMcInerney
- Source: DanMcInerney/orchflows
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.