CtrlK
BlogDocsLog inGet started
Tessl Logo

opik-integrations

Build, update, test, and document Opik SDK integrations (Python & TypeScript). Use when adding a new framework/provider integration under sdks/python/src/opik/integrations or sdks/typescript/src/opik/integrations, updating an existing one, or verifying that an integration logs traces correctly.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-architected skill body that balances a lean overview with clearly signaled references to deeper material, a concrete clone-the-sibling decision tree, and a phased workflow with verification checkpoints. The main gap is that the most actionable, executable detail is delegated to referenced files rather than appearing inline.

Suggestions

Tighten the OpenTelemetry paragraph (line 51): move the backend-first rationale and SpanProcessor/SpanExporter building-block detail into python.md/typescript.md, leaving only the routing decision in SKILL.md.

Add one short inline executable snippet or exact command for the verify step (e.g., the Opik MCP read/list invocation) so the core feedback loop is copy-paste ready without opening workflow.md.

Surface the validation feedback loop (verify -> fix -> re-verify) explicitly in the at-a-glance phase list rather than only referencing the Opik-MCP verification loop by name.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no basic-concept padding), and most tokens earn their place, though the OpenTelemetry paragraph is somewhat explanatory and could be trimmed slightly.

4 / 5

Actionability

Concrete guidance is provided via the clone-source decision tree, named patterns (BaseTrackDecorator, BaseTracer, SpanProcessor), and exact file paths, but the executable steps themselves are delegated to referenced files rather than shown inline.

4 / 5

Workflow Clarity

The 0–8 phase sequence is clearly ordered with explicit verify and test checkpoints and a referenced Opik-MCP verification loop, but the detailed validation feedback steps live in workflow.md rather than in this overview.

4 / 5

Progressive Disclosure

The SKILL.md is a clear overview with well-signaled, one-level-deep markdown links to workflow.md, python.md, and typescript.md, with detail appropriately split out and a section explicitly listing skills it builds on to avoid duplication.

5 / 5

Total

17

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description that clearly answers both what the skill does and when to use it, with natural trigger phrases and specific file-path anchoring. Its only weakness is minor overlap risk with the sibling external-integrations skill, which is not disambiguated within the description itself.

DimensionReasoningScore

Specificity

"Build, update, test, and document Opik SDK integrations (Python & TypeScript)" lists four concrete actions on a well-scoped domain, but the verbs are somewhat high-level compared to fully concrete mechanism descriptions, so it sits above the midpoint rather than at the top anchor.

4 / 5

Completeness

It explicitly states what the skill does and follows with a clear "Use when..." clause containing three concrete trigger scenarios, matching the top anchor for both what and when.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ("adding a new framework/provider integration", "updating an existing one", "verifying that an integration logs traces correctly") plus concrete file paths, giving good keyword coverage though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The path-qualified "Opik SDK integrations" niche is mostly distinct, but the description does not disambiguate from the closely related opik-external-integrations skill, leaving minor overlap risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing

Warning

Total

15

/

16

Passed

Repository
comet-ml/opik
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.