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.
npx skills add K-Dense-AI/scientific-agent-skills --skill pylabrobot --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Verified snapshot
- Non-negotiable hardware boundary
- Required intake
- Reproducible install
- Offline-first workflow
- Verified software-only example
- API rules that prevent stale code
- References
- Dated upstream sources
uv venv --python 3.11 .venv-pylabrobot uv pip install --python .venv-pylabrobot/bin/python "PyLabRobot==0.2.1" python3 skills/pylabrobot/scripts/validate_manifest.py \ python3 skills/pylabrobot/scripts/check_deck_geometry.py \ python3 skills/pylabrobot/scripts/plan_transfers.py \ python3 skills/pylabrobot/scripts/generate_simulation_plan.py \ python3 skills/pylabrobot/scripts/inspect_backends.py \
What does the pylabrobot skill do?
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.
How do I install it?
Run `npx skills add K-Dense-AI/scientific-agent-skills --skill pylabrobot --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From K-Dense-AI/scientific-agent-skills, a repository with 32,619 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.