CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pylabrobot

Develops and reviews PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Supports PyLabRobot protocols and API questions; keep physical execution behind an explicit operator safety gate.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

Excellent skill body: executable commands and code dominate, validation and safety gates are built into the workflow, and detailed material is properly pushed to well-signaled one-level-deep references. The only improvements are tightening a few verbose passages in the snapshot/verification sections and making the workflow order explicit.

DimensionReasoningScore

Conciseness

The body is dense and high-signal, adding version-specific facts Claude cannot know (0.2.2 backend names, changelog drift, API rules) rather than generic explanations. Minor trims are possible — e.g. verified-snapshot minutiae like 'GitHub has no v0.2.2 tag and its changelog has no 0.2.2 section' — so it fits 'efficient; minor instances of over-explanation', not the fully lean 5 anchor.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: uv install commands, five concrete CLI invocations with arguments, a complete runnable software-only Python example with asyncio adaptation notes, and exact import-name rules ('do not use stale STAR, TecanBackend... imports'). This matches the fully-executable 5 anchor.

5 / 5

Workflow Clarity

A clear sectioned sequence (required intake → reproducible install → validated offline CLIs → software-only example) with explicit checkpoints (validate_manifest.py, check_deck_geometry.py, --strict), a missing-information fallback ('produce an assumptions/blockers list and an offline draft only'), and error-recovery guidance ('Do not blindly retry'). It falls short of 5 because the sequence is implied by section order rather than explicitly enumerated as ordered steps.

4 / 5

Progressive Disclosure

The SKILL.md overview is lean and points to six clearly annotated, one-level-deep reference files (verified to exist, with no nested references inside them), plus supporting scripts and a schema asset. Content is appropriately split with easy navigation, matching the 5 anchor.

5 / 5

Total

18

/

20

Passed

Description

75%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 specific, distinctive description with strong third-person action verbs and comprehensive capability coverage. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the usage condition only weakly implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with PyLabRobot, designing liquid-handling protocols, or simulating lab automation offline.'

Include device-ecosystem keywords users would naturally say (Hamilton STAR, Opentrons, Tecan, deck layout, plate mapping) to broaden natural trigger coverage.

Mention the supported vendor backends or device families briefly so users naming a specific instrument can find the skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('Develops and reviews PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Supports PyLabRobot protocols and API questions') covering the skill's full scope, matching the comprehensive-coverage anchor. It is not a 4 because no meaningful capability of the skill is left unmentioned.

5 / 5

Completeness

The 'what' is clearly answered, but there is no 'Use when...' clause or equivalent explicit trigger guidance; 'Supports PyLabRobot protocols and API questions' states capability rather than a usage condition, so 'when' is only weakly implied. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3, so 4 is excluded.

3 / 5

Trigger Term Quality

Good natural-keyword coverage ('PyLabRobot', 'lab-automation', 'liquid-handling', 'protocols', 'API', 'simulations') that users would actually say. It falls short of 5 because common synonyms users might use — device/brand names like Hamilton, Opentrons, Tecan, or terms like 'deck' and 'plate' — are absent.

4 / 5

Distinctiveness Conflict Risk

'PyLabRobot' is a highly specific, niche library name paired with a distinct domain (lab automation, liquid handling), giving a clear niche with minimal conflict risk against other skills. No neighboring anchor fits better.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

K-Dense-AI/scientific-agent-skills

Path

skills/pylabrobot/SKILL.md

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.