K-Dense-AI/scientific-agent-skills / skills/opentrons-integration
opentrons-integration
VerifiedAuthors, reviews, migrates, simulates, and troubleshoots 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.9 KB |
| references/api_reference.md | markdown | 12.6 KB |
| references/liquid_handling.md | markdown | 12.9 KB |
| references/migration-api-2-19-to-2-29.md | markdown | 8.5 KB |
| references/modules_and_deck.md | markdown | 11.9 KB |
| references/protocol_authoring.md | markdown | 11.4 KB |
| references/sources.md | markdown | 9.1 KB |
| references/validation_and_operations.md | markdown | 10.2 KB |
| requirements-flex.txt | markdown | 18 B |
| requirements-ot2.txt | markdown | 17 B |
| scripts/absorbance_reader_template.py | script | 2.3 KB |
| scripts/basic_protocol_template.py | script | 1.8 KB |
| scripts/ot2_basic_protocol_template.py | script | 1.7 KB |
| scripts/pcr_setup_template.py | script | 4.7 KB |
| scripts/runtime_parameters_template.py | script | 3.2 KB |
| scripts/serial_dilution_template.py | script | 3.3 KB |
scripts/basic_protocol_template.py
View on GitHub"""Minimal Opentrons Flex protocol template.
Simulate and analyze this protocol before any physical run. Replace the
labware, volumes, liquids, and deck layout with a validated wet-lab method.
"""
from opentrons import protocol_api
metadata = {
"protocolName": "Flex Basic Transfer Template",
"author": "Customize before use",
"description": "Transfer buffer from a reservoir into one plate well.",
}
requirements = {
"robotType": "Flex",
"apiLevel": "2.29",
}
def run(protocol: protocol_api.ProtocolContext) -> None:
"""Load a minimal Flex deck and perform one 100 µL transfer."""
tips = protocol.load_labware(
load_name="opentrons_flex_96_tiprack_200ul",
location="D1",
label="200 µL Tips",
)
reservoir = protocol.load_labware(
load_name="nest_12_reservoir_15ml",
location="D2",
label="Buffer Reservoir",
)
destination_plate = protocol.load_labware(
load_name="nest_96_wellplate_200ul_flat",
location="C2",
label="Destination Plate",
)
protocol.load_trash_bin(location="A3")
pipette = protocol.load_instrument(
instrument_name="flex_1channel_1000",
mount="left",
tip_racks=[tips],
)
buffer = protocol.define_liquid(
name="Buffer",
description="Nonhazardous example buffer",
display_color="#1F77B4",
)
reservoir.load_liquid(
wells=["A1"],
volume=1_000,
liquid=buffer,
)
with protocol.group_steps(
name="Transfer Buffer",
description="Move 100 µL from reservoir A1 to plate A1.",
):
pipette.transfer(
volume=100,
source=reservoir["A1"],
dest=destination_plate["A1"],
new_tip="always",
)
protocol.comment("Transfer complete.")
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |