checking-delivery SKILL.md skillA
checking-delivery from grit-77/done-is-a-claim is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add grit-77/done-is-a-claim/checking-delivery@git:20261010.677e0a8Pins git:20261010.677e0a8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- grit-77/done-is-a-claim
- Path
skills/checking-delivery/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261010.677e0a8, committed Oct 10, 2026
- Size
- 3,624 bytes
- Repository stars
- 33
- License
- Apache-2.0
Verify an artifact at its actual delivery destination and distinguish send attempts, acknowledgements, publication and consumer checks. Use when reporting a file, message, export or deployment as delivered; creating a local draft alone does not imply delivery.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Checking delivery Inspecting the source establishes what was prepared. Delivery requires evidence about the destination the user was meant to receive. Check only within the authorized scope; this skill grants no publishing or send rights. ## Identify the artifact and destination Record the inspected source artifact and its revision or byte identity, the intended destination and the relevant operation identity. A source path, preview or successful build does not identify the delivered copy. Keep these observations separate, using the states the system exposes: - **Prepared:** the source exists and has been inspected. - **Attempted:** a send, upload or publication operation was issued. - **Acknowledged:** the system returned a receipt matching that operation. - **Published:** the intended destination exposes the artifact or revision. - **Consumer checked:** the delivered artifact was opened in its intended use. - **Unverified:** a necessary observation is unavailable or inconclusive. These are claims with separate evidence, not a universal status sequence. An acknowledgement can establish system acceptance without establishing …
Read the whole file at its exact version.
How to install
mdr add grit-77/done-is-a-claim/checking-delivery@sha256:2b2386c7307c524cThe line at the top of this page pins the label git:20261010.677e0a8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_bsxmj3z4r4juhs4o)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 10, 2026.
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 (3624 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
grit-77/done-is-a-claim · 33 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bsxmj3z4r4juhs4o GET https://markdownregistry.com/api/v1/resolve?ref=grit-77/done-is-a-claim/checking-delivery GET https://markdownregistry.com/api/v1/blob/2b2386c7307c524cc68d3a1f388ece733d796691e32ece6c9e184d4ab643c8ad
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.