CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

kopai/root-cause-analysis

Investigate and root-cause production issues from live OpenTelemetry telemetry (traces, logs, metrics) through the Kopai connector or the Kopai SDK in TypeScript code mode. Use this skill to debug errors and error-rate spikes, investigate latency/slowness and timeouts, trace requests across services, find failing or cascading services, and correlate logs to a trace — including vague symptom reports like 'why is my API slow', 'getting 500 errors', 'service is down', 'requests are timing out', or 'something is failing in prod', even when the user never says 'traces' or 'observability'. This analyzes existing telemetry to find a cause. Do NOT use it to add instrumentation (use otel-instrumentation), to build dashboards or visualizations (use create-dashboard), or to fix non-telemetry problems like failing CI, lint errors, unit tests, or SQL query tuning. For on-call alerts where ONCALL.md exists, use kopai-triage if it is installed (the Kopai plugin's on-call skills).

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files
Low

W011: Third-party content exposure detected (indirect prompt injection risk).

What this means

The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.

Why it was flagged

The required workflow runs aggregate and raw queries against the Kopai telemetry feed (traces, logs, metrics), which reads log Body, StatusMessage, and exception attributes that can carry user-supplied strings from unauthenticated OTLP ingestion, without the agent selecting a specific item first.

Where we found it

api.kopai.app

domain · 2 sites

The plugin connects to the Kopai API (api.kopai.app) to query telemetry data (traces, logs, metrics). The queries read log Body, StatusMessage, and exception attributes (exception.type, exception.message, exception.stacktrace) which can carry user-supplied strings from unauthenticated OTLP ingestion, creating an indirect prompt-injection vector.

SKILL.md

101

requests to `api.kopai.app` get the channel's Kopai credential

SKILL.md

103

`clientFromConfig({ url: "https://api.kopai.app/v2" })`

Report incorrect finding
Audited
Security analysis
Snyk