Borrowing it
Nothing to install: this file belongs to rakovi4/continue-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rakovi4/continue-framework/main/.claude/skills/rca/SKILL.mdgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/rakovi4/continue-framework/rca)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/rca"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/rca/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rakovi4/continue-framework/rca"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/rca.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00057 | $0.01050 |
| Opus 5.5 | $0.00023 | $0.00420 |
| Sonnet 5.5 | $0.00011 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
rca scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/rca - Root Cause Analysis
Find the real cause of a defect from evidence, not speculation. The deliverable is a cause you have confirmed against real data — logs, test runs, query plans, measurements you actually pulled — recorded in the task spec.md. Producing a plausible-sounding story is the failure mode this skill exists to prevent: a narrative that was never checked against data is a guess, even when it reads like a conclusion.
Input
- target (optional): bugfix task number/slug, or a free-text symptom. If absent, infer from the current task or conversation.
- evidence sources (optional): credentials or paths for authoritative data (CI API, log locations, a reproducible environment). When provided, use them — do not substitute a guess for data you could fetch.
Core Principle
Every prior claim is a hypothesis until you re-verify it here — including claims already written in spec.md, an earlier RCA attempt, a code comment, or this conversation. Carrying a prior hypothesis forward as established fact is the exact failure this skill exists to prevent. Re-derive each claim from primary evidence, or mark it unverified. Distinguish MEASURED (you observed it directly) from REASONED (you inferred it from code plus rules) on every statement, and never present REASONED as MEASURED.
Workflow
-
State the symptom precisely. Pull the exact observable from its authoritative source — the test report, the log line, the failing assertion message — with exact values, units, and frequency, not a paraphrase. For an intermittent failure, get the real pass/fail count and the measured values on both sides of the boundary. Quote the source. Confirm which value the assertion actually checks (it is often not the one a summary reports).
-
Audit prior assumptions. List every claim the existing write-up, prior RCA, comments, or conversation treats as known. For each, record a status — verified (with evidence), refuted (with evidence), or unverified — and reuse no prior conclusion you have not personally re-confirmed.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 51 lines · 57 tokens per session scan A cdbc35fa51f3
rca is a skill published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 57 tokens to every session and 1,050 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…