think-diagnose
Abductive reasoning about causes. Takes a phenomenon, separates observations from interpretations, then spawns diagnosticians applying different reasoning lenses (technical, human-factors, process, incentive-structure, environmental, temporal, measurement-artifact, statistical) in isolation. Orchestrator evaluates candidate causes for fit-against-evidence, calibrates confidence honestly, and reports leading candidate(s) with distinguishing evidence needed. Produces feedback only — no code, no tickets, no artifacts.
Profile →npx skills add majiayu000/claude-skill-registry --skill think-diagnose --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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) - Calibrate confidence hone
- Roles
- Workflow
- 1. Receive the Phenomenon
- 2. Gather Evidence — Separate Observation from Interpretation
- 3. Choose Reasoning Lenses
- 4. Spawn Diagnosticians (Parallel, Isolated)
- 5. Evaluate Fit — Orchestrator's Work
- 6. Calibrate Confidence
- 7. Report
- 8. No Iteration
- Constraints
- When to Use
- Relationship to Other Skills
- Philosophy
What does the think-diagnose skill do?
Abductive reasoning about causes. Takes a phenomenon, separates observations from interpretations, then spawns diagnosticians applying different reasoning lenses (technical, human-factors, process, incentive-structure, environmental, temporal, measurement-artifact, statistical) in isolation. Orchestrator evaluates candidate causes for fit-against-evidence, calibrates confidence honestly, and reports leading candidate(s) with distinguishing evidence needed. Produces feedback only — no code, no tickets, no artifacts.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill think-diagnose --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.