Opik Explain

by comet-ml

Opik Explain is an AI Engineering skill for Claude Code, published by comet-ml in opik-mcp.

217 stars35 forkson comet-ml/opik-mcpAdded 2026/09/04Repository updated 2026/09/03

View source on GitHub Download repo ZIP

claude-codegenerative-aillm-observabilitymcpmcp-servermodel-context-protocolopikpython

Install in seconds

Install Opik Explain

Copy Opik Explain into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/comet-ml/opik-mcp/tree/main/src/opik_mcp/skills/opik-explain ~/.claude/skills/opik-explain

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/comet-ml/opik-mcp.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: src/opik_mcp/skills/opik-explain/SKILL.md in comet-ml/opik-mcp
Installs to: ~/.claude/skills/opik-explain
Collection: One of 5 skills cataloged from this repository
Category: AI Engineering — 2970 skills

What Opik Explain does

Opik Explain roots cause a specific Opik trace or trace pattern and ties the explanation to evidence spans. Use it to debug failed, wrong, or slow traces without changing code.

Opik Explain is cataloged under AI Engineering on DirSkills. Opik Explain comes from a repository tagged claude-code, generative-ai, llm-observability, mcp and mcp-server.

Documentation

README

Excerpt

Explain — Root-Cause an Opik Trace and Ground It in the Code

Definition of done: a grounded root cause for the requested trace (or pattern), tied to specific evidence spans and paired with exactly one suggested next step. "Grounded" means the explanation names the failing/anomalous span and connects it to the code or data that produced it — not a restatement of the trace. If the target can't be fetched or read, stop at the first genuine blocker and return one concrete next step. A trace dump is not an explanation.

Operate: investigate over the real trace data, reason against the repo, commit to a single most-likely root cause with its evidence — and change no code. This skill is read-only by design.

Inputs

This is the opening of the README. Read the full README on GitHub.

Commands Opik Explain provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

/opik-explain
/opik-test

Frequently asked about Opik Explain

What else does comet-ml publish alongside Opik Explain?
Opik Explain is one of 5 skills that DirSkills catalogs from comet-ml/opik-mcp, the repository it ships in. Its siblings there include Instrument, Opik and Opik Diagnose. Each one is a separate skill with its own page in this directory, installs the same way Opik Explain does, and is maintained by comet-ml in that same repository. The rest of the collection is listed on the comet-ml/opik-mcp page.
How does Opik Explain compare to other AI Engineering skills?
Opik Explain ranks #2622 by stars among the 2970 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Opik Explain against them. Open each page to compare what they document and how they install.