pylabrobot

Orchestrate multi-device laboratory workflows across Hamilton, Opentrons, and simulation backends.

33.0k|3.2k|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/K-Dense-AI/scientific-agent-skills --skill pylabrobot-k-dense-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pylabrobot
Source: https://github.com/K-Dense-AI/scientific-agent-skills/tree/main/scientific-skills/pylabrobot
Command: npx skills add https://github.com/K-Dense-AI/scientific-agent-skills --skill pylabrobot-k-dense-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PyLabRobot addresses the challenge of coordinating lab automation across multiple hardware platforms by providing a vendor-agnostic API to control devices, manage decks and resources, and run protocols in a consistent way.

Core Features & Use Cases

  • Backend-agnostic control over Hamilton STAR, Opentrons OT-2, and simulation backends through a unified Python API.
  • Deck & Resource Management: create, assign, and serialize decks and resources for reproducible protocols.
  • Simulation & Visualization: validate protocols with a simulation backend and visualize deck state and tip tracking.
  • Multi-device Workflows: orchestrate multi-device workflows combining liquid handling, plate readers, scales, and more.
  • Use Case: develop end-to-end research protocols that can run on hardware or in simulation with one code path.

Quick Start

Create a STAR backend and STARLetDeck, initialize a LiquidHandler, and run a simple tip transfer to validate end-to-end operation.

Frequently Asked Questions about pylabrobot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I control Hamilton and Opentrons devices using a single Python API?

Lab automation across Hamilton STAR and Opentrons OT-2 can be controlled through a vendor-agnostic Python API. PyLabRobot abstracts hardware backends, enabling consistent protocol execution across multiple devices with one code path.

What is vendor-agnostic lab automation and when do I need it?

Vendor-agnostic lab automation provides a unified Python interface to coordinate hardware from different manufacturers. It is needed when orchestrating multi-device workflows across platforms like Hamilton and Opentrons without maintaining separate protocol codebases.

Can I simulate liquid handling protocols before running them on actual hardware?

Liquid handling protocols can be validated using a simulation backend before hardware execution. PyLabRobot includes simulation and visualization features to check deck state and tip tracking, ensuring protocol safety without consuming physical resources.

How do I manage deck layouts and resources for reproducible lab automation protocols?

Deck layouts and resources are managed by creating, assigning, and serializing them within the Python API. PyLabRobot handles deck and resource management to ensure protocols remain reproducible across different runs and hardware backends.

Does PyLabRobot support multi-device workflows combining plate readers and liquid handlers?

Multi-device workflows combining liquid handlers, plate readers, and scales are supported. PyLabRobot orchestrates these laboratory devices across Hamilton, Opentrons, and simulation backends within a single vendor-agnostic workflow.

What are the limitations of vendor-agnostic lab automation in Python?

Vendor-agnostic lab automation abstracts common operations but may not expose highly proprietary features specific to individual hardware. PyLabRobot currently supports Hamilton STAR, Opentrons OT-2, and simulation backends, with safety and validation hooks for cross-device execution.