Agent skill · software engineering · k-dense-ai
opentrons-integration
Author, review, migrate, simulate, and troubleshoot official Opentrons Python Protocol API v2 protocols for Flex and OT-2 robots. Use for robot-specific liquid handling, deck and labware setup, pipettes, modules, runtime parameters, liquid classes, and Opentrons App analysis. Use pylabrobot instead when one workflow must support multiple robot vendors.
Why this skill is useful
Adds executable scripts and detailed protocols for Opentrons robot integration that are not covered in public documentation.
What it needs
Requires python, uv installed locally. About 7k tokens when loaded. Last updated 2026-08-03. 32,849 stars on the source repository.
What this skill does
Opentrons Integration Overview Create production-minded Python Protocol API v2 protocols for Opentrons Flex and OT-2. This skill covers protocol structure, hardware and deck configuration, liquid handling, runtime customization, module control, simulation, and safe deployment. The verified baseline as of 2026-07-23 is: opentrons==9.1.1 for reproducible Flex simulation. opentrons==9.0.0 for local OT-2 API 2.28 compatibility simulation. Flex supports API levels 2.15 through 2.29 on current software. OT-2 supports API levels 2.0 through 2.28 on current software. API 2.29 is Flex-only at this baseline. Do not put 2.29 in an OT-2 protocol. Read references/sources.md for the upstream documentation used for this snapshot. Recheck the official versioning page before targeting newer robot software. Safety Boundary Opentrons protocols control physical equipment. Never treat successful Python syntax or local simulation as permission to run on a robot. Before live execution: 1. Simulate locally with the same pinned opentrons version used for authoring. 2. Import the protocol into the correct Opentrons App and require successful analysis. 3. Verify robot model, software, pipettes, mounts, modules, adapters, labware definitions, deck fixtures, tip count, source volumes, dead volumes, and destination capacity. 4. Review the run preview and deck map with the operator. 5. Perform a slow dry run with nonhazardous liquid when geometry, custom labware, partial tip pickup, or gripper moves are new. 6. Keep the emergency stop accessible and follow site-specific biosafety, chemical-safety, and contamination-control procedures. Simulation cannot verify physical calibration, liquid properties, meniscus behavior, labware manufacturing tolerances, cap or seal removal, tubing, or all possible collisions. Choose the Right Interface Use this skill for Python files imported into the Opentrons App and run through the Protocol API. Use Protocol Designer for supported no-code workflows. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills k-dense-ai/opentrons-integration