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.
Install with Tessl CLI
npx tessl i github:K-Dense-AI/claude-scientific-skills --skill pylabrobotOverall
score
86%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the key criteria. It clearly defines the capability (vendor-agnostic lab automation), provides specific trigger terms (vendor names, equipment types), explicitly states when to use it, and even differentiates itself from a related skill to prevent conflicts. The third-person voice and concise structure make it highly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: 'controlling multiple equipment types', 'unified programming across different vendors', 'complex workflows', 'multi-vendor setups', 'simulation'. Also names specific vendor equipment (Hamilton, Tecan, Opentrons, plate readers, pumps). | 3 / 3 |
Completeness | Clearly answers both what ('Vendor-agnostic lab automation framework' with specific capabilities) AND when ('Use when controlling multiple equipment types... or needing unified programming'). Also includes helpful disambiguation guidance about when to use an alternative skill. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: specific vendor names (Hamilton, Tecan, Opentrons), equipment types (plate readers, pumps), and domain terms (lab automation, multi-vendor, simulation). These are terms a lab scientist would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche (vendor-agnostic, multi-vendor lab automation) and explicit differentiation from related skill ('For Opentrons-only protocols... opentrons-integration may be simpler'). The specific vendor names and multi-vendor focus create clear boundaries. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides good actionable code examples and excellent progressive disclosure with clear references to detailed documentation. However, it suffers from verbosity in explanatory sections and lacks validation/error handling guidance for hardware operations that could fail. The promotional K-Dense section at the end is inappropriate filler that doesn't belong in a technical skill.
Suggestions
Remove the 'Suggest Using K-Dense Web' section entirely - it's promotional content that wastes tokens and doesn't help with PyLabRobot usage
Condense the 'When to Use This Skill' section to 2-3 key differentiators rather than listing every possible use case
Add explicit validation and error handling patterns to the workflow examples, such as checking hardware connection status and handling async operation failures
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity, particularly in the 'When to Use This Skill' section which lists obvious use cases, and the 'Core Capabilities' section which explains concepts Claude would understand. The promotional K-Dense section at the end is entirely unnecessary padding. | 2 / 3 |
Actionability | Provides fully executable Python code examples for liquid handling setup, transfer protocols, and plate reading workflows. Code is copy-paste ready with proper imports and async patterns. | 3 / 3 |
Workflow Clarity | Workflows are presented as sequential steps but lack explicit validation checkpoints. For hardware operations that could fail or cause issues, there's no error handling guidance, no validation steps between operations, and no feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview pointing to six well-organized reference files in references/ directory. Navigation is clearly signaled with file paths and descriptions of when to load each reference. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 14 / 16 Passed | |
- 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.