Agent skill
diagnostic-action
Use when the user asks why something happened, what’s wrong, root cause analysis, debugging, or incident explanation.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/action-diagnostic
SKILL.md
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
- Restate symptoms and scope clearly.
- Generate multiple plausible hypotheses.
- Explain the mechanism for each hypothesis.
- Rank by likelihood and impact.
- Identify missing data that would disambiguate causes.
- 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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?