opik-external-integrations

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.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%

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

A lean, actionable, well-sequenced routing skill body that names specific APIs, modules to avoid, and a validated workflow. The one weak spot is progressive disclosure: the body points to workflow.md and references.md, but neither file (nor any references/scripts/assets bundle) is present, so the offloaded detail is missing.

Suggestions

Ship the referenced workflow.md and references.md bundle files (or inline their essential content into SKILL.md) so the well-signaled links actually resolve.

Verify the cross-skill references (../opik-integrations/python.md, ../opik-integrations/typescript.md) resolve from this skill's location, or describe the patterns inline to avoid dangling pointers.

Add a one-line note in references.md linking each known external integration to its repo and Opik-docs URL as promised in the 'Start with the questionnaire' section.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it states principles ('Follow the HOST repo's conventions', 'Consume Opik through its PUBLISHED public API') without explaining what an integration or SDK is, and every section earns its place.	3 / 3
Actionability	Concrete, specific guidance for an instruction-only skill: names exact APIs to use ('@opik.track / track_* wrappers, the low-level client, or REST'), exact modules to avoid ('opik.decorator.*, rest_api'), and a numbered 0–8 workflow with named steps. Absence of code is not penalized per the scoring notes since the guidance is actionable.	3 / 3
Workflow Clarity	A clearly sequenced 0–8 workflow with an explicit validation/feedback checkpoint — step 5 'Verify via the Opik MCP... read the trace/spans back. Loop until correct' — and a dedicated Test step (6), matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	The overview is well-signaled and references are one level deep ('Full playbook in workflow.md', 'check references.md'), but those referenced files do not exist in the bundle — navigation leads nowhere, so the split is incomplete. Not a 3 because the separated content is absent; not a 1 because the SKILL.md overview itself is well organized rather than a monolithic wall.	2 / 3
	Total	11 / 12 Passed

Description

100%

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 names specific actions, shapes, and example targets, with an explicit 'Use ONLY when...' trigger and a clear disambiguation against the sibling opik-integrations skill. All four dimensions land at the top of the scale.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ('Build or update an Opik integration') plus concrete shapes — 'standalone opik-* package (e.g. opik-openclaw, opik-claude-code-plugin)' and 'Opik support contributed into a third-party project (e.g. LiteLLM, Dify)' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	States both what ('Build or update an Opik integration that lives OUTSIDE this repo...') and when with an explicit trigger ('Use ONLY when the user names an external repository or external package as the target'), satisfying the what-AND-when anchor.	3 / 3
Trigger Term Quality	Names natural terms a user would actually say — 'Opik integration', 'external repository', 'external package', 'LiteLLM', 'Dify', 'opik-* package' — giving good coverage rather than jargon.	3 / 3
Distinctiveness Conflict Risk	Defines a clear external-vs-internal niche and explicitly routes conflicts away ('for integrations under sdks/ use the opik-integrations skill instead'), making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 missing, 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: comet-ml/opik
Path: .agents/skills/opik-external-integrations/SKILL.md
Commit: aae4650

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.