Agent skill · software engineering · k-dense-ai
pylabrobot
Develop and review PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Use for PyLabRobot protocols or API questions; keep physical execution behind an explicit operator safety gate.
Why this skill is useful
Adds executable scripts for liquid-handling automation and integration patterns specific to PyLabRobot that aren't widely available.
What it needs
Requires python installed locally. About 5k tokens when loaded. Last updated 2026-08-03. 32,849 stars on the source repository.
What this skill does
PyLabRobot Use PyLabRobot's hardware-agnostic frontends, resource tree, trackers, and device-specific backends to develop laboratory automation. Default to local manifest validation, bookkeeping, and the software-only chatterbox backend. Verified snapshot PyPI stable: PyLabRobot==0.2.1, released 2026-03-23. Upstream requirement: Python >=3.9. This skill uses Python 3.11 for its reproducible smoke tests. /stable/ documentation identifies itself as 0.2.1. /dev/ and repository main describe unreleased work and must not be assumed available in 0.2.1. Stable liquid-handler backends include STARBackend, VantageBackend, EVOBackend, OpentronsOT2Backend, and the offline LiquidHandlerChatterboxBackend. PyLabRobot's GitHub Releases page has no 0.2.x software release entry; use the PyPI history, v0.2.1 tag, and changelog as release evidence. Non-negotiable hardware boundary Never connect to, initialize, home, move, heat, shake, spin, pump, open/close, or otherwise command physical equipment automatically. Do not turn a simulation plan into a live backend merely by changing an environment variable, config value, or import. Before any separately authorized live run, require a trained human to: 1. Explicitly confirm the exact backend, device identity, firmware, transport, deck, and protocol revision. 2. Reconcile the physical deck against the resource tree, including carriers, adapters, lids, plates, tip racks, waste, labware orientation, barcodes, and every occupied coordinate. 3. Verify calibration, teaching, motion envelopes, collision risks, gripper or channel clearances, and all aspiration/dispense coordinates. 4. Review source identity and actual fill volume, dead volume, destination capacity, tip type/capacity/filter compatibility, channel mapping, units, heights, rates, liquid class, blowout/mixing, and contamination boundaries. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills k-dense-ai/pylabrobot