deployment skillA
deployment is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Prepare and run a release you can explain and undo — exact artifact identity, environment parity, config and secrets, a rollout strategy matched to blast radius, and a preflight that names the abort condition in advance. Use when planning or performing a deploy, building a release path, or when someone says "ship it" and the steps are not written down anywhere. Not for proving the deployed thing is healthy (release-verification) or for getting back out (rollback), and it never treats a green bui.
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
# Deployment A release has two halves that get conflated constantly: preparing it, which you can do freely, and executing it, which is an outward-facing action against a system other people depend on. This skill covers both and keeps the line between them visible. ## When this fires A change is heading for an environment other people use, or the path that takes it there is being built or changed. It does not fire for running something locally, and it does not fire while an incident is in progress — restoring service outranks release process. ## Procedure 1. **Name the artifact exactly.** A commit SHA, an image digest, a build number — something that resolves to one immutable thing. "main", "latest" and "the current branch" are not artifact identities; they are queries whose answer changes while you work. Everything downstream, from the rollback target to the verification, depends on this being pinned. 2. **Read the delivery path that already exists** before designing one. CI config, deploy scripts, the platform's own project settings, and however the last release actually went out. Most …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/deployment@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/deployment@sha256:b45aaf4f0b5fb502Pin 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_yscrzczracojmslv)
1 badge views in 30 days
Versions
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 (7495 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
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yscrzczracojmslv GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/deployment GET https://markdownregistry.com/api/v1/blob/b45aaf4f0b5fb502a43b1c38159154bab0772b30c9a23d8ae3e0ade267638d8b
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.
More from nahid-sparktales/agent-dispatcher
Every file in nahid-sparktales/agent-dispatcher