deliverable-check skillA
deliverable-check is agent-read markdown (skill) from ericpardee/agent-files: Use before any client-facing or stakeholder-facing deliverable ships (report, email draft, Jira/Slack post, doc) - lints for metaspeak (references to prior drafts, revisions, feedback, the writing process), em/en dashes, and the "isn't just" trope. Triggers on "check this before I send it", "lint the report", "is this clean", or /deliverable-check <file>..
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
# Deliverable Check Deliverables must read as standalone artifacts written by a fresh author. This skill makes that rule mechanical instead of remembered. ## Usage ```bash python3 ~/.claude/skills/deliverable-check/scripts/lint.py <file> [<file> ...] ``` Exit 0 clean, 1 findings (printed as `file:line: [rule] text`), 2 read error. ## Workflow 1. Run the linter on the deliverable file(s). 2. Fix every finding by rewriting the sentence as if no prior version ever existed. Do not delete content the reader needs; restate it standalone. 3. Re-run until clean. 4. Only then present, post, or send the deliverable. ## What it catches - Metaspeak: "as discussed", "per your feedback", "updated to reflect", "previous draft", "I've revised", "now includes", and similar references to drafts, revisions, reviewers, or process. - Em and en dashes (house style bans them). - The "isn't just X, it's Y" trope. ## Limits The regex list is a floor, not a ceiling. After a clean lint, do one human-eye pass for subtler process references the patterns cannot catch (for example a paragraph that only makes sense if the reader saw an earlier version). Add any …
Read the whole file at its exact version.
How to install
mdr add ericpardee/agent-files/deliverable-check@git:20260727.291aeaemdr add ericpardee/agent-files/deliverable-check@sha256:00dfa1754c83bc69Pin 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_loxyo7a4kn44ebjd)
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 (1630 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
ericpardee/agent-files · 3 stars · license MIT · pushed 2026-09-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_loxyo7a4kn44ebjd GET https://markdownregistry.com/api/v1/resolve?ref=ericpardee/agent-files/deliverable-check GET https://markdownregistry.com/api/v1/blob/00dfa1754c83bc69fa9dfbb7e0be70ca440c394bd8bd3f84266b02cdbcb2aa45
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.