CtrlK
BlogDocsLog inGet started
Tessl Logo

python-sdk

Python SDK patterns for Opik. Use when working in sdks/python, on SDK APIs, integrations, or message processing.

59

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/python-sdk/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 dense, well-organized reference with good executable code and conciseness, undermined by a batch system that lacks verification steps and by three referenced files that do not exist in the bundle.

Suggestions

Create the missing referenced files (testing.md, error-handling.md, good-code.md) under references/ so the one-level-deep navigation actually resolves.

Add a verification/feedback step for the batching/flush workflow, e.g. how to confirm traces were delivered or detect a failed flush, to lift workflow clarity above the batch-operation cap.

Fill in the schematic snippets (e.g. give a concrete batch_create_items example instead of '...') to close the actionability gaps.

DimensionReasoningScore

Conciseness

The body is lean and dense with terse diagrams, code blocks, and bullets that assume Claude's competence, with only minor over-explanatory lines like 'Reduces HTTP overhead significantly', fitting anchor 4 (efficient with minor trim opportunities) just below the fully lean anchor 5.

4 / 5

Actionability

Concrete copy-pasteable code covers the common cases (flush, method patching, callbacks, decorator, CRUD/search/batch), but schematic snippets like the architecture diagram and 'client.batch_create_items(...)' leave minor gaps, fitting anchor 4 (mostly executable with minor gaps) below the fully-executable anchor 5.

4 / 5

Workflow Clarity

Sequencing aids like the integration-pattern decision table and flush-before-exit steps are present, but the batching system is a batch operation with no validation/verification or feedback loop (e.g. how to confirm a flush succeeded), so the batch-operation cap at 3 applies rather than anchor 4.

3 / 5

Progressive Disclosure

The body is well-sectioned and the 'Reference Files' section clearly signals one-level-deep references, but the referenced files (testing.md, error-handling.md, good-code.md) do not exist and no bundle directory is present, so the promised content split is unrealized — worse than the 'references present but not clearly signaled' anchor 3.

2 / 5

Total

13

/

20

Passed

Description

77%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, distinctive description with explicit what/when trigger guidance that fits its niche well. Its only weakness is specificity: it names topical areas rather than concrete actions.

Suggestions

Replace topical area names with concrete verbs, e.g. 'Instrument tracing, build integrations, and process Opik messages in the Python SDK.'

Add 1-2 concrete actions (e.g. 'add traces/spans', 'wire up library integrations') to lift specificity from a topic-list to an action-list.

DimensionReasoningScore

Specificity

The description names the domain ('Python SDK patterns for Opik') and sub-areas ('SDK APIs, integrations, or message processing') but lists no concrete actions or verbs, fitting the 'names the domain but actions are minimal or generic' anchor rather than the anchor 3 which requires concrete actions.

2 / 5

Completeness

It clearly states what ('Python SDK patterns for Opik') and explicitly when ('Use when working in sdks/python, on SDK APIs, integrations, or message processing') with concrete trigger phrases, matching the anchor 5 'clearly and explicitly answers both what AND when'.

5 / 5

Trigger Term Quality

Phrases like 'working in sdks/python, on SDK APIs, integrations, or message processing' give good keyword coverage matching a developer's natural trigger language, with only a few common synonyms missing, fitting anchor 4 above the 'some relevant keywords' anchor 3.

4 / 5

Distinctiveness Conflict Risk

Tied to a specific SDK and repo path ('Opik', 'sdks/python'), it carves a clear niche with distinct triggers and minimal overlap risk, matching anchor 5.

5 / 5

Total

16

/

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: 3 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.