diagnostic-action
Use when the user asks why something happened, what’s wrong, root cause analysis, debugging, or incident explanation.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
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
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-28
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!