Diagnose and resolve active environmental, runtime, process, or tool failures.
npx skills add https://github.com/usurobor/cnos --skill troubleshoot-usurobor
Please help me install this Agent Skill. Skill: troubleshoot Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.eng/skills/eng/troubleshoot Command: npx skills add https://github.com/usurobor/cnos --skill troubleshoot-usurobor
Diagnose and resolve active environmental, runtime, process, or tool failures while work is blocked.
Describe the symptom and preserve evidence, then test the cheapest discriminating hypotheses in triage order.
High-intent search queries and answers about installing and using this skill.
To isolate root causes during a live debugging session, apply a hypothesis-driven approach by preserving evidence, testing the cheapest discriminating hypotheses first, and recording results to minimize guesswork.
The best triage order for troubleshooting runtime failures follows a structured sequence: process state, kernel logs, tool outputs, resources, lifecycle, and then application behavior.
Preserve evidence for incident management by capturing process states, kernel logs, and tool outputs before testing hypotheses, ensuring data remains available for RCA handoff during escalation.
Yes, you can use hypothesis-driven troubleshooting for multi-component tool errors. It applies to active environmental, runtime, and process failures across single-task flows and multi-component work.
Testing the cheapest hypotheses first when diagnosing tool failures minimizes risk and guesswork, allowing you to efficiently isolate root causes without unnecessary environmental changes.
gracefullightReproduces failures, identifies root cause, applies minimal fixes with regression tests.
blakeoxReconstruct incident timelines and perform root cause analysis from logs.
Mekann2904Analyze log files to extract error patterns and detect anomalies.
arvindbattulaDiagnose root-cause failures with a structured triage workflow.
