zapier-handoff skillA
zapier-handoff is agent-read markdown (skill) from runxhq/runx: Validate a runx execution context and hand off a governed payload to a Zapier Catch Hook through any compatible provider binding, with idempotency and receipt-backed readback..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Zapier Handoff Hand off governed runx work to a Zapier Catch Hook while keeping authority, provider credentials, and receipts in runx. This skill is for the outbound side of the Zapier integration story. It is not the public Zapier App Directory app; that app should call hosted runx APIs. This skill gives the same execution-context contract to local dogfood and any operator-owned Zap that receives governed effects from runx. ## Runners - `preflight`: validates and normalizes the handoff context without network. - `send`: validates the context, invokes the selected Catch Hook, and reads the invocation back. Use `preflight` for reviews, CI, and local harnesses; it never needs approval. The `send` runner first calls native `control.prepare_handoff`, which validates the execution identity and produces the canonical delivery envelope. It then uses the provider boundary for `hook.invoke`; that boundary owns the exact approval, credential custody, idempotency, and provider operation. A separate provider read verifies the same event and invocation reference. The compatible binding may be local or hosted; the skill does not assume credential custody. ## Execution context …
Read the whole file at its exact version.
How to install
mdr add runxhq/runx/zapier-handoff@git:20260811.1ec1771mdr add runxhq/runx/zapier-handoff@sha256:fa960978f3a83254Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_yrxrlhzqsywogcqr)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260811.1ec1771 latest | 2026-08-11 | 1ec1771 | 3,372 B | A | view · diff |
| git:20260803.aaae4e0 | 2026-08-03 | aaae4e0 | 3,429 B | A | view · diff |
| git:20260723.6e5370b | 2026-07-23 | 6e5370b | 2,805 B | A | view · diff |
| git:20260716.b2ae7b6 | 2026-07-16 | b2ae7b6 | 2,427 B | A | view · diff |
| git:20260715.f00df98 | 2026-07-15 | f00df98 | 2,411 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3372 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
runxhq/runx · 93 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yrxrlhzqsywogcqr GET https://markdownregistry.com/api/v1/resolve?ref=runxhq/runx/zapier-handoff GET https://markdownregistry.com/api/v1/blob/fa960978f3a8325428c192badf7b449213015e8f789ab6d513c5138983ae30e9
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.