pylabrobot-vendor-agnostic

Develop and execute liquid handling protocols across Hamilton STAR, Tecan Freedom EVO, and Opentrons OT-2.

6|2|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/pradyumnasagar/open-research-skills --skill pylabrobot-vendor-agnostic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pylabrobot-vendor-agnostic
Source: https://github.com/pradyumnasagar/open-research-skills/tree/main/skills/lab-automation/pylabrobot-vendor-agnostic
Command: npx skills add https://github.com/pradyumnasagar/open-research-skills --skill pylabrobot-vendor-agnostic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pylabrobot[hamilton], pylabrobot[opentrons], pylabrobot[tecan], and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the challenge of writing liquid handling protocols that are compatible with multiple robots from different vendors, reducing the need for vendor-specific scripting and allowing for flexible automation across different laboratory settings.

Core Features & Use Cases

  • Vendor-Agnostic Protocols: Develop and execute protocols on Hamilton STAR, Tecan Freedom EVO, Opentrons OT-2, and simulated backends without code changes.
  • Async-first API: Clean, non-blocking operations that allow for complex workflows and integration with other systems.
  • Use Case: For a core lab with multiple robots, this Skill enables a shared protocol development approach, simplifying collaboration and reducing dependency on specific hardware.

Quick Start

Use the 'pylabrobot-vendor-agnostic' skill to create a serial dilution protocol that can be run on any of the supported robots.

Frequently Asked Questions about pylabrobot-vendor-agnostic

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

FAQPage Schema
How do I write liquid handling protocols that work on Hamilton, Tecan, and Opentrons robots?

Vendor-agnostic liquid handling protocols allow you to write a single script that executes across Hamilton STAR, Tecan Freedom EVO, and Opentrons OT-2 robots without code changes. Using an async-first API, the same protocol runs on multiple hardware backends and simulators.

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

Vendor-agnostic lab automation is the ability to develop and execute wet-lab protocols independently of specific hardware. You need it when a core lab has multiple robots from different vendors and wants a shared protocol development approach to simplify collaboration.

Does pylabrobot support running serial dilution protocols on simulated backends?

Yes, pylabrobot supports executing serial dilution protocols on simulated backends. The universal liquid handling protocols are compatible with various hardware drivers and simulators, allowing you to test workflows without physical robots.

Do I need an async-first API design for multi-robot automation?

Yes, an async-first API design is required for multi-robot automation. Clean, non-blocking operations allow for complex wet-lab workflows and integration with other systems while maintaining compatibility with various hardware drivers.

What are the limitations of universal liquid handling protocols?

Universal liquid handling protocols are limited by their dependency on specific hardware drivers for Hamilton, Tecan, and Opentrons. Protocol portability requires that the target robot's capabilities match the protocol's requirements, and complex vendor-specific features may not translate universally.