deliverability-specialist SKILL.md skillA
deliverability-specialist from reply-team/jason-ai is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add reply-team/jason-ai/deliverability-specialist@git:20261112.f46bee4Pins git:20261112.f46bee4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- reply-team/jason-ai
- Path
skills/runtime/roles/deliverability-specialist/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261112.f46bee4, committed Nov 12, 2026
- First version recorded
- Oct 23, 2026
- Size
- 13,923 bytes
- Repository stars
- 9
- License
- MIT
Use when Jason launches you as the deliverability specialist role on an ai_role work item — read what stopped and what was suppressed, say what it means for deliverability, and answer in the shape the item asks for.
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
# Deliverability specialist You read what stopped and what was suppressed, and you say what it means for whether messages are reaching anybody — and what somebody would have to do about it. **Status: draft.** No agent host has read this text in the state it ships in. Its commands parse against this build, because every skill's do. ## What this build gives you, and what it does not **There is nothing to warm in this build.** No mailbox, domain or sending identity is modelled here and no verb changes one; warming up is a provider operation, and nobody has routed one. What you can do is read what stopped and say what it means. ``` jason suppression list jason workitem list --campaign cmp_01JB6K8TQ2W9V4MZ0C3Y7H5NRD --status failed jason journal list --campaign cmp_01JB6K8TQ2W9V4MZ0C3Y7H5NRD ``` **What the provider counts, you can read.** A `provider_op` item naming `engagement.summarize` answers a row of counts per channel over a window, with the envelope that says what each number counts; `bounced` and `opted_out` are counts in the email row. **And there is one protective move.** When what you read means a campaign must stop sending, a `provider_op` item …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_t3fctpan2faz7ilh/0ea3e0c91508d40ee9a2d77a011c57080d83807da4a52a2fc203417857059820.json
Then /plugin install deliverability-specialist@markdownregistry-t3fctpan2faz7ilh in Claude Code. It installs git:20261112.f46bee4, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add reply-team/jason-ai/deliverability-specialist@sha256:0ea3e0c91508d40eThe line at the top of this page pins the label git:20261112.f46bee4, 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_t3fctpan2faz7ilh)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in reply-team/jason-ai/deliverability-specialist since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of deliverability-specialist from somewhere else? Ask it: where did my deliverability-specialist come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Oct 23, 2026 and Nov 12, 2026, about one every 5 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261112.f46bee4 latest | 2026-11-12 | f46bee4 | 13,923 B | A | view · diff |
| git:20261105.700a80a | 2026-11-05 | 700a80a | 13,272 B | A | view · diff |
| git:20261104.b756b1e | 2026-11-04 | b756b1e | 13,297 B | A | view · diff |
| git:20261025.d537b05 | 2026-10-25 | d537b05 | 13,062 B | A | view · diff |
| git:20261023.8cfd508 | 2026-10-23 | 8cfd508 | 10,766 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/deliverability-specialist/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (13923 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
reply-team/jason-ai · 9 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t3fctpan2faz7ilh GET https://markdownregistry.com/api/v1/resolve?ref=reply-team/jason-ai/deliverability-specialist GET https://markdownregistry.com/api/v1/blob/0ea3e0c91508d40ee9a2d77a011c57080d83807da4a52a2fc203417857059820
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.