[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QFMXSHR3RK2AZ8EY5032HN":3,"skill-same:01M6QFMXSHR3RK2AZ8EY5032HN":147},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":14,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6QFMXSHR3RK2AZ8EY5032HN","pylabrobot",null,"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.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[5,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"read","calibration","verified","usb","make","resources","robotics","only","edit","write","review","integrations","model","Bash","api","Safety","network","operator","offline","2026-11-10 10:12:30",false,"---\nname: pylabrobot\ndescription: 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.\nlicense: MIT\ncompatibility: Verified against PyLabRobot 0.2.1 on Python 3.9+. Bundled planning CLIs require only Python 3.11+ and make no serial, USB, or network connections. Physical devices need model-specific extras, configuration, calibration, and trained operator approval.\nallowed-tools: Read Write Edit Bash\nmetadata:\n  version: '1.3'\n  category: lab-automation\n  maintainer: Kalaris Labs\n  pylabrobot-version: 0.2.1\n  researched: '2026-07-23'\n  tags: lab automation, liquid handling, lab robotics, protocols\n---\n\n# PyLabRobot\n\nUse PyLabRobot's hardware-agnostic frontends, resource tree, trackers, and\ndevice-specific backends to develop laboratory automation. Default to local\nmanifest validation, bookkeeping, and the software-only chatterbox backend.\n\n## Verified snapshot\n\n- PyPI stable: **`PyLabRobot==0.2.1`**, released **2026-03-23**.\n- Upstream requirement: **Python >=3.9**. This skill uses Python 3.11 for its\n  reproducible smoke tests.\n- `\u002Fstable\u002F` documentation identifies itself as 0.2.1. `\u002Fdev\u002F` and repository\n  `main` describe unreleased work and must not be assumed available in 0.2.1.\n- Stable liquid-handler backends include `STARBackend`, `VantageBackend`,\n  `EVOBackend`, `OpentronsOT2Backend`, and the offline\n  `LiquidHandlerChatterboxBackend`.\n- PyLabRobot's GitHub Releases page has no 0.2.x software release entry; use\n  the PyPI history, `v0.2.1` tag, and changelog as release evidence.\n\n## Non-negotiable hardware boundary\n\nNever connect to, initialize, home, move, heat, shake, spin, pump, open\u002Fclose,\nor otherwise command physical equipment automatically. Do not turn a simulation\nplan into a live backend merely by changing an environment variable, config\nvalue, or import.\n\nBefore any separately authorized live run, require a trained human to:\n\n1. Explicitly confirm the exact backend, device identity, firmware, transport,\n   deck, and protocol revision.\n2. Reconcile the physical deck against the resource tree, including carriers,\n   adapters, lids, plates, tip racks, waste, labware orientation, barcodes, and\n   every occupied coordinate.\n3. Verify calibration, teaching, motion envelopes, collision risks, gripper or\n   channel clearances, and all aspiration\u002Fdispense coordinates.\n4. Review source identity and actual fill volume, dead volume, destination\n   capacity, tip type\u002Fcapacity\u002Ffilter compatibility, channel mapping, units,\n   heights, rates, liquid class, blowout\u002Fmixing, and contamination boundaries.\n5. Confirm guards, doors, waste capacity, containment, emergency stop readiness,\n   PPE, biosafety\u002Fchemical controls, and a safe abort\u002Frecovery procedure.\n6. Approve a slow dry run or nonhazardous commissioning run when anything is\n   new or changed.\n\nTracker state is **bookkeeping**, not sensing. It cannot prove that liquid or a\ntip is physically present. The Visualizer renders resource\u002Ftracker events; it\ndoes not model physics. Chatterbox prints planned operations; it does not prove\ncalibration, reachability, collision freedom, liquid behavior, or device state.\n\n## Required intake\n\nDo not guess any of these:\n\n- Exact device model, installed options, firmware, computer\u002FOS, and transport.\n- Stable PyLabRobot version and required extras.\n- Deck\u002Fdeck origin, carriers, adapters, resource definitions, dimensions,\n  coordinates, orientations, and motion clearances.\n- Plate\u002Ftube\u002Freservoir capacities and dead volumes; initial physical volumes.\n- Tip model, filter, fitting, capacity, rack state, channel count, and channel\n  mapping.\n- Transfer units (`uL`, `mm`, `uL\u002Fs`, `s`), heights, rates, mixing, air gaps,\n  blowout, liquid properties, and validated vendor liquid class.\n- Contamination policy, controls, waste handling, operator interventions,\n  acceptance criteria, and recovery procedure.\n\nIf information is missing, produce an assumptions\u002Fblockers list and an offline\ndraft only.\n\n## Reproducible install\n\nFor offline API inspection and chatterbox simulation:\n\n```bash\nuv venv --python 3.11 .venv-pylabrobot\nuv pip install --python .venv-pylabrobot\u002Fbin\u002Fpython \"PyLabRobot==0.2.1\"\n```\n\nOn Windows, use `.venv-pylabrobot\\Scripts\\python.exe`. Do not install hardware\nextras until the user names the device and explicitly approves its transport\ndependencies. Then inspect the matching stable device page before considering a\npin such as `\"PyLabRobot[serial]==0.2.1\"` or `\"PyLabRobot[usb]==0.2.1\"`.\n\n## Offline-first workflow\n\nRun from the repository root. Every bundled CLI uses strict, bounded UTF-8\nJSON\u002FCSV, local non-symlink paths, fixed allowlists, and JSON output. None can\nselect a live backend.\n\n```bash\npython3 skills\u002Fpylabrobot\u002Fscripts\u002Fvalidate_manifest.py \\\n  --input tests\u002Fpylabrobot\u002Ffixtures\u002Fprotocol_manifest.json\n\npython3 skills\u002Fpylabrobot\u002Fscripts\u002Fcheck_deck_geometry.py \\\n  --input tests\u002Fpylabrobot\u002Ffixtures\u002Fprotocol_manifest.json\n\npython3 skills\u002Fpylabrobot\u002Fscripts\u002Fplan_transfers.py \\\n  --manifest tests\u002Fpylabrobot\u002Ffixtures\u002Fprotocol_manifest.json \\\n  --transfers tests\u002Fpylabrobot\u002Ffixtures\u002Ftransfers.csv\n\npython3 skills\u002Fpylabrobot\u002Fscripts\u002Fgenerate_simulation_plan.py \\\n  --manifest tests\u002Fpylabrobot\u002Ffixtures\u002Fprotocol_manifest.json \\\n  --transfers tests\u002Fpylabrobot\u002Ffixtures\u002Ftransfers.csv\n\npython3 skills\u002Fpylabrobot\u002Fscripts\u002Finspect_backends.py \\\n  --expected-version 0.2.1 --strict\n```\n\nThe geometry checker uses conservative static axis-aligned boxes; it is not a\nmotion planner. The transfer planner requires one new tip per row and checks\nsource\u002Fdead\u002Fdestination volumes, tip capacity, wells, channels, heights, rates,\nunits, and allowlists. Review\n`assets\u002Fprotocol-manifest.schema.json` and the synthetic fixtures before making\na project-specific manifest.\n\n## Verified software-only example\n\nThe exact backend below is software-only. Do not substitute a hardware backend.\n\n```python\nfrom pylabrobot.liquid_handling import LiquidHandler\nfrom pylabrobot.liquid_handling.backends import LiquidHandlerChatterboxBackend\nfrom pylabrobot.resources import (\n    Cor_96_wellplate_360ul_Fb,\n    PLT_CAR_L5AC_A00,\n    TIP_CAR_480_A00,\n    hamilton_96_tiprack_1000uL_filter,\n    set_tip_tracking,\n    set_volume_tracking,\n)\nfrom pylabrobot.resources.hamilton import STARLetDeck\n\nset_tip_tracking(True)\nset_volume_tracking(True)\n\ndeck = STARLetDeck()\ntip_carrier = TIP_CAR_480_A00(name=\"tip_carrier\")\ntips = hamilton_96_tiprack_1000uL_filter(name=\"tips\")\ntip_carrier[0] = tips\nplate_carrier = PLT_CAR_L5AC_A00(name=\"plate_carrier\")\nsource = Cor_96_wellplate_360ul_Fb(name=\"source\")\ndestination = Cor_96_wellplate_360ul_Fb(name=\"destination\")\nplate_carrier[0] = source\nplate_carrier[1] = destination\ndeck.assign_child_resource(tip_carrier, rails=3)\ndeck.assign_child_resource(plate_carrier, rails=15)\nsource.get_well(\"A1\").tracker.set_volume(100.0)  # planned state, not sensing\n\nlh = LiquidHandler(backend=LiquidHandlerChatterboxBackend(), deck=deck)\nawait lh.setup()  # safe here only because the backend above is software-only\ntry:\n    await lh.pick_up_tips(tips[\"A1\"])\n    await lh.aspirate(source[\"A1\"], vols=[10.0])\n    await lh.dispense(destination[\"A1\"], vols=[10.0])\n    await lh.return_tips()\nfinally:\n    await lh.stop()\n```\n\n## API rules that prevent stale code\n\n- Current names are `STARBackend`, `VantageBackend`, `EVOBackend`, and\n  `OpentronsOT2Backend`; do not use stale `STAR`, `TecanBackend`,\n  `OpentronsBackend`, or `ChatterboxBackend` imports.\n- Use `LiquidHandlerChatterboxBackend` for generic offline liquid-handler\n  testing. `ChatterBoxBackend` is a separate legacy-named export; do not\n  conflate the two.\n- `Visualizer(resource=...)` is valid, followed by `await vis.setup()` and\n  `await vis.stop()`; it starts localhost HTTP\u002FWebSocket servers and may open a\n  browser.\n- There is no generic `from pylabrobot.liquid_handling import LiquidClass` in\n  0.2.1. Stable liquid classes are vendor-specific, for example\n  `pylabrobot.liquid_handling.liquid_classes.hamilton.HamiltonLiquidClass`.\n- Most frontend methods are async. Backend kwargs and capabilities are\n  vendor\u002Fmodel specific; a shared frontend does not imply identical behavior.\n\n## References\n\n- [Liquid handling](references\u002Fliquid-handling.md) — operations, tips, tracking,\n  liquid classes, units, and validation.\n- [Resources](references\u002Fresources.md) — decks, coordinates, plates, tip racks,\n  collisions, state, and serialization.\n- [Hardware backends](references\u002Fhardware-backends.md) — verified names,\n  support levels, capabilities, and live-run gate.\n- [Analytical equipment](references\u002Fanalytical-equipment.md) — plate readers\n  and scales.\n- [Material handling](references\u002Fmaterial-handling.md) — pumps, heaters,\n  shakers, temperature control, storage, and centrifuges.\n- [Visualization](references\u002Fvisualization.md) — chatterbox, Visualizer,\n  localhost services, and simulation limits.\n\n## Dated upstream sources\n\nChecked **2026-07-23**:\n\n- [PyPI 0.2.1](https:\u002F\u002Fpypi.org\u002Fproject\u002FPyLabRobot\u002F) — released 2026-03-23;\n  Python >=3.9; extras and artifacts.\n- [Stable installation guide](https:\u002F\u002Fdocs.pylabrobot.org\u002Fstable\u002Fuser_guide\u002F_getting-started\u002Finstallation.html)\n  — stable versus source\u002Fdev install and optional transport groups.\n- [Stable API](https:\u002F\u002Fdocs.pylabrobot.org\u002Fstable\u002Fapi\u002Fpylabrobot.html) and\n  [supported machines](https:\u002F\u002Fdocs.pylabrobot.org\u002Fstable\u002Fuser_guide\u002Fmachines.html)\n  — 0.2.1 API and model-specific support labels.\n- [`v0.2.1` source tag](https:\u002F\u002Fgithub.com\u002FPyLabRobot\u002Fpylabrobot\u002Ftree\u002Fv0.2.1)\n  and [changelog](https:\u002F\u002Fgithub.com\u002FPyLabRobot\u002Fpylabrobot\u002Fblob\u002Fmain\u002FCHANGELOG.md)\n  — tag dated 2026-03-23; `Unreleased` is development-only.\n\n## Agent operating procedure\n\n1. **Check the environment.** Confirm the instrument or platform model, API version, credentials and whether a simulator is available.\n2. **Pin down the inputs.** Confirm formats, identifiers and parameters from the data or the user. Ask rather than guess any value that changes the result.\n3. **Run a small version first.** Simulate the protocol or run it with water or dummy labware before using real samples.\n4. **Execute the full task** using the instructions and references above.\n5. **Validate the result.** Verify volumes, deck layout and labware definitions; have a human approve the protocol before execution.\n6. **Report.** State what was run (versions, commands, parameters), what was checked, and what is still uncertain.\n\n| If this happens | Do this |\n|---|---|\n| The protocol fails in simulation | Fix it in simulation; never run an unvalidated protocol on hardware. |\n| A function, flag or endpoint in these instructions is missing in the installed version | Check the installed version's own documentation (`help()`, `--help`, official docs), adapt, and tell the user. Never invent an API. |\n| A required input, identifier or parameter is ambiguous | Ask the user, or state the assumption explicitly before running. |\n\n**Integrity rules**\n\n- Never fabricate results, parameters, identifiers, citations or statistics. If something cannot be run or verified, say so plainly.\n- Never trigger physical actions, orders or charges without explicit user confirmation.\n- Treat version-specific details here as possibly outdated: confirm them against the official documentation for the installed version.\n- Ask before actions that cost money, consume shared GPUs or cloud quota, touch personal or patient data, or cannot be undone.\n\n## Related skills\n\n- `opentrons-integration`: Author, review, migrate, simulate, and troubleshoot official Opentrons Python Protocol API v2 protocols for Flex and OT-2 robots.\n- `fluidsim`: Plan, configure, inspect, restart, and analyze bounded FluidSim computational-fluid-dynamics simulations with explicit numerical-validity a…\n","# PyLabRobot\n\nUse PyLabRobot's hardware-agnostic frontends, resource tree, trackers, and\ndevice-specific backends to develop laboratory automation. Default to local\nmanifest validation, bookkeeping, and the software-only chatterbox backend.\n\n## Verified snapshot\n\n- PyPI stable: **`PyLabRobot==0.2.1`**, released **2026-03-23**.\n- Upstream requirement: **Python >=3.9**. This skill uses Python 3.11 for its\n  reproducible smoke tests.\n- `\u002Fstable\u002F` documentation identifies itself as 0.2.1. `\u002Fdev\u002F` and repository\n  `main` describe unreleased work and must not be assumed available in 0.2.1.\n- Stable liquid-handler backends include `STARBackend`, `VantageBackend`,\n  `EVOBackend`, `OpentronsOT2Backend`, and the offline\n  `LiquidHandlerChatterboxBackend`.\n- PyLabRobot's GitHub Releases page has no 0.2.x software release entry; use\n  the PyPI history, `v0.2.1` tag, and changelog as release evidence.\n\n## Non-negotiable hardware boundary\n\nNever connect to, initialize, home, move, heat, shake, spin, pump, open\u002Fclose,\nor otherwise command physical equipment automatically. Do not turn a simulation\nplan into a live backend merely by changing an environment variable, config\nvalue, or import.\n\nBefore any separately authorized live run, require a trained human to:\n\n1. Explicitly confirm the exact backend, device identity, firmware, transport,\n   deck, and protocol revision.\n2. Reconcile the physical deck against the resource tree, including carriers,\n   adapters, lids, plates, tip racks, waste, labware orientation, barcodes, and\n   every occupied coordinate.\n3. Verify calibration, teaching, motion envelopes, collision risks, gripper or\n   channel clearances, and all aspiration\u002Fdispense coordinates.\n4. Review source identity and actual fill volume, dead volume, destination\n   capacity, tip type\u002Fcapacity\u002Ffilter compatibility, channel mapping, units,\n   heights, rates, liquid class, blowout\u002Fmixing, and contamination boundaries.\n5. Confirm guards, doors, waste capacity, containment, emergency stop readiness,\n   PPE, biosafety\u002Fchemical controls, and a safe abort\u002Frecovery procedure.\n6. Approve a slow dry run or nonhazardous commissioning run when anything is\n   new or changed.\n\nTracker state is **bookkeeping**, not sensing. It cannot prove that liquid or a\ntip is physically present. The Visualizer renders resource\u002Ftracker events; it\ndoes not model physics. Chatterbox prints planned operations; it does not prove\ncalibration, reachability, collision freedom, liquid behavior, or device state.\n\n## Required intake\n\nDo not guess any of these:\n\n- Exact device model, installed options, firmware, computer\u002FOS, and transport.\n- Stable PyLabRobot version and required extras.\n- Deck\u002Fdeck origin, carriers, adapters, resource definitions, dimensions,\n  coordinates, orientations, and motion clearances.\n- Plate\u002Ftube\u002Freservoir capacities and dead volumes; initial physical volumes.\n- Tip model, filter, fitting, capacity, rack state, channel count, and channel\n  mapping.\n- Transfer units (`uL`, `mm`, `uL\u002Fs`, `s`), heights, rates, mixing, air gaps,\n  blowout, liquid properties, and validated vendor liquid class.\n- Contamination policy, controls, waste handling, operator interventions,\n  acceptance criteria, and recovery procedure.\n\nIf information is missing, produce an assumptions\u002Fblockers list and an offline\ndraft only.\n\n## Reproducible install\n\nFor offline API inspection and chatterbox simulation:\n\n```bash\nuv venv --python 3.11 .venv-pylabrobot\nuv pip install --python .venv-pylabrobot\u002Fbin\u002Fpython \"PyLabRobot==0.2.1\"\n```\n\nOn Windows, use `.venv-pylabrobot\\Scripts\\python.exe`. Do not install hardware\nextras until the user names the device and explicitly approves its transport\ndependencies. Then inspect the matching stable device page before considering a\npin such as `\"PyLabRobot[serial]==0.2.1\"` or `\"PyLabRobot[usb]==0.2.1\"`.\n\n## Offline-first workflow\n\nRun from the repository root. Every bundled CLI uses strict, bounded UTF-8\nJSON\u002FCSV, local non-symlink paths, fixed allowlists, and JSON output. None can\nselect a live backend.\n\n```bash\npython3 skills\u002Fpylabrobot\u002Fscripts\u002Fvalidate_manifest.py \\\n  --input tests\u002Fpylabrobot\u002Ffixtures\u002Fprotocol_manifest.json\n\npython3 skills\u002Fpylabrobot\u002Fscripts\u002Fcheck_deck_geometry.py \\\n  --input tests\u002Fpylabrobot\u002Ffixtures\u002Fprotocol_manifest.json\n\npython3 skills\u002Fpylabrobot\u002Fscripts\u002Fplan_transfers.py \\\n  --manifest tests\u002Fpylabrobot\u002Ffixtures\u002Fprotocol_manifest.json \\\n  --transfers tests\u002Fpylabrobot\u002Ffixtures\u002Ftransfers.csv\n\npython3 skills\u002Fpylabrobot\u002Fscripts\u002Fgenerate_simulation_plan.py \\\n  --manifest tests\u002Fpylabrobot\u002Ffixtures\u002Fprotocol_manifest.json \\\n  --transfers tests\u002Fpylabrobot\u002Ffixtures\u002Ftransfers.csv\n\npython3 skills\u002Fpylabrobot\u002Fscripts\u002Finspect_backends.py \\\n  --expected-version 0.2.1 --strict\n```\n\nThe geometry checker uses conservative static axis-aligned boxes; it is not a\nmotion planner. The transfer planner requires one new tip per row and checks\nsource\u002Fdead\u002Fdestination volumes, tip capacity, wells, channels, heights, rates,\nunits, and allowlists. Review\n`assets\u002Fprotocol-manifest.schema.json` and the synthetic fixtures before making\na project-specific manifest.\n\n## Verified software-only example\n\nThe exact backend below is software-only. Do not substitute a hardware backend.\n\n```python\nfrom pylabrobot.liquid_handling import LiquidHandler\nfrom pylabrobot.liquid_handling.backends import LiquidHandlerChatterboxBackend\nfrom pylabrobot.resources import (\n    Cor_96_wellplate_360ul_Fb,\n    PLT_CAR_L5AC_A00,\n    TIP_CAR_480_A00,\n    hamilton_96_tiprack_1000uL_filter,\n    set_tip_tracking,\n    set_volume_tracking,\n)\nfrom pylabrobot.resources.hamilton import STARLetDeck\n\nset_tip_tracking(True)\nset_volume_tracking(True)\n\ndeck = STARLetDeck()\ntip_carrier = TIP_CAR_480_A00(name=\"tip_carrier\")\ntips = hamilton_96_tiprack_1000uL_filter(name=\"tips\")\ntip_carrier[0] = tips\nplate_carrier = PLT_CAR_L5AC_A00(name=\"plate_carrier\")\nsource = Cor_96_wellplate_360ul_Fb(name=\"source\")\ndestination = Cor_96_wellplate_360ul_Fb(name=\"destination\")\nplate_carrier[0] = source\nplate_carrier[1] = destination\ndeck.assign_child_resource(tip_carrier, rails=3)\ndeck.assign_child_resource(plate_carrier, rails=15)\nsource.get_well(\"A1\").tracker.set_volume(100.0)  # planned state, not sensing\n\nlh = LiquidHandler(backend=LiquidHandlerChatterboxBackend(), deck=deck)\nawait lh.setup()  # safe here only because the backend above is software-only\ntry:\n    await lh.pick_up_tips(tips[\"A1\"])\n    await lh.aspirate(source[\"A1\"], vols=[10.0])\n    await lh.dispense(destination[\"A1\"], vols=[10.0])\n    await lh.return_tips()\nfinally:\n    await lh.stop()\n```\n\n## API rules that prevent stale code\n\n- Current names are `STARBackend`, `VantageBackend`, `EVOBackend`, and\n  `OpentronsOT2Backend`; do not use stale `STAR`, `TecanBackend`,\n  `OpentronsBackend`, or `ChatterboxBackend` imports.\n- Use `LiquidHandlerChatterboxBackend` for generic offline liquid-handler\n  testing. `ChatterBoxBackend` is a separate legacy-named export; do not\n  conflate the two.\n- `Visualizer(resource=...)` is valid, followed by `await vis.setup()` and\n  `await vis.stop()`; it starts localhost HTTP\u002FWebSocket servers and may open a\n  browser.\n- There is no generic `from pylabrobot.liquid_handling import LiquidClass` in\n  0.2.1. Stable liquid classes are vendor-specific, for example\n  `pylabrobot.liquid_handling.liquid_classes.hamilton.HamiltonLiquidClass`.\n- Most frontend methods are async. Backend kwargs and capabilities are\n  vendor\u002Fmodel specific; a shared frontend does not imply identical behavior.\n\n## References\n\n- [Liquid handling](references\u002Fliquid-handling.md) — operations, tips, tracking,\n  liquid classes, units, and validation.\n- [Resources](references\u002Fresources.md) — decks, coordinates, plates, tip racks,\n  collisions, state, and serialization.\n- [Hardware backends](references\u002Fhardware-backends.md) — verified names,\n  support levels, capabilities, and live-run gate.\n- [Analytical equipment](references\u002Fanalytical-equipment.md) — plate readers\n  and scales.\n- [Material handling](references\u002Fmaterial-handling.md) — pumps, heaters,\n  shakers, temperature control, storage, and centrifuges.\n- [Visualization](references\u002Fvisualization.md) — chatterbox, Visualizer,\n  localhost services, and simulation limits.\n\n## Dated upstream sources\n\nChecked **2026-07-23**:\n\n- [PyPI 0.2.1](https:\u002F\u002Fpypi.org\u002Fproject\u002FPyLabRobot\u002F) — released 2026-03-23;\n  Python >=3.9; extras and artifacts.\n- [Stable installation guide](https:\u002F\u002Fdocs.pylabrobot.org\u002Fstable\u002Fuser_guide\u002F_getting-started\u002Finstallation.html)\n  — stable versus source\u002Fdev install and optional transport groups.\n- [Stable API](https:\u002F\u002Fdocs.pylabrobot.org\u002Fstable\u002Fapi\u002Fpylabrobot.html) and\n  [supported machines](https:\u002F\u002Fdocs.pylabrobot.org\u002Fstable\u002Fuser_guide\u002Fmachines.html)\n  — 0.2.1 API and model-specific support labels.\n- [`v0.2.1` source tag](https:\u002F\u002Fgithub.com\u002FPyLabRobot\u002Fpylabrobot\u002Ftree\u002Fv0.2.1)\n  and [changelog](https:\u002F\u002Fgithub.com\u002FPyLabRobot\u002Fpylabrobot\u002Fblob\u002Fmain\u002FCHANGELOG.md)\n  — tag dated 2026-03-23; `Unreleased` is development-only.\n\n## Agent operating procedure\n\n1. **Check the environment.** Confirm the instrument or platform model, API version, credentials and whether a simulator is available.\n2. **Pin down the inputs.** Confirm formats, identifiers and parameters from the data or the user. Ask rather than guess any value that changes the result.\n3. **Run a small version first.** Simulate the protocol or run it with water or dummy labware before using real samples.\n4. **Execute the full task** using the instructions and references above.\n5. **Validate the result.** Verify volumes, deck layout and labware definitions; have a human approve the protocol before execution.\n6. **Report.** State what was run (versions, commands, parameters), what was checked, and what is still uncertain.\n\n| If this happens | Do this |\n|---|---|\n| The protocol fails in simulation | Fix it in simulation; never run an unvalidated protocol on hardware. |\n| A function, flag or endpoint in these instructions is missing in the installed version | Check the installed version's own documentation (`help()`, `--help`, official docs), adapt, and tell the user. Never invent an API. |\n| A required input, identifier or parameter is ambiguous | Ask the user, or state the assumption explicitly before running. |\n\n**Integrity rules**\n\n- Never fabricate results, parameters, identifiers, citations or statistics. If something cannot be run or verified, say so plainly.\n- Never trigger physical actions, orders or charges without explicit user confirmation.\n- Treat version-specific details here as possibly outdated: confirm them against the official documentation for the installed version.\n- Ask before actions that cost money, consume shared GPUs or cloud quota, touch personal or patient data, or cannot be undone.\n\n## Related skills\n\n- `opentrons-integration`: Author, review, migrate, simulate, and troubleshoot official Opentrons Python Protocol API v2 protocols for Flex and OT-2 robots.\n- `fluidsim`: Plan, configure, inspect, restart, and analyze bounded FluidSim computational-fluid-dynamics simulations with explicit numerical-validity a…\n",{"name":5,"license":15,"metadata":53,"description":7,"allowed-tools":60,"compatibility":61},{"tags":54,"version":55,"category":56,"maintainer":57,"researched":58,"pylabrobot-version":59},"lab automation, liquid handling, lab robotics, protocols","1.3","lab-automation","Kalaris Labs","2026-07-23","0.2.1","Read Write Edit Bash","Verified against PyLabRobot 0.2.1 on Python 3.9+. Bundled planning CLIs require only Python 3.11+ and make no serial, USB, or network connections. Physical devices need model-specific extras, configuration, calibration, and trained operator approval.","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fkal-pylabrobot","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill pylabrobot",{"tool":77,"command":78},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill pylabrobot",{"tool":80,"command":81},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill pylabrobot","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002FSKILL.md",true,[85,91,97,101,105,109,113,117,123,127,131,135,139,143],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Fprotocol-manifest.schema.json","ASSET","资产文件",7890,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Fassets\u002Fprotocol-manifest.schema.json",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fanalytical-equipment.md","REFERENCE","参考文档",7584,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Freferences\u002Fanalytical-equipment.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fhardware-backends.md",8141,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Freferences\u002Fhardware-backends.md",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fliquid-handling.md",8572,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Freferences\u002Fliquid-handling.md",{"path":106,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fmaterial-handling.md",8298,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Freferences\u002Fmaterial-handling.md",{"path":110,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fresources.md",8695,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Freferences\u002Fresources.md",{"path":114,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fvisualization.md",6648,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Freferences\u002Fvisualization.md",{"path":118,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002F__init__.py","SCRIPT","脚本",72,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Fscripts\u002F__init__.py",{"path":124,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":125,"sourceHtmlUrl":126},"scripts\u002F_common.py",26669,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Fscripts\u002F_common.py",{"path":128,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":129,"sourceHtmlUrl":130},"scripts\u002Fcheck_deck_geometry.py",1301,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Fscripts\u002Fcheck_deck_geometry.py",{"path":132,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":133,"sourceHtmlUrl":134},"scripts\u002Fgenerate_simulation_plan.py",4793,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Fscripts\u002Fgenerate_simulation_plan.py",{"path":136,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":137,"sourceHtmlUrl":138},"scripts\u002Finspect_backends.py",7041,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Fscripts\u002Finspect_backends.py",{"path":140,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":141,"sourceHtmlUrl":142},"scripts\u002Fplan_transfers.py",1556,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Fscripts\u002Fplan_transfers.py",{"path":144,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":145,"sourceHtmlUrl":146},"scripts\u002Fvalidate_manifest.py",1391,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-pylabrobot\u002Fscripts\u002Fvalidate_manifest.py",[148,178,202,226,251,275],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":157,"publishedAt":48},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[154],{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":48},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[185,186,187,188,162,189,190,191,192,193,194,195,38,196,197,198,199,200,201,174],"twitter","x twitter growth","growth","research","content","engineering","plan","web search","competitors","analyze","engine","strategy","use","platform","grow","posting","competitive",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":209,"publishedAt":48},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[208],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[210,38,211,212,213,214,215,216,197,217,218,62,219,220,221,34,222,223,224,225],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","with","tree","progressive disclosure","author",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":232,"publishedAt":48},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[233,234,235,236,237,238,239,240,241,197,242,169,243,244,245,246,247,248,249,250],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":252,"name":253,"nameZh":6,"description":254,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":255,"categories":256,"keywords":258,"publishedAt":48},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[257],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[259,260,261,262,263,212,238,264,265,266,267,268,38,269,168,270,271,272,273,274],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":276,"name":277,"nameZh":6,"description":278,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":279,"categories":280,"keywords":281,"publishedAt":48},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[39,282,283,284,285,286,287,288,289,267,290,291,292,293,294,295,170,296,297,250],"weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]