Diagnose SKILL.md skillA
Diagnose from wrg32786/aigent-os is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wrg32786/aigent-os/Diagnose@git:20260707.2a2e857Pins git:20260707.2a2e857 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wrg32786/aigent-os
- Path
skills/diagnose/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260707.2a2e857, committed Jul 7, 2026
- Size
- 6,538 bytes
- Repository stars
- 23
- License
- MIT
When something feels off, type /diagnose and describe the symptom. The skill walks the seven-layer stack (kernel, skills, hooks, daemons, vault, doctrine, principal config) and reports which layer is most likely responsible. Caddy pattern applied to debugging.
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
# Diagnose Most failures in an aigent-OS install aren't bugs in any single component — they're integration failures across layers. `/diagnose` walks the stack with you so you don't have to. ## When to use - "It used to work, now it doesn't" - Caddy isn't surfacing a skill you expect - `/open` produces incomplete context - Hooks not firing - Wikilinks not resolving - AI behavior changed unexpectedly after an update - Anything you can't immediately attribute to a single component ## How to execute ### Step 1 — Capture the symptom Ask the user (or read from their prompt): - **What were you trying to do?** - **What happened instead?** - **What did you expect?** - **What changed recently?** (git pull, new skill installed, hook edit, kernel update) Frame the symptom in one sentence. Example: *"Caddy used to surface /channel-audit when I asked about YouTube performance, now it doesn't."* ### Step 2 — Walk the seven-layer stack For each layer, ask: could this layer be responsible for the symptom? If yes, run the specific check. If no, move on. ``` LAYER 7 — Principal Configuration - system/00_identity.md customized? …
Read the whole file at its exact version.
How to install
mdr add wrg32786/aigent-os/Diagnose@sha256:63b57798e2d26395The line at the top of this page pins the label git:20260707.2a2e857, 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_3xh4xmcgnjzlv5fg)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 7, 2026.
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 (6538 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
wrg32786/aigent-os · 23 stars · license MIT · pushed 2026-10-23 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_3xh4xmcgnjzlv5fg GET https://markdownregistry.com/api/v1/resolve?ref=wrg32786/aigent-os/Diagnose GET https://markdownregistry.com/api/v1/blob/63b57798e2d26395d187b6d6d1c80b6e64f367e85ab1b8f6e3f9f0351c02ed9d
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.