ops-root-cause SKILL.md skillA
ops-root-cause from baristaze/swe_guidelines is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add baristaze/swe_guidelines/ops-root-cause@git:20261014.7748a1fPins git:20261014.7748a1f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- baristaze/swe_guidelines
- Path
scaffold/acme_root/.agents/skills/ops-root-cause/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261014.7748a1f, committed Oct 14, 2026
- First version recorded
- Sep 29, 2026
- Size
- 21,631 bytes
- Repository stars
- 94
- License
- MIT
Find the root cause of one tenant's problem in one environment: read that tenant's rows through the operator plane's read routes with a read-only operator token, correlate them with the logs, the trace, and the error event by request id, at most five ids and one pass each, and report the cause and the fix, or that none was found. Takes the org id and optionally a user id. Never a database login, never a write, never another tenant's data.
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
# ops-root-cause The supporter's skill. An investigation ends at "tenant X sees Y"; this skill opens tenant X, and only tenant X, through the operator plane, and follows each request id, at most five, once across every signal. The cause it names is a line of code, a row, or a resource, or it reports "not found". Read `../_shared/ops-preamble.md`, a path from this skill's folder, before the first step: the profiles, the account check, and the env file are there. ## Input `--env local|staging|production --org <org_id> [--user <user_id>] [--request-id <id>]... [--since 24h]` `--env` and `--org` are required; ask for them when missing. `--user` narrows to one member of the tenant. `--request-id` starts from a request, and may be given more than once; without it the skill finds the failing requests of the window in the tenant's change events (step 3), the one signal read by tenant: the error tracker holds no tenant (step 4). `--since` is the window, a day by default. A run follows at most 5 request ids, one pass each: the first five given, in the order given, or without `--request-id`, the five newest requests whose change events step 3 ties to the symptom (the Y of "tenant X …
Read the whole file at its exact version.
How to install
mdr add baristaze/swe_guidelines/ops-root-cause@sha256:dd18fd247f9786bdThe line at the top of this page pins the label git:20261014.7748a1f, 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_kdf34wvrkmkku6xr)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Sep 29, 2026 and Oct 14, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.7748a1f latest | 2026-10-14 | 7748a1f | 21,631 B | A | view · diff |
| git:20261014.62aa70e | 2026-10-14 | 62aa70e | 20,259 B | A | view · diff |
| git:20260930.97478f9 | 2026-09-30 | 97478f9 | 20,076 B | A | view · diff |
| git:20260930.6934ae1 | 2026-09-30 | 6934ae1 | 19,852 B | A | view · diff |
| git:20260930.6756f8f | 2026-09-30 | 6756f8f | 14,723 B | A | view · diff |
| git:20260929.0713568 | 2026-09-29 | 0713568 | 12,656 B | A | view · diff |
| git:20260929.3422014 | 2026-09-29 | 3422014 | 9,621 B | A | view |
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 (21631 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
baristaze/swe_guidelines · 94 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kdf34wvrkmkku6xr GET https://markdownregistry.com/api/v1/resolve?ref=baristaze/swe_guidelines/ops-root-cause GET https://markdownregistry.com/api/v1/blob/dd18fd247f9786bd4e7c1705ca33c00f93aa448a9f35d54dd68d2b7c175d6064
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.