Rca
Root cause analysis for bugs, incidents, failed tests, build errors, outages, and unexpected behavior. Use when the user asks for RCA, root cause, why something failed, or asks to diagnose a problem from code, logs, tests, traces, tickets, or terminal output.
Install
$ agentstack add skill-kaynetik-skills-rca ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-kaynetik-skills-rca) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Root Cause Analysis
Goal
Find the most likely root cause from available evidence. Stay brief, explicit, and falsifiable.
Method
- Identify the context: language, framework, runtime, toolchain, environment, and failure mode.
- Separate observed facts from assumptions. Do not invent missing logs, code paths, services, timings, or user actions.
- Trace backward from the symptom to the earliest credible cause.
- Prefer causes supported by code, logs, tests, config, version changes, or reproducible behavior.
- If evidence is incomplete, say what is unknown and name the next smallest check.
Output
Use this format unless the user asks otherwise:
Root cause:
Evidence:
-
-
Fix:
-
Confidence: because Rules
- Be concise. Do not pad with process language.
- Do not speculate beyond the evidence. Label hypotheses as hypotheses.
- Do not recommend broad rewrites unless the evidence points there.
- Do not hide uncertainty.
- When multiple causes are plausible, rank them by evidence and propose one discriminating check.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: kaynetik
- Source: kaynetik/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.