think-diagnose SKILL.md skillA
think-diagnose from chrisallenlane/claude-swe-workflows is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chrisallenlane/claude-swe-workflows/think-diagnose@git:20261116.75ffff6Pins git:20261116.75ffff6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chrisallenlane/claude-swe-workflows
- Path
skills/think-diagnose/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261116.75ffff6, committed Nov 16, 2026
- First version recorded
- Apr 21, 2026
- Size
- 18,420 bytes
- Repository stars
- 21
- License
- MIT
Abductive reasoning about the causes of a bug, incident, or phenomenon. Parallel diagnosticians apply different lenses; surviving candidates are narrowed by Analysis of Competing Hypotheses (ACH) when needed. Reports leading causes. Feedback only.
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
# Think-Diagnose - Abductive Reasoning About Causes Takes a phenomenon — something that was observed and that the user wants to understand — and produces a ranked set of candidate causes with evidence-based confidence calibration. Uses **abductive reasoning**: inference to the best explanation. Distinct from `/bug-fix` (which handles code-specific diagnosis with artifact output and execution tooling); `/think-diagnose` is pure reasoning about causes, applicable to non-code phenomena as readily as code ones. **This skill produces no tangible artifacts.** It is a consultant, not an implementer. No code, no tickets, no commits. The output is a structured diagnosis report that the user can act on by gathering more evidence, adopting a leading cause, or piping to `/think-brainstorm` for remediation. ## Roles **Judge (you, running this skill):** - Capture the phenomenon in a written brief - Elicit evidence, rigorously separating observation from interpretation - Choose appropriate reasoning lenses - Spawn diagnosticians in isolation - **Evaluate** candidate causes against evidence (this skill has a real evaluative phase, unlike purely-divergent think-* skills) …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_z552h45fxahoqs3j/7c309f53d8d4f7cd123a41b592147d1fb04dc5b74f66ae50a851990350a6c829.json
Then /plugin install think-diagnose@markdownregistry-z552h45fxahoqs3j in Claude Code. It installs git:20261116.75ffff6, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add chrisallenlane/claude-swe-workflows/think-diagnose@sha256:7c309f53d8d4f7cdThe line at the top of this page pins the label git:20261116.75ffff6, 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_z552h45fxahoqs3j)
1 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 chrisallenlane/claude-swe-workflows/think-diagnose 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 think-diagnose from somewhere else? Ask it: where did my think-diagnose 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 Apr 21, 2026 and Nov 16, 2026, about one every 52 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261116.75ffff6 latest | 2026-11-16 | 75ffff6 | 18,420 B | A | view · diff |
| git:20261116.ba42984 | 2026-11-16 | ba42984 | 19,027 B | A | view · diff |
| git:20261116.e39effb | 2026-11-16 | e39effb | 19,003 B | A | view · diff |
| git:20261116.a1d034c | 2026-11-16 | a1d034c | 20,264 B | A | view · diff |
| git:20260421.6ad2603 | 2026-04-21 | 6ad2603 | 14,631 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/think-diagnose/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 (18420 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
chrisallenlane/claude-swe-workflows · 21 stars · license MIT · pushed 2026-11-17 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_z552h45fxahoqs3j GET https://markdownregistry.com/api/v1/resolve?ref=chrisallenlane/claude-swe-workflows/think-diagnose GET https://markdownregistry.com/api/v1/blob/7c309f53d8d4f7cd123a41b592147d1fb04dc5b74f66ae50a851990350a6c829
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.