nw-root-why
From the author
Root cause analysis and debugging
Install
npx skills add nWave-ai/nWave --skill nw-root-why -a claude-code
Installs to .claude/skills/nw-root-why/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 84
Security100
Provenance74
Maintenance85
Licence100
Adoption46
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- nw-tr-review-criterianWave-ai/nWaveReview dimensions and scoring for root cause analysis quality assessmentEngineering★ 622
- source-codingparcadei/Continuous-Claude-v3Problem-solving strategies for source coding in information theoryEngineering★ 3.9K
- gsd:debugdavepoon/buildwithclaudeSystematic debugging with persistent state across context resetsEngineering★ 3.7K
- nw-der-review-criterianWave-ai/nWaveEvaluation criteria and scoring for data engineering artifact reviewsEngineering★ 622
- systematic-debuggingmvschwarz/openrigUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesEngineering★ 8.1K
- debugging-and-error-recoveryaddyosmani/agent-skillsGuides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than guessing.Engineering★ 109.8K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in