opscrew-troubleshoot SKILL.md skillB
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-troubleshoot 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-troubleshoot@git:20261107.89a31f8Pins git:20261107.89a31f8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- opscrew-hub/opscrew
- Path
plugin/skills/opscrew-troubleshoot/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261107.89a31f8, committed Nov 7, 2026
- First version recorded
- Oct 31, 2026
- Size
- 12,153 bytes
- Repository stars
- 3
- License
- Apache-2.0
Find out why an app OpsCrew deployed is failing, slow or using too much, from its status, resource figures, alerts and logs, all read-only with secrets masked, and when a recent release is the cause, how to roll it back in the terminal; with self-hosted monitoring on, how to open its Grafana dashboards and what each shows; and what to change (a larger or smaller server, backups, security updates, tokens about to expire), each proposal with its figures and price. Use when the user asks…
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
# Troubleshooting with OpsCrew
Everything here is read-only: these tools change nothing on the server, in the Portainer or on
Cloudflare. Secrets in log lines arrive masked; never try to recover them.
1. **Status first.** Call `opscrew_status` (with `app` and `environment` when the repository has
several). Read, in this order:
- **Components:** which part (`app`, a worker, a cron job, a service such as `db`) is stopped or
has no container.
- **Resources (read now):** the server's load against its CPUs, memory used of total, the disk,
and each container's CPU, memory against its limit, restarts and uptime. On Cloudflare's
hosting: the last day's requests, errors and CPU time per request against the free plan.
- **Flags:** each line starting `Warning:` or `High:` says what a figure means and what to do:
memory at 90% of a limit (the container is stopped and restarted at the limit), the disk at 85%
or 95%, a restart since the last deploy.
- **Not available:** figures this target can't give (the host's disk in a Portainer; everything
on GitHub Pages). Say so; don't guess them.
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_afec3odu42uvjben/c73a97e66175d7671a11ae8931bdea28cb17a140df71ef302e8d2368acf8074a.json
Then /plugin install opscrew-troubleshoot@markdownregistry-afec3odu42uvjben in Claude Code. It installs git:20261107.89a31f8, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add opscrew-hub/opscrew/opscrew-troubleshoot@sha256:c73a97e66175d767The line at the top of this page pins the label git:20261107.89a31f8, 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_afec3odu42uvjben)
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-troubleshoot 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-troubleshoot from somewhere else? Ask it: where did my opscrew-troubleshoot 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 31, 2026 and Nov 7, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261107.89a31f8 latest | 2026-11-07 | 89a31f8 | 12,153 B | B | view · diff |
| git:20261105.3abd051 | 2026-11-05 | 3abd051 | 11,923 B | B | view · diff |
| git:20261105.2498d20 | 2026-11-05 | 2498d20 | 12,079 B | B | view · diff |
| git:20261104.b283923 | 2026-11-04 | b283923 | 10,071 B | B | view · diff |
| git:20261031.53ecfc6 | 2026-10-31 | 53ecfc6 | 6,282 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/opscrew-troubleshoot/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 instruction to read or print local credentials (matched: read `.env)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12153 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 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
opscrew-hub/opscrew · 3 stars · license Apache-2.0 · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_afec3odu42uvjben GET https://markdownregistry.com/api/v1/resolve?ref=opscrew-hub/opscrew/opscrew-troubleshoot GET https://markdownregistry.com/api/v1/blob/c73a97e66175d7671a11ae8931bdea28cb17a140df71ef302e8d2368acf8074a
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