operating-the-installation SKILL.md skillB
operating-the-installation 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/operating-the-installation@git:20261117.ade33bcPins git:20261117.ade33bc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- reply-team/jason-ai
- Path
skills/runtime/operating-the-installation/SKILL.md- Versions recorded
- 10
- Latest version
- git:20261117.ade33bc, committed Nov 17, 2026
- First version recorded
- Nov 6, 2026
- Size
- 43,084 bytes
- Repository stars
- 9
- License
- MIT
Use when a person asks about the Jason installation itself rather than about campaign work - whether the runtime is up, starting and stopping it, having it start at logon, which plugins and routes exist, which journal kinds a subscribing plugin is handed and where each stands, which accounts' events it reads and reading a span of one again, which agent hosts are registered, whether notifications reach the person and turning them off, whether a newer version has been released, opening the…
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
# Operating the installation This skill is about the installation, not about the work it performs. A person reaches it when they ask whether Jason is up, why nothing is happening, what is installed, where work would go, or whether they are on the current version. Campaign work itself is `managed-campaign-work`. **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. It covers what this build does and nothing else. Two things are true throughout and are easy to forget. **Nothing is registered until somebody asks**: Jason starts because you started it, or because somebody registered it to start at logon. And **no provider ships configured**: a fresh installation performs no provider work at all until an operator has installed a plugin and written a route. ## Is it running ``` jason runtime status --human ``` That asks the runtime for `system.info` and prints what it says: the version, the data directory it is using, how long it has been up, the migrations applied, and — once the runtime has successfully asked the release feed — an `update` section saying whether a newer version exists. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ohw3cqepqpz2ne3q/ca815fad6aa1b5119974db3d9ffba08dd7657bfb5411dc5d2d9387341821b2e9.json
Then /plugin install operating-the-installation@markdownregistry-ohw3cqepqpz2ne3q in Claude Code. It installs git:20261117.ade33bc, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add reply-team/jason-ai/operating-the-installation@sha256:ca815fad6aa1b511The 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_ohw3cqepqpz2ne3q)
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/operating-the-installation 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 operating-the-installation from somewhere else? Ask it: where did my operating-the-installation 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 6, 2026 and Nov 17, 2026, about one every day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261117.ade33bc latest | 2026-11-17 | ade33bc | 43,084 B | B | view · diff |
| git:20261117.41ec6d2 | 2026-11-17 | 41ec6d2 | 42,742 B | B | view · diff |
| git:20261117.1dc9c93 | 2026-11-17 | 1dc9c93 | 42,422 B | B | view · diff |
| git:20261116.5dc560e | 2026-11-16 | 5dc560e | 42,017 B | B | view · diff |
| git:20261115.1a52521 | 2026-11-15 | 1a52521 | 41,569 B | B | view · diff |
| git:20261112.efc6e96 | 2026-11-12 | efc6e96 | 39,033 B | B | view · diff |
| git:20261111.5faa598 | 2026-11-11 | 5faa598 | 38,836 B | B | view · diff |
| git:20261109.6201450 | 2026-11-09 | 6201450 | 36,522 B | B | view · diff |
| git:20261107.9bced8f | 2026-11-07 | 9bced8f | 33,286 B | B | view · diff |
| git:20261106.0382826 | 2026-11-06 | 0382826 | 31,865 B | B | 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/operating-the-installation/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
- fail: No curl or wget piped into a shell (matched: curl -fsSL https://get.jasonharness.ai/releases/latest/download/install.sh | sh)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (43084 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 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
reply-team/jason-ai · 9 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ohw3cqepqpz2ne3q GET https://markdownregistry.com/api/v1/resolve?ref=reply-team/jason-ai/operating-the-installation GET https://markdownregistry.com/api/v1/blob/ca815fad6aa1b5119974db3d9ffba08dd7657bfb5411dc5d2d9387341821b2e9
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.