opscrew-adapt SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
opscrew-adapt from opscrew-hub/opscrew is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add opscrew-hub/opscrew/opscrew-adapt@git:20261023.e0d016cPins git:20261023.e0d016c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- opscrew-hub/opscrew
- Path
plugin/skills/opscrew-adapt/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261023.e0d016c, committed Oct 23, 2026
- First version recorded
- Oct 11, 2026
- Size
- 4,872 bytes
- Repository stars
- 3
- License
- Apache-2.0
Prepare the app's code for container deployment the OpsCrew way (production Dockerfile, .dockerignore, health endpoint, port from the environment, secrets moved to environment variables, build settings). Use after OpsCrew's design step, or whenever the user asks to containerize or productionize the app for OpsCrew.
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
# Prepare the code for deployment The list of required changes is `codeChanges` in `opscrew/plan.yaml` (read it; do not edit it). Work on a new branch, change only what each item needs, keep the app's behaviour, and do not add dependencies unless there is no other way (then tell the user which and why). In a repository with several apps, a further app's plan is `opscrew/apps/<key>/plan.yaml` (`opscrew_app_list` names the apps): read the plan of the app the user means, and change only the files in that app's folder. ## Per change kind - **dockerfile / dockerignore / env-example:** prefer OpsCrew's templates — they run as a non-root user and match the detected stack. If the files are missing, generate them with the same structure as OpsCrew's templates: multi-stage build, base images pinned by tag and `@sha256` digest, at the runtime version in `app.build.runtime.version` of `opscrew/plan.yaml` (the version the app declares, else OpsCrew's default), dependencies installed from the lockfile, `USER` set to a non-root user, the app listening on `0.0.0.0:$PORT`. Write no Dockerfile when `app.build.builder` …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_vzzesb5mtfi6vsuy/ea247bb8f758ec21c2b5a9c5e6c9ccaba34d02f86604d9a2be08df97298935ec.json
Then /plugin install opscrew-adapt@markdownregistry-vzzesb5mtfi6vsuy in Claude Code. It installs git:20261023.e0d016c, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add opscrew-hub/opscrew/opscrew-adapt@sha256:ea247bb8f758ec21The line at the top of this page pins the label git:20261023.e0d016c, 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_vzzesb5mtfi6vsuy)
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 opscrew-hub/opscrew/opscrew-adapt 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 opscrew-adapt from somewhere else? Ask it: where did my opscrew-adapt 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 4 versions of this file, between Oct 11, 2026 and Oct 23, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261023.e0d016c latest | 2026-10-23 | e0d016c | 4,872 B | A | view · diff |
| git:20261020.d875f12 | 2026-10-20 | d875f12 | 4,655 B | A | view · diff |
| git:20261019.aa36972 | 2026-10-19 | aa36972 | 2,440 B | A | view · diff |
| git:20261011.31287ef | 2026-10-11 | 31287ef | 2,201 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/opscrew-adapt/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 (4872 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
opscrew-hub/opscrew · 3 stars · license Apache-2.0 · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vzzesb5mtfi6vsuy GET https://markdownregistry.com/api/v1/resolve?ref=opscrew-hub/opscrew/opscrew-adapt GET https://markdownregistry.com/api/v1/blob/ea247bb8f758ec21c2b5a9c5e6c9ccaba34d02f86604d9a2be08df97298935ec
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.
More from opscrew-hub/opscrew
Every file in opscrew-hub/opscrew