release-maintenance skillA
release-maintenance is agent-read markdown (skill) from flurdy/agent-skills: Separately confirmed manifest reconciliation, scoped config synchronization, workload restart, or evidence-backed rollout acknowledgement. Requires explicit invocation; never runs inside a release watch tick..
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
# Release Maintenance Own production-affecting maintenance separately from shipping decisions. This skill is **never invoked by** `/release-manager` or `/watch-release`; those workflows may suggest a fresh explicit invocation but cannot dispatch it. A push answer is not maintenance authorization. ## Usage ```text /release-maintenance reconcile-order /release-maintenance config-sync <repository> /release-maintenance restart <service> /release-maintenance acknowledge-rollout <service> ``` Require an explicit operation and target. A missing/ambiguous argument is a clarification, not a license to scan for actions. Load the verified project's guidance and relevant runbook first. Do not invent repository names, cluster context, namespaces, startup-only config behavior, or consumer sets. Unsupported project capabilities require a handoff, not generic fallback commands. ## Shared action boundary 1. Identify the exact repository/worktree or Kubernetes context/namespace/resource and current evidence. Preserve unrelated edits and state. One writer per state file; pause the attended manager before any shared-state update. Malformed or concurrently changed state stops writes. …
Read the whole file at its exact version.
How to install
mdr add flurdy/agent-skills/release-maintenance@v1.0.0mdr add flurdy/agent-skills/release-maintenance@sha256:75c19541d8988358Pin 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_zw3ao7kajj3iynoj)
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 (7723 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
flurdy/agent-skills · 9 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zw3ao7kajj3iynoj GET https://markdownregistry.com/api/v1/resolve?ref=flurdy/agent-skills/release-maintenance GET https://markdownregistry.com/api/v1/blob/75c19541d8988358373c6a6b2be6251457271f1e795e291ff3551ab741abf71b
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.