leanbusqts/troubleshoot
templates/base/skills/troubleshoot/SKILL.md
Isolate root causes and propose targeted fixes with clear validation steps.
$ install --global
skillsauthnpx skillsauth add leanbusqts/agent47 troubleshootInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 9:08 AM129.5s1 file scanned
SKILL.md
- name:
- troubleshoot
- description:
- Isolate root causes and propose targeted fixes with clear validation steps.
- compatibility:
- Designed for skills-compatible coding agents.
- category:
- troubleshooting
- tags:
- [debugging, incident, root-cause]
- applies_to:
- [frontend, backend, cli, scripts, mobile]
- priority:
- core
- agents:
- [universal, codex]
- repo_shapes:
- [app, library, cli, scripts, monorepo]
Troubleshoot
Objective
- Reproduce and isolate the issue.
- Identify the most probable root cause and next actions.
When to use
- A bug or failure is reported or observed.
- Symptoms are unclear and need narrowing down.
Inputs
- User-reported symptoms, logs, or reproduction steps.
- AGENTS.md, rules, relevant code/tests.
- Environment details if available.
Process
- Confirm and restate the symptom; note missing repro info.
- Form quick hypotheses; prioritize simplest checks.
- Collect minimal evidence (logs/tests/inputs) to confirm/deny hypotheses.
- Identify the likely root cause or narrow to top candidates.
- Propose next actions (fix path or deeper check) and validation steps.
Outputs
- Likely root cause (or narrowed hypotheses).
- Evidence collected and what’s still unknown.
- Proposed fix direction and validation plan.
Edge cases
- If repro is missing, request exact steps or data.
- Avoid broad changes; focus on evidence-driven narrowing.
Related Skills
leanbusqts/cli-design
tools
VerifiedTrustedCommunity
Design or refine command surfaces, output contracts, and preview flows for CLI tools.
2SKILL.mdUpdated May 1, 2026
leanbusqts/spec-clarify
tools
VerifiedTrustedCommunity
Ask targeted questions to clarify scope, edge cases, and acceptance before coding.
2SKILL.mdUpdated May 1, 2026
leanbusqts/review
tools
VerifiedTrustedCommunity
Inspect changes for correctness, risks, and regressions before accepting them.
2SKILL.mdUpdated May 1, 2026
leanbusqts/refactor
development
VerifiedTrustedCommunity
Improve structure and clarity without changing externally visible behavior.
2SKILL.mdUpdated May 1, 2026