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.

77

Quality

97%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted skill that provides clear, actionable guidance for root cause analysis using Kopai CLI. The workflow is well-sequenced with concrete commands and fallback strategies. The main weakness is that referenced files (rules/*.md, references/*.md) cannot be verified since no bundle was provided, and the Rules section's format could be clearer about what each entry represents.

Suggestions

Clarify the Rules section format — currently the bullet items look like labels without clear instruction on how/when to apply them. Consider briefly describing what each rule file contains or when to consult it.

Provide the referenced bundle files (rules/*.md, references/*.md) to support the progressive disclosure structure, or consolidate critical content inline if the files don't exist.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It assumes Claude's competence with CLI tools and observability concepts, avoids explaining what traces/logs/metrics are, and every section earns its place. The prerequisites are minimal and appropriate.

3 / 3

Actionability

Provides fully executable CLI commands with specific flags (--status-code ERROR, --json, --severity-min 17), a concrete example workflow with real command sequences, and actionable tips like using jq for filtering. Commands are copy-paste ready.

3 / 3

Workflow Clarity

The RCA workflow is clearly sequenced (find errors → get context → correlate logs → check metrics → present findings) with explicit fallback guidance at step 1 ('if empty: broaden time range, check service name'). The workflow includes validation checkpoints and a clear error recovery path.

3 / 3

Progressive Disclosure

References to rules/<rule-name>.md and references/*.md files are well-signaled and one level deep, but no bundle files were provided to verify these exist. The Rules section lists workflow and pattern rules but their format (bullet list of rule names) is somewhat unclear — it's not obvious whether these are just labels or actionable references without seeing the actual files.

2 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that clearly communicates what the skill does (telemetry-based root cause analysis via Kopai CLI), when to use it (with explicit trigger scenarios), and includes natural user language that would realistically trigger selection. It uses proper third-person voice throughout and provides both technical and colloquial trigger terms, making it robust for skill selection across diverse user queries.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'root cause analysis', 'debugging errors', 'investigating latency issues', 'tracing request flows across services', 'correlating logs with traces'. These are clear, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (analyze telemetry data for root cause analysis using Kopai CLI) and 'when' (explicit 'Use when...' clause with multiple trigger scenarios including both technical and natural-language user complaints).

3 / 3

Trigger Term Quality

Excellent coverage of natural user language including 'why is my API slow', 'getting 500 errors', 'service is down', 'requests are timing out', plus technical terms like 'telemetry', 'traces', 'latency', 'logs'. The note about triggering even without explicit observability mentions is particularly strong.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific tool name 'Kopai CLI', the telemetry/observability domain, and the focus on production debugging with traces and logs. Unlikely to conflict with general debugging or logging skills due to the specific scope.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents