New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Opik External Integrations

by comet-ml in comet-ml/opik

Builds Opik tracing integrations that live outside the Opik repository, either as standalone opik-* packages or as contributions into projects such as LiteLLM or Dify.

Apache-2.0Auto-check passedAI & LLM Engineering

Install Opik External Integrations

skills CLI
$ npx skills add comet-ml/opik --skill opik-external-integrations -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install comet-ml/opik opik-external-integrations --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/comet-ml/opik.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/opik-external-integrations .claude/skills/opik-external-integrations && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
opik-external-integrations
GitHub stars
22k
Token cost
~1.3k tokens
SKILL.md length
637 words
Files
3
Skills in repo
19
Repo updated
First seen
Licence
Apache-2.0

At a glance

Builds Opik tracing integrations that live outside the Opik repository, either as standalone opik-* packages or as contributions into projects such as LiteLLM or Dify.

  • Works in 2 steps: Follow the HOST repo's conventions, not… → Consume Opik through its PUBLISHED…
  • Building a standalone opik-* plugin or package for a new agent framework
  • SKILL.md covers Two principles that make…, Start with the questionnaire, The workflow and How this maps to the internal…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This skill covers Opik integrations whose code lives in another repository. There are two shapes: a standalone opik-* package or plugin that depends on the published Opik SDK, with opik-openclaw and opik-claude-code-plugin as examples, and an upstream contribution that adds Opik support to a third-party project with its own logging, callback or plugin system, such as a callback in LiteLLM or an integration in Dify.

An activation gate limits use to external targets; integrations that ship under sdks/python or sdks/typescript belong to the opik-integrations skill. Two principles apply: follow the host repository's conventions for structure, dependencies, linting, tests and docs, mirroring its closest existing integration, and use Opik only through its published Python or TypeScript SDK or the REST API, never internal modules.

Work starts with a free-form questionnaire covering which external repo or package, the integration shape, the host language and stack, where the Opik code goes, how the host tests and documents, and how to run it to verify. A references file lists known external integrations, including the cookiecutter template and hosts like LiteLLM, Dify and n8n, and a workflow file holds the phases.

When your agent uses it

  • Building a standalone opik-* plugin or package for a new agent framework
  • Contributing Opik tracing support into a third-party project
  • Updating an existing external Opik integration after an SDK change
  • Finding the closest existing integration to copy before starting a new one

Example prompts

  • “Build an Opik integration as a standalone opik-* package for this agent framework repo.”
  • “I want to add an Opik callback to LiteLLM. Start with the questions you need answered.”
  • “Update the opik-claude-code-plugin to use the latest published Opik SDK.”
  • “Which known external Opik integrations are closest to a plugin for n8n?”

Requirements

  • The external repository or package you are targeting, checked out locally
  • The published Opik Python or TypeScript SDK

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Follow the HOST repo's conventions, not this repo's. Structure, dependency management, lint/format, test framework, docs, and the…
  2. Consume Opik through its PUBLISHED public API. Use the released opik (Python) / opik (TypeScript) SDK or the REST API — the same surface…

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Opik External Integrations loads about 1.3k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 637 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~100
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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 at commit f217a86, republished under its Apache-2.0 licence (© comet-ml). 637 words, ~1,285 tokens.

Download SKILL.mdSave it as .claude/skills/opik-external-integrations/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
opik-external-integrations
description
Build or update an Opik integration that lives OUTSIDE this repo — a standalone opik-* package (e.g. opik-openclaw, opik-claude-code-plugin) or Opik support contributed into a third-party project (e.g. LiteLLM, Dify). Use ONLY when the user names an external repository or external package as the target; for integrations under sdks/ use the opik-integrations skill instead.

Opik External Integrations

This skill builds Opik integrations whose code does not live in this repository. Two shapes:

  • Standalone opik-* package / plugin — its own repo or package that depends on the published Opik SDK. Examples: opik-openclaw, opik-claude-code-plugin.
  • Upstream contribution — Opik support added into a third-party project that already has its own logging/callback/plugin system. Examples: an Opik callback in LiteLLM, an Opik integration in Dify.

Activation gate — read this first. Use this skill only when the target lives in an external repo or external package. If the user wants an integration that ships inside sdks/python/src/opik/integrations/ or sdks/typescript/src/opik/integrations/, this is the wrong skill — use opik-integrations. When in doubt, ask the "where does it live" question (below) and route accordingly.

Two principles that make external work different

  1. Follow the HOST repo's conventions, not this repo's. Structure, dependency management, lint/format, test framework, docs, and the contribution guide are dictated by the target project. Do not impose sdks/ layout, fake_backend, or Fern docs on an external repo. Read its CONTRIBUTING/AGENTS.md and mirror its closest existing integration/plugin.
  2. Consume Opik through its PUBLISHED public API. Use the released opik (Python) / opik (TypeScript) SDK or the REST API — the same surface end users get. Never import this repo's internal modules (opik.decorator.*, rest_api, message-processing internals); they are not available outside this repo and are not a stable contract.

Start with the questionnaire

Collect everything up front, free-form — do not propose a target. See workflow.md Phase 0 for the full list. The essentials: which external repo/package (URL + links), integration shape (standalone package vs. upstream contribution vs. plugin), host language/stack, where the Opik code goes, how the host tests and documents, and how to run it to verify.

Once you know the target, check references.md — a curated list of known external integrations (standalone opik-* plugins incl. the cookiecutter template, and third-party host repos like LiteLLM / Dify / n8n) with their repo and Opik-docs URLs. If the target is listed or resembles one, start from its links and clone the closest sibling instead of researching blind.

Show full SKILL.md (302 more words)Show less

The workflow

Multi-step and autonomous by default (front-load preparation, run through, self-verify, end with a report); ask for the interactive variant to approve the design first. Full playbook in workflow.md. At a glance:

  1. Questionnaire + acquire the external repo (clone/checkout into the scratchpad).
  2. Investigate the host — its integration/plugin conventions, dep management, test framework, docs, contribution guide. Find the closest existing integration to clone.
  3. Investigate the Opik surface — pick the public API to use: @opik.track / track_* wrappers, the low-level client, or REST. Lean on the opik and instrument skills for the public API.
  4. Design how Opik plugs into the host's extension point (callback hook, plugin entrypoint, middleware). Map host data → Opik trace/span fields.
  5. Implement in the host checkout, mirroring its closest sibling and its style.
  6. Verify via the Opik MCP — run the host with the integration active, log to the workspace the MCP reads, and read the trace/spans back. Loop until correct.
  7. Test using the host's test framework and conventions.
  8. Document following the host's docs conventions; optionally add/point an Opik docs page (write-docs).
  9. Report — what was done, verification evidence, a per-flow supported/tested table, limitations, and how to open the upstream PR.

How this maps to the internal skill

The mechanism knowledge is shared — how a provider/framework exposes hooks, streaming, and usage is the same problem as in opik-integrations. Read that skill's python.md / typescript.md for the patterns (method patching, callback handler, OTel), but apply them against the published SDK surface and inside the host repo's structure.

Skills this one builds on (do not duplicate them)

  • opik / instrument — the user-facing public API surface (the right way to consume Opik from outside).
  • opik-integrations — the integration mechanism patterns (patching / callback / OTel) and field mapping.
  • write-docs — only if you also add an Opik-side docs page pointing at the external integration.

© 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 2 other files in .agents/skills/opik-external-integrations of comet-ml/opik.

  • SKILL.md
  • references.md
  • workflow.md

Open the folder on GitHubat commit f217a86

Compare with similar skills

Opik External Integrations next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Opik External Integrations compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Opik External Integrations this skillcomet-ml/opik22k—~1.3kAutomated safety check: PassApache-2.0
Failproof AI SDK IntegrationFailproofAI/failproofai5.3k—~6kAutomated safety check: PassCustom licence
Langchain Dependencieslangchain-ai/langchain-skills1.3k1 repos~3.6kAutomated safety check: PassMIT
SEO APIseranking/seo-skills160—~4.1kAutomated safety check: PassMIT
Phoenix Tracinggithub/awesome-copilot40k3 repos~1.6kAutomated safety check: PassApache-2.0
Phoenix Integration SnippetsArize-ai/phoenix12k—~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Failproof AI SDK Integration

    FailproofAI/failproofai

    Helps instrument a custom Python or TypeScript agent to record events for Failproof AI, verify what gets written, and run an evaluator worker that scores the runs.

    5.3k GitHub stars~6k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed

  • Langchain Dependencies

    langchain-ai/langchain-skills

    Official

    INVOKE THIS SKILL when setting up a new project or when asked about package versions, installation, or dependency management for LangChain, LangGraph, LangSmith, or Deep Agents.

    1.3k GitHub starsUsed in 1 repo~3.6k tokens
    AI & LLM EngineeringAuto-check passed

  • SEO API

    seranking/seo-skills

    SE Ranking API integration architect. An agent skill from seranking/seo-skills.

    160 GitHub stars~4.1k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed

  • Phoenix Tracing

    github/awesome-copilot

    Official

    OpenInference semantic conventions and instrumentation for Phoenix AI observability.

    40k GitHub starsUsed in 3 repos~1.6k tokens
    AI & LLM EngineeringAuto-check passed

  • Phoenix Integration Snippets

    Arize-ai/phoenix

    Generates onboarding code snippets for Phoenix tracing integrations and wires them into the project onboarding UI.

    12k GitHub stars~1.4k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

  • Phoenix Skills Audit

    Arize-ai/phoenix

    Audit recent changes to Phoenix's user-facing surfaces (Python clients, TypeScript clients, CLI, REST/GraphQL APIs) and patch the three external-facing agent skills — phoenix-tracing, phoenix-cli…

    12k GitHub stars~5.1k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

More from comet-ml/opik

All 19 skills in this repo

  • Add Opik Code Quality Hook

    comet-ml/opik

    Checklist for wiring a new linter into Opik's Code Quality pipeline: the four files to edit, the silent-failure gotchas and the pass/fail verification loop.

    22k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Opik Analytics Instrumentation

    comet-ml/opik

    Shows how to add product analytics events to Opik's frontend, Java backend and Python SDK, all reporting through Segment to PostHog with an opik_ name prefix.

    22k GitHub stars~4.4k tokensUpdated today
    Auto-check passed

  • Debugging Opik E2E Tests

    comet-ml/opik

    Investigates a failed Opik end-to-end test from CI, TestOps or a local run, decides regression versus flake, and proposes a fix without editing tests.

    22k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Opik Documentation Patterns

    comet-ml/opik

    Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.

    22k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Explore Feature E2E Test

    comet-ml/opik

    Turns a code change into one committed, passing Playwright end-to-end spec by resolving the change scope and handing authoring to a companion skill.

    22k GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Opik Local Dev Environment

    comet-ml/opik

    Starts, rebuilds, and troubleshoots the Opik local dev stack, including an optional Comet Platform integration mode for the Opik team.

    22k GitHub stars~734 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Opik External Integrations

What does Opik External Integrations do?

Builds Opik tracing integrations that live outside the Opik repository, either as standalone opik-* packages or as contributions into projects such as LiteLLM or Dify. This skill covers Opik integrations whose code lives in another repository. There are two shapes: a standalone opik-* package or plugin that depends on the published Opik SDK, with opik-openclaw and opik-claude-code-plugin as examples, and an upstream contribution that adds Opik support to a third-party project with its own logging, callback or plugin system, such as a callback in LiteLLM or an integration in Dify.

When should I use Opik External Integrations?

Opik External Integrations fits situations like: building a standalone opik-* plugin or package for a new agent framework; contributing Opik tracing support into a third-party project; updating an existing external Opik integration after an SDK change; finding the closest existing integration to copy before starting a new one.

How do I install Opik External Integrations in Claude Code?

Run `npx skills add comet-ml/opik --skill opik-external-integrations -a claude-code`. Or copy the skill folder (.agents/skills/opik-external-integrations in comet-ml/opik) into .claude/skills/opik-external-integrations in your project. Claude Code loads it when a task matches its description.

How do I install Opik External Integrations in Codex?

Run `npx skills add comet-ml/opik --skill opik-external-integrations -a codex`. Or copy the skill folder (.agents/skills/opik-external-integrations in comet-ml/opik) into .agents/skills/opik-external-integrations in your project. Codex loads it when a task matches its description.

Can I use Opik External Integrations in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add comet-ml/opik --skill opik-external-integrations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/opik-external-integrations, .gemini/skills/opik-external-integrations, .github/skills/opik-external-integrations and .opencode/skills/opik-external-integrations in your project.

What does Opik External Integrations need to run?

SKILL.md names no scripts, command-line tools or credentials: Opik External Integrations is instructions for the agent only. Our summary lists: The external repository or package you are targeting, checked out locally; The published Opik Python or TypeScript SDK.

Does Opik External Integrations access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Opik External Integrations safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Opik External Integrations use?

Opik External Integrations is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Opik External Integrations use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Opik External Integrations?

Skills that share tags, products or a category with Opik External Integrations: Failproof AI SDK Integration (FailproofAI/failproofai, 5.3k stars), Langchain Dependencies (langchain-ai/langchain-skills, 1.3k stars), SEO API (seranking/seo-skills, 160 stars) and Phoenix Tracing (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Opik External Integrations?

comet-ml (a GitHub organization) maintains it in comet-ml/opik, which has 22,412 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.

Source: comet-ml/opik on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.