- Home
- Skills
- Agents & Orchestration
- Artifact Relay Orchestration
Artifact Relay Orchestration
Multi-agent teams that verify everything against the source — zero "trust me" handoffs.
$34
Works with the AI Agents you already use
Artifact Relay Orchestration
Example session with this skill installed
Initialize a builder-verifier handoff for the auth-service refactor. Verify the current head commit hash and ensure the verifier lane is ready to read the live object.
- Read your context and instructions
- Compiled the artifact relay orchestration
I have initialized the Artifact Relay Orchestration protocol for the auth-service refactor. The builder lane has completed the task, and the transport laws are now being applied to the handoff.
Artifact Handoff Verification
| Metric | Value | Verification Status |
|---|---|---|
| Current Head Commit | 8f2a1c9e4b3d7f0a1b2c3d4e5f6a7b8c9d0e1f2a | Verified (Live) |
| Artifact Hash (SHA-256) | e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 | Match Confirmed |
| Lane Attribution | lane-builder-01 | Signed |
| Standing Queue Status | auth-service-refactor (Processing) | Active |
| CI Gate Status | build-green | Pass |
The verifier lane (lane-verifier-01) is now gated. It will re-read the object at the specified commit hash above to perform independent verification. No summary data from the builder lane will be used for the audit.
Next steps
- Trigger Verifier Lane: Invoke the verifier to read the live repo state at the pinned hash.
- Review Merge Gate: Once the verifier posts the result, execute the
Merge Gatechecklist. - Update Queue: Mark the refactor item as verified and move to the next item in the standing queue.
Connects securely to your tools. The creator never sees your data.
About this skill
Most multi-agent failures aren't model failures — they're stale relays, silent error swallows, unmergeable "verification," and surfaces claiming states that aren't true. This skill encodes the hard-won operating law for agent swarms: go to the object never a reference of it; byte-for-byte is a gate while a hash is an audit; frame-transform at boundaries; the builder never merges without an independent verifier posted on the object; standing queues with no empty wakes; pre-authorization that ships self-executing machinery. Comes with freeze discipline for exams/graded runs, surface-honesty rules, a merge-gate checklist, and a reference file of failure families (stale relay, silent swallow, guard that can't fire, fantasy fill, overclaim, correlated evidence) each mapped to its mechanical counter-law. What's inside: SKILL.md (the law set), reference/workflow-patterns.md (relay message format, standing queue template, failure families, post-mortem pattern), examples/worked-example.md (a merge that almost shipped on a stale relay, worked end to end).
Requires terminal/filesystem access for hash checks. Handoffs fail if live sources are unreachable. No support for untracked manual changes.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago