diagnostic-action
Use when the user asks why something happened, what’s wrong, root cause analysis, debugging, or incident explanation.
Best use case
diagnostic-action is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Use when the user asks why something happened, what’s wrong, root cause analysis, debugging, or incident explanation.
Use when the user asks why something happened, what’s wrong, root cause analysis, debugging, or incident explanation.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "diagnostic-action" skill to help with this workflow task. Context: Use when the user asks why something happened, what’s wrong, root cause analysis, debugging, or incident explanation.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/diagnostic-action/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How diagnostic-action Compares
| Feature / Agent | diagnostic-action | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when the user asks why something happened, what’s wrong, root cause analysis, debugging, or incident explanation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
github-actions-docs
Use when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows, artifacts, caching, secrets, OIDC, deployments, custom actions, or Actions Runner Controller, especially when they need official GitHub documentation, exact links, or docs-grounded YAML guidance.
interaction-design
Design and implement microinteractions, motion design, transitions, and user feedback patterns. Use when adding polish to UI interactions, implementing loading states, or creating delightful user experiences.
security-requirement-extraction
Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
error-diagnostics-smart-debug
Use when working with error diagnostics smart debug
error-diagnostics-error-trace
You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging,
error-diagnostics-error-analysis
You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.
azure-diagnostics
Debug and troubleshoot production issues on Azure. Covers Container Apps diagnostics, log analysis with KQL, health checks, and common issue resolution for image pulls, cold starts, and health probes. USE FOR: debug production issues, troubleshoot container apps, analyze logs with KQL, fix image pull failures, resolve cold start issues, investigate health probe failures, check resource health, view application logs, find root cause of errors DO NOT USE FOR: deploying applications (use azure-deploy), creating new resources (use azure-prepare), setting up monitoring (use azure-observability), cost optimization (use azure-cost-optimization)
control-loop-extraction
Extract and analyze agent reasoning loops, step functions, and termination conditions. Use when needing to (1) understand how an agent framework implements reasoning (ReAct, Plan-and-Solve, Reflection, etc.), (2) locate the core decision-making logic, (3) analyze loop mechanics and termination conditions, (4) document the step-by-step execution flow of an agent, or (5) compare reasoning patterns across frameworks.
star-story-extraction
Auto-invoke after task completion to extract interview-ready STAR stories from completed work.
resume-bullet-extraction
Auto-invoke after task completion to generate powerful resume bullet points from completed work.
design-spec-extraction
Extract comprehensive JSON design specifications from visual sources including Figma exports, UI mockups, screenshots, or live website captures. Produces W3C DTCG-compliant output with component trees, suitable for code generation, design documentation, and developer handoff.