CtrlK
BlogDocsLog inGet started
Tessl Logo

kopai/root-cause-analysis

Analyze telemetry data for root cause analysis using Kopai CLI. Use when debugging errors, investigating latency issues, tracing request flows across services, or correlating logs with traces. Also use when users report production issues like "why is my API slow", "getting 500 errors", "service is down", "requests are timing out", or any symptom that needs telemetry-based investigation — even if they don't mention traces or observability explicitly.

100

Quality

100%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

_sections.mdrules/

titleimpacttags
SectionsCRITICALindex, sections

Sections

Impact: CRITICAL

Section definitions for root cause analysis rules.

Sections

SectionImpactFiles
workflowCRITICALworkflow-find-errors.md, workflow-get-context.md, workflow-correlate-logs.md, workflow-check-metrics.md, workflow-identify-cause.md
patternHIGHpattern-http-errors.md, pattern-slow-requests.md, pattern-distributed.md, pattern-log-driven.md

SKILL.md

tile.json