Opik Integrations Auditor logo

Opik Integrations Auditor

Community
vincentkoc
opik-integrations-auditor

Audit, compare, and document Opik integrations across Python SDK, TypeScript SDK, and OTEL/API backend. Use when adding a new integration, reviewing an existing one, or generating first-pass integration docs and gap analysis.

Overview

Publishervincentkoc
Repositorydotskills
Skill nameopik-integrations-auditor
Stars
112
Forks
9
Bundled files
8
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 8 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by vincentkoc on GitHub. Read the source before you install it.

Installation

Install the Opik Integrations Auditor AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/vincentkoc/dotskills/tree/main/skills/opik-integrations-auditor
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/vincentkoc/dotskills.git /tmp/dotskills
mkdir -p .claude/skills
cp -r /tmp/dotskills/skills/opik-integrations-auditor .claude/skills/opik-integrations-auditor
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Opik Integrations Auditor in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Opik Integrations Auditor on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Opik Integrations Auditor is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Opik Integrations Auditor

Purpose

Audit, compare, and document Opik integrations across Python, TypeScript, and backend OTEL/API surfaces with a repeatable evidence-first workflow.

When to use

Use this skill when the task involves:

  • reviewing existing Opik integrations for behavior, coverage, or documentation quality
  • designing or implementing a new integration
  • producing integration pattern docs across Python, TypeScript, and OTEL/API
  • identifying gaps between code, tests, and docs

Required outputs

Produce these artifacts in the response (or files if asked):

  1. Integration inventory table
  2. Pattern classification per integration
  3. Cross-surface comparison matrix (Python / TypeScript / OTEL/API)
  4. Findings list (bugs/risks/gaps)
  5. Documentation patch plan
  6. Test plan (unit + integration + e2e)

Workflow

  1. Build inventory and classify pattern per integration.
  2. Extract behavior contract (capture, streaming, errors, flush, span hierarchy).
  3. Extract data contract (usage, metadata/tags, thread propagation).
  4. Validate backend compatibility (OTEL endpoint/protocol/mapping rules).
  5. Review tests for coverage and missing edge cases.
  6. Produce documentation updates with consistent template.

Load references as needed

  • For matrix schema and scoring: references/matrix-and-rubric.md
  • For pattern definitions: references/patterns.md
  • For evidence collection paths and commands: references/evidence-collection.md
  • For documentation update template: references/doc-template.md
  • For testing checklist: references/testing-checklist.md
  • For subagent prompt templates: references/subagent-prompts.md

Inputs

  • Integration scope (specific integration or full inventory)
  • Target surfaces to compare (Python, TypeScript, OTEL/API)
  • Relevant repo paths and branch/diff scope
  • Output expectations (table depth, doc patch format, test depth)

Outputs

  • Inventory and comparison matrix
  • Findings and risk summary
  • Documentation patch plan
  • Test plan with missing coverage calls

Default evidence locations (override if repo differs)

  • Python:
    • sdks/python/src/opik/integrations
    • sdks/python/design/INTEGRATIONS.md
    • sdks/python/design/TESTING.md
  • TypeScript:
    • sdks/typescript/design/INTEGRATIONS.md
    • sdks/typescript/design/TESTING.md
  • Backend OTEL:
    • apps/opik-backend/src/main/java/com/comet/opik/api/resources/v1/priv/OpenTelemetryResource.java
    • apps/opik-backend/src/main/java/com/comet/opik/domain/OpenTelemetryService.java
    • apps/opik-backend/src/main/java/com/comet/opik/domain/OpenTelemetryMapper.java
    • apps/opik-backend/src/main/java/com/comet/opik/domain/mapping/OpenTelemetryMappingRuleFactory.java
    • apps/opik-backend/docs/integrations.md

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Opik Integrations Auditor AI skill do?

Audit, compare, and document Opik integrations across Python SDK, TypeScript SDK, and OTEL/API backend. Use when adding a new integration, reviewing an existing one, or generating first-pass integration docs and gap analysis.

Why use Opik Integrations Auditor on TypingMind?

Because you install it once and use it with any model. Opik Integrations Auditor is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Opik Integrations Auditor in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vincentkoc/dotskills/tree/main/skills/opik-integrations-auditor. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Opik Integrations Auditor?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Opik Integrations Auditor?

As many as you like. As long as a model supports skills, you can use Opik Integrations Auditor with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Opik Integrations Auditor AI skill free?

Yes. It is published on GitHub by vincentkoc under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇