CtrlK
BlogDocsLog inGet started
Tessl Logo

opentrons-integration

Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable with thorough executable code, but it functions as a monolithic inline API reference rather than a lean overview, and the referenced bundle files it points to are absent. Batch-operation workflows also lack explicit validation feedback loops.

Suggestions

Move the bulk of the per-method API reference (sections 2–8) into references/api_reference.md and keep SKILL.md as a concise overview with one-level-deep links, then actually create that file so the reference resolves.

Add an explicit validation workflow for batch liquid-handling protocols, e.g. 'simulate with opentrons_simulate → fix errors → re-simulate → only then run on robot', embedded in the Common Protocol Patterns rather than only as a best-practice bullet.

Create the referenced scripts/ directory with the example protocol templates mentioned in the Resources section, or remove the dangling reference.

DimensionReasoningScore

Conciseness

The body avoids explaining basic concepts Claude already knows, but it is a ~560-line inline API reference that largely duplicates what the referenced 'references/api_reference.md' is meant to hold; it could be tightened by moving bulk reference material out of SKILL.md.

2 / 3

Actionability

Provides extensive copy-paste-ready, executable code with real API names, parameter comments, and concrete examples (pipette loading, liquid handling, module control, serial dilution, PCR setup).

3 / 3

Workflow Clarity

Common Protocol Patterns are sequenced, but batch/destructive liquid-handling workflows lack an explicit simulate→validate→fix→retry checkpoint; 'Simulate first' appears only as a best-practice bullet, capping clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

References to 'references/api_reference.md' and 'scripts/' are signaled, but those directories do not exist in the bundle, and the detailed API reference that should live in those files is inlined in SKILL.md rather than split out.

2 / 3

Total

9

/

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.

The description is third-person, concise, and explicitly states both what the skill does and when to use it, with a clear disambiguating redirect to a competing skill. It is a strong, low-conflict trigger description.

DimensionReasoningScore

Specificity

Names concrete capabilities — 'Opentrons Protocol API for OT-2 and Flex robots', 'Protocol API v2 features', 'production Opentrons protocols', 'official API compatibility' — listing multiple specific actions rather than vague language.

3 / 3

Completeness

Explicitly answers what it does ('Official Opentrons Protocol API...') and when to use it via a clear 'Use when writing protocols specifically for Opentrons hardware' clause, plus a redirect ('For multi-vendor automation... use pylabrobot').

3 / 3

Trigger Term Quality

Uses natural terms a user would say when needing this skill — 'Opentrons', 'OT-2 and Flex robots', 'writing protocols', 'Protocol API v2', 'production Opentrons protocols' — with good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (Opentrons hardware only) and explicitly disambiguates from a sibling skill ('For multi-vendor automation or broader equipment control use pylabrobot'), making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (573 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
wu-yc/LabClaw
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.