Skip to content
Skills Library
Programming · Analysis

nth-problem-analysis

/nth-problem-analysis

Use when the user asks to diagnose, debug, or find the root cause of an observed failure (error, crash, wrong output, flaky, intermittent, or regressed behavior) whose cause is not yet known, especially when a previous fix failed or several causes are plausible. Not for obvious one-line bugs, design questions without a failure, or misbehaving Claude instructions (nth-prompt-engineer).

Repository
nth-dev-kit ↗
Licence
MIT
Last repository change
03.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 03.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user asks to diagnose, debug, or find the root cause of an observed failure (error, crash, wrong output, flaky, intermittent, or regressed behavior) whose cause is not yet known, especially when a previous fix failed or several causes are plausible. Not for obvious one-line bugs, design questions without a failure, or misbehaving Claude instructions (nth-prompt-engineer).

Original author description

Use when the user asks to diagnose, debug, or find the root cause of an observed failure (error, crash, wrong output, flaky, intermittent, or regressed behavior) whose cause is not yet known, especially when a previous fix failed or several causes are plausible. Not for obvious one-line bugs, design questions without a failure, or misbehaving Claude instructions (nth-prompt-engineer).

How it works

  1. Procedure
  2. Output
Original SKILL.md headings · 25 lines, 263 words
SKILL.md preview
---
name: nth-problem-analysis
description: Use when the user asks to diagnose, debug, or find the root cause of an observed failure (error, crash, wrong output, flaky, intermittent, or regressed behavior) whose cause is not yet known, especially when a previous fix failed or several causes are plausible. Not for obvious one-line bugs, design questions without a failure, or misbehaving Claude instructions (nth-prompt-engineer).
metadata:
  managed-by: nth-claude-kit
---

# Problem analysis

Find the actual root cause before proposing a fix. This skill is an analysis procedure only. Do not edit code just because it was invoked. The main conversation decides whether and how to implement afterward. It is not `reviewer`, which reviews completed changes, and not `verifier`, which runs noisy checks.

## Procedure

1. **State the failure.** Record exactly what happens, where, and with which inputs, compared with what was expected.
2. **Separate observations from assumptions.** Treat every assumption as unverified until evidence supports it.
3. **Gather the smallest useful evidence.** Use the failing path, logs, recent changes, or a targeted reproduction. Use Explore only when broad codebase investigation would materially help.
4. **Form 2–4 plausible hypotheses.** For each one, note which evidence would confirm it and which would falsify it.
5. **Check the highest-value evidence first.** That is the check that eliminates the most hypotheses for the least cost. Drop hypotheses the evidence does not support.
6. **Name a root cause only when the evidence supports it.** If it does not yet, say so and name the next check that would tell the remaining hypotheses apart.

## Output

Give concise, visible findings. Do not narrate your internal thought process.

- **Observed failure**
- **Hypotheses**: for each, the evidence that confirmed or eliminated it
- **Root cause**, or "not yet established" plus the next check
- **Contributing factors** and **symptoms**, kept separate from the root cause
- **Corrective direction**: the smallest change that addresses the root cause
- **Verification**: how to confirm the fix works and the symptom does not return

Versions

The database has no other skills named nth-problem-analysis.

Database snapshot: 13.11.2026 · package version fa34f5a67994 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90root-cause-first
    Debugging discipline. Use whenever diagnosing a bug, error, test failure, crash, regression, flaky behavior, or unexpected output, and especially before applying any fix. Also trigger when a previous fix attempt did not work and another attempt is about to be made.
  • 100debug-failure
    Find the root cause of an error, crash, failing test, regression or wrong behaviour, then fix it with a regression test. Use this whenever something is broken or behaves unexpectedly and the cause is not already proven, even if a fix seems obvious. Do not guess at fixes.
  • 90investigate-debug
    Use when something is wrong and the cause is not yet known — failures, regressions, flaky behaviour, performance problems, incidents, or a user report that does not match what the code appears to do. Concerns holding the difference between what is observed and what is believed,…
  • 100v1-debug
    Use when an observable problem is wrong, recurring, or unexplained and needs root-cause diagnosis. Triggers on "debug this", "why is this failing", or "find the root cause".
  • 85vibe-debug
    Find the root cause before changing anything — for a bug, a test failure, a check that went red, or behaviour nobody can explain. Use when the cause is not yet known, when a previous fix did not hold, or when the same symptom has come back.
  • 100systematic-debugging
    Use when something is broken — an error message, stack trace, failing test, crash, wrong output, "it doesn't work", build failure, or unexpected behavior. Finds the root cause with evidence before changing code, then saves the fix to memory.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.