diagnose
Routes a vague symptom or complaint to the most relevant Clairvoyance skill via a decision tree. Use when someone describes a problem but doesn't know which skill to reach for. Not for running a comprehensive review (use design-review) or scanning a checklist (use red-flags).
npx skills add majiayu000/claude-skill-registry --skill diagnose-codybrom-clairvoyance --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.
# Diagnose When invoked with $ARGUMENTS, match the described symptom against the decision tree below and route to the appropriate skill. If code paths are referenced, read them first to confirm the match before routing. This skill routes to other skills from Clairvoyance (https://clairvoyance.fyi). It works best when the full collection is installed. ## Decision Tree ### 1. "Something feels wrong but I can't say what" The symptom is a general sense of unease with no concrete complaint. → **complexity-recognition**: Apply the three-symptom framework to locate the source. ### 2. "Simple changes require edits in many files" Change amplification. Branch by cause: - Shared knowledge is scattered across modules → **information-hiding** (look for leaked implementation details) - Old abstractions no longer fit the current shape of the system → **code-evolution** (check whether the design has kept pace with requirements) - Module boundaries cut across concerns instead of encapsulating them → **module-boundaries** (re-evaluate decomposition) ### 3. "This interface is awkward / too many parameters" The interface exposes too much or forces callers to assemble details they shouldn't need. - Imp
- Decision Tree
- 1. "Something feels wrong but I can't say what"
- 2. "Simple changes require edits in many files"
- 3. "This interface is awkward / too many parameters"
- 4. "I can't name this thing"
- 5. "Errors everywhere / too many exceptions"
- 6. "Layers feel redundant / wrappers add nothing"
- 7. "Comments are useless / missing / stale"
- 8. "Code was written under pressure"
- Multiple Symptoms
- Fallback
What does the diagnose skill do?
Routes a vague symptom or complaint to the most relevant Clairvoyance skill via a decision tree. Use when someone describes a problem but doesn't know which skill to reach for. Not for running a comprehensive review (use design-review) or scanning a checklist (use red-flags).
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill diagnose-codybrom-clairvoyance --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.