diagnostic-action
Use when the user asks why something happened, what’s wrong, root cause analysis, debugging, or incident explanation.
npx skills add majiayu000/claude-skill-registry --skill action-diagnostic --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.
# Diagnostic Action Skill ## Purpose Identify and explain likely causes of an observed problem or symptom. ## When to use - “Why did this happen?” - Root cause analysis - Debugging / incident investigation - Failure analysis Do NOT use for: - recommendations or fixes (use prescriptive-actions) - plans or procedures (use planning-action / procedural-action) ## Operating rules 1. Restate symptoms and scope clearly. 2. Generate multiple plausible hypotheses. 3. Explain the mechanism for each hypothesis. 4. Rank by likelihood and impact. 5. Identify missing data that would disambiguate causes. 6. Do not prescribe fixes unless explicitly asked. ## Outputs ### Symptoms & scope ### Hypotheses (ranked) - Cause - Mechanism - Evidence for/against - Confidence ### Most likely causes ### Data needed / open questions
- Purpose
- When to use
- Operating rules
- Outputs
- Symptoms & scope
- Hypotheses (ranked)
- Most likely causes
- Data needed / open questions
What does the diagnostic-action skill do?
Use when the user asks why something happened, what’s wrong, root cause analysis, debugging, or incident explanation.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill action-diagnostic --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.