managed-campaign-work SKILL.md skillA
managed-campaign-work 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/managed-campaign-work@git:20261117.ade33bcPins git:20261117.ade33bc 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/managed-campaign-work/SKILL.md- Versions recorded
- 10
- Latest version
- git:20261117.ade33bc, committed Nov 17, 2026
- First version recorded
- Nov 2, 2026
- Size
- 42,288 bytes
- Repository stars
- 9
- License
- MIT
Use when a person wants Jason to start outbound work for them, such as getting meetings or running a campaign, and asks what to do first, and when an interactive agent session should turn an outbound objective into durable campaign work that Jason performs - creating a campaign, adding the people it is about, submitting managed provider operations and AI role work, and following what the runtime does with them; and when a person wants Jason to answer somebody who wrote back - answering a…
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
# Managed campaign work Jason owns campaign state; a conversation does not. Anything decided in a session that is not committed through the Jason CLI has not happened: it will not survive the session, will not be dispatched, will not be approved by anybody, and will leave no history. This skill is the managed path — how to put work where the runtime can perform it, and what to do while it waits. **Status: draft.** No agent host has read this text in the state it ships in. It covers the operations this build publishes and nothing else. ## What you are responsible for, and what the runtime is You decide *what* should happen: which campaign, which people, which operation, with which arguments. The runtime decides *whether and when* it happens: it validates the arguments against the operation's published contract, refuses work it cannot route, waits for a person where a person is required, retries what is worth retrying, and records every attempt. Do not re-implement any of that in a session — if the runtime refuses something, read the code it answered with rather than working around it. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ffuk3bsjn6gr42nl/6668c81fba616c8f9c8495d757d594008a9255faa2e73387d80ced9f4bb26f35.json
Then /plugin install managed-campaign-work@markdownregistry-ffuk3bsjn6gr42nl in Claude Code. It installs git:20261117.ade33bc, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add reply-team/jason-ai/managed-campaign-work@sha256:6668c81fba616c8fThe line at the top of this page pins the label git:20261117.ade33bc, 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_ffuk3bsjn6gr42nl)
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/managed-campaign-work 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 managed-campaign-work from somewhere else? Ask it: where did my managed-campaign-work 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 10 versions of this file, between Nov 2, 2026 and Nov 17, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261117.ade33bc latest | 2026-11-17 | ade33bc | 42,288 B | A | view · diff |
| git:20261117.41ec6d2 | 2026-11-17 | 41ec6d2 | 40,364 B | A | view · diff |
| git:20261116.b93cf38 | 2026-11-16 | b93cf38 | 40,193 B | A | view · diff |
| git:20261116.5dc560e | 2026-11-16 | 5dc560e | 39,833 B | A | view · diff |
| git:20261114.6b52d5c | 2026-11-14 | 6b52d5c | 38,935 B | A | view · diff |
| git:20261112.f46bee4 | 2026-11-12 | f46bee4 | 38,513 B | A | view · diff |
| git:20261105.700a80a | 2026-11-05 | 700a80a | 35,479 B | A | view · diff |
| git:20261104.b756b1e | 2026-11-04 | b756b1e | 35,504 B | A | view · diff |
| git:20261103.46702c0 | 2026-11-03 | 46702c0 | 35,476 B | A | view · diff |
| git:20261102.e0633ba | 2026-11-02 | e0633ba | 35,315 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/managed-campaign-work/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 (42288 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_ffuk3bsjn6gr42nl GET https://markdownregistry.com/api/v1/resolve?ref=reply-team/jason-ai/managed-campaign-work GET https://markdownregistry.com/api/v1/blob/6668c81fba616c8f9c8495d757d594008a9255faa2e73387d80ced9f4bb26f35
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.