Opik Diagnose

What it does

When your agent uses it

• What is broken in production
• Which traces need attention
• Which tool calls are failing
• Triage my agent

Example prompts

• “what is broken in production”
• “which traces need attention”
• “find failing or slow traces”
• “/opik-diagnose”

Requirements

• Python 3
• A credential in OPIK_API_KEY
• Compatibility (from SKILL.md): Tested with Claude Code; works with any Agent Skills-compatible host (Cursor, VS Code Copilot, Codex). Requires a Python or TypeScript project with Opik configured and a project that has traces. Install the `opik` skill alongside this one — it holds the shared SDK and observability references; without it, this skill falls back to the public docs.
• Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash

Workflow steps

7 steps, taken from the step headings in SKILL.md.

1. 1Resolve scope
2. 2Read the project once, for the shape of the week
3. 3Start from Diagnostics issues
4. 4Pull candidate traces to fill the gaps — MCP first, SDK fallback
5. 5Rank the remaining traces by signal
6. 6Stay in scope
7. 7Report

What it can do on your machine

Read from SKILL.md and the folder at commit e737581. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Grep
  • Glob
  • Bash

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships script files (Python), which the agent can run.

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • comet.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • OPIK_API_KEY

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  Tested with Claude Code; works with any Agent Skills-compatible host (Cursor, VS Code Copilot, Codex). Requires a Python or TypeScript project with Opik configured and a project that has traces. Install the `opik` skill alongside this one — it holds the shared SDK and observability references; without it, this skill falls back to the public docs.

  From compatibility in the SKILL.md frontmatter.

Context cost

Opik Diagnose loads about 2.7k tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 213 tokens; SKILL.md has 1,350 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~213

When it runs · the whole SKILL.md, loaded when a task matches

~2.7k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~4.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

  allowed-tools: Read, Grep, Glob, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from comet-ml/opik-mcp at commit e737581, republished under its Apache-2.0 licence (© comet-ml). 1,350 words, ~2,749 tokens.

name

opik-diagnose

description

Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agent_insights_issue entities, offers to turn Diagnostics on when the project has it switched off, then fills the gaps with list (filters, sort, a time window); without the MCP it reads the same via the SDK (agent_insights and search_traces), so it works with no MCP. Returns a ranked shortlist, each item ready to hand to the explain skill. Use for "what is broken in production", "which traces need attention", "find failing or slow traces", "which tool calls are failing", "triage my agent". Not for offline experiment results (use evaluate or compare) and not for root-causing one trace (use explain).

allowed-tools

Read, Grep, Glob, Bash

compatibility

Tested with Claude Code; works with any Agent Skills-compatible host (Cursor, VS Code Copilot, Codex). Requires a Python or TypeScript project with Opik configured and a project that has traces. Install the `opik` skill alongside this one — it holds the shared SDK and observability references; without it, this skill falls back to the public docs.

metadata.last_updated

2026-09-09

metadata.source_commit

2.0.0

metadata.argument-hint

[optional: project name, or what to look for]

list('agent_insights_issue', project_name='<project>')        # open issues, ranked as the Diagnostics page ranks them
read('agent_insights_issue', '<issue id>', project_name='<project>')
#  → {issue: {name, cause, suggested_fix, severity, status, …}, example_trace_ids: [...], details: [...],
#     url: '<the issue's Diagnostics page>', trace_url_template: '<…/logs?trace={trace_id}>'}

© comet-ml, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 12 other files (references) in src/opik_mcp/skills/opik-diagnose of comet-ml/opik-mcp.

• SKILL.md
• evals/.gitignore
• evals/HARNESS.md
• evals/cases.yaml
• evals/fixtures/seed/pyproject.toml
• evals/fixtures/seed/seed.py
• evals/grader.py
• evals/metrics.py
• evals/run_evals.py
• references/diagnostics-list.md
• references/examples.md
• references/output-shape.md
• references/trace-queries.md

Open the folder on GitHubat commit e737581