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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/biology/opentrons-integration/SKILL.md

Quality

Content

68%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.

The content is highly actionable with comprehensive executable examples and a well-organized structure that points to real bundle files. Its weaknesses are verbosity from inlining API reference material that duplicates the separate reference file, and the absence of validation checkpoints in batch workflow patterns.

Suggestions

Trim the inlined per-method API examples (sections 2-7) and defer the bulk to references/api_reference.md, keeping only a concise quick-start and the common protocol patterns in SKILL.md to raise conciseness toward 4-5.

Add explicit validation checkpoints to the batch patterns (e.g., verify tip rack capacity before starting, confirm thermocycler lid is closed before set_block_temperature, check volumes against pipette/well limits) so workflow clarity can exceed the 3 cap.

Surface the references/api_reference.md and scripts/ pointers earlier (e.g., in a Quick start or Resources section near the top) rather than only at the very end, improving navigation.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code without padding about concepts Claude already knows, but at ~560 lines it heavily inlines API reference material that overlaps the separate references/api_reference.md and includes minor redundant code comments, fitting anchor 3.	3 / 5
Actionability	Provides extensive executable, copy-paste-ready code covering the common cases (serial dilution, plate replication, PCR setup, and every module control), matching anchor 5.	5 / 5
Workflow Clarity	Pattern examples like PCR setup are sequenced, but there are no explicit validation/verification checkpoints for batch operations, which per the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Clear section structure with one-level-deep references to the real references/api_reference.md and scripts/ directory signaled at the end, though a large volume of reference-style content remains inlined, fitting anchor 4.	4 / 5
	Total	15 / 20 Passed

Description

82%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.

The description is clear, well-triggered, and well-disambiguated, explicitly covering what and when with a useful boundary pointer to pylabrobot. Its only weakness is that the stated capabilities collapse to a single action ('writing protocols') rather than a comprehensive list of concrete actions.

Suggestions

Expand the capability list with concrete actions such as 'control hardware modules (heater-shaker, thermocycler, magnetic, temperature)', 'manage labware and deck layouts', and 'simulate protocols before robot execution' to lift specificity from 3 to 4-5.

Add the natural term 'lab automation' and pipette/labware synonyms so trigger coverage reaches anchor 5.

Dimension	Reasoning	Score
Specificity	Names the Opentrons domain and a couple of concrete framings ('writing protocols specifically for Opentrons hardware', 'production Opentrons protocols'), but the actions reduce to essentially one activity rather than several distinct concrete actions, matching anchor 3.	3 / 5
Completeness	Explicitly answers both what ('Official Opentrons Protocol API for OT-2 and Flex robots') and when ('Use when writing protocols specifically for Opentrons hardware') with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('Opentrons', 'OT-2', 'Flex robots', 'Protocol API v2', 'protocols') with good coverage, though 'lab automation' and some synonyms are absent, fitting anchor 4.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Opentrons hardware) and explicitly disambiguates from pylabrobot for multi-vendor cases, yielding minimal conflict risk per anchor 5.	5 / 5
	Total	17 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (573 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: synthetic-sciences/openscience
Path: backend/cli/skills/biology/opentrons-integration/SKILL.md
Commit: 3a6c3a9

Reviewed: 1 day 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.