CtrlK
BlogDocsLog inGet started
Tessl Logo

pylabrobot

Vendor-agnostic lab automation framework. Use when controlling multiple equipment types (Hamilton, Tecan, Opentrons, plate readers, pumps) or needing unified programming across different vendors. Best for complex workflows, multi-vendor setups, simulation. For Opentrons-only protocols with official API, opentrons-integration may be simpler.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/biology/pylabrobot/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured with strong progressive disclosure and actionable code examples, but weakened by padded capability restatements and a lack of validation checkpoints in the physical/batch pipetting workflows, which caps workflow clarity.

Suggestions

Trim the 'When to Use' and per-capability bullet lists that restate the description or explain self-evident operations like aspirate/dispense, keeping only guidance Claude would not already know.

Add explicit validation/verification checkpoints to the workflows (e.g., verify deck assignment succeeded, confirm tip pickup, check volumes before dispensing) so the batch pipetting flow has a validate-fix-retry loop.

Close actionability gaps by including the missing imports (TIP_CAR_480_A00, Cos_96_DW_1mL) and defining tip_rack in the Quick Start example so snippets are copy-paste runnable.

DimensionReasoningScore

Conciseness

Mostly efficient, but the 10-bullet 'When to Use' list and the per-capability bullet lists restate the description and explain operations (e.g., 'Aspirate, dispense, transfer liquids between wells') that Claude already knows, adding padding that could be trimmed.

3 / 5

Actionability

Provides concrete, mostly executable Python in Quick Start and two Common Workflows covering setup and operations, with minor gaps such as undefined tip_rack and omitted labware imports.

4 / 5

Workflow Clarity

Operations appear as code sequences rather than a sequenced workflow, and the batch/physical pipetting workflows include no validation or verify-step checkpoints; per the rubric cap, destructive/batch workflows without validation cannot exceed 3.

3 / 5

Progressive Disclosure

A clear overview routes each of six capability areas to a verified, one-level-deep references/*.md file, keeping the bulk of detail out of SKILL.md while keeping navigation explicit and shallow.

5 / 5

Total

15

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill does and when to use it, with good natural trigger terms and an explicit disambiguation pointer to a competing skill. It sits just below top marks on specificity and completeness only because the capability enumeration could be slightly fuller.

DimensionReasoningScore

Specificity

Names the lab-automation domain plus several concrete capabilities (controlling Hamilton, Tecan, Opentrons, plate readers, pumps; unified programming; simulation), stopping just short of the comprehensive multi-action enumeration of a 5.

4 / 5

Completeness

Explicitly answers both 'what' ('Vendor-agnostic lab automation framework... unified programming across different vendors') and 'when' ('Use when controlling multiple equipment types... Best for complex workflows, multi-vendor setups, simulation'), with the 'when' concrete but not maximally specific.

4 / 5

Trigger Term Quality

Includes natural vendor and equipment terms users would actually say (Hamilton, Tecan, Opentrons, plate readers, pumps, multi-vendor, simulation), with only minor synonyms like 'liquid handler' or 'robot' missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (multi-vendor lab automation) and actively reduces conflict risk by redirecting Opentrons-only cases to opentrons-integration, minimizing mis-triggering.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
synthetic-sciences/openscience
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.