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.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

A high-quality, executable lab-automation skill body with a runnable software-only example, concrete CLIs, explicit safety/intake checklists, and a clean one-level reference structure. The main improvements are isolating time-sensitive version/date detail and making the manifest validate-retry loop explicit.

Suggestions

Move version/date specifics (PyLabRobot==0.2.1, release 2026-03-23, checked 2026-07-23) into a dedicated 'Verified snapshot / deprecation' section so they read as dated evidence rather than inlined constraints, improving conciseness.

Add an explicit validate-fix-retry loop for manifest validation (e.g., 'run validate_manifest.py; on failure, fix the manifest and re-run until it passes before geometry/transfer planning') to lift workflow clarity.

Tighten the two long enumerations (the 6-item live-run checklist and 7-item required-intake list) into compact bullet phrases or move their fuller detail into a reference file to reduce token load.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and assumes Claude's competence (no 'what is a liquid handler' padding), but time-sensitive details like PyLabRobot==0.2.1 and dated snapshots are inlined rather than isolated in a deprecated/old-patterns section, fitting the 4 anchor's 'minor instances that could be trimmed'.	4 / 5
Actionability	Provides fully copy-paste-ready runnable code (real imports, real resource names, awaited setup/stop) plus five concrete CLI invocations with exact paths and flags and exact uv install commands, matching the 5 anchor's fully-executable common-case coverage.	5 / 5
Workflow Clarity	The offline-first workflow sequences validate_manifest and check_deck_geometry as explicit checkpoints and supplies intake/safety checklists, but the validate-fix-retry feedback loop is only implied rather than spelled out, fitting the 4 anchor's 'clear sequence with most checkpoints; minor validation gaps'.	4 / 5
Progressive Disclosure	The body is a clear overview that keeps only the runnable example and rules inline while offloading exhaustive detail to six well-signaled one-level-deep reference files (verified real, linking only to external URLs), five scripts, and one schema asset, matching the 5 anchor.	5 / 5
	Total	18 / 20 Passed

Description

92%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, third-person description that clearly states capabilities and explicit usage triggers with a distinctive hardware-safety boundary. The only gap is keyword synonym/extension coverage, which keeps trigger term quality at 4.

Dimension	Reasoning	Score
Specificity	Names the domain plus multiple concrete actions ('Develop and review PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations'), matching the comprehensive-coverage anchor rather than the 4 anchor's 'minor gaps'.	5 / 5
Completeness	Explicitly answers both 'what' (develop/review resources, plans, simulations, integrations) and 'when' ('Use for PyLabRobot protocols or API questions') with concrete trigger phrases, matching the 5 anchor exactly.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('PyLabRobot protocols', 'API questions', 'liquid-handling plans', 'offline simulations') but misses common synonyms and file/extension variations, fitting the 4 anchor's 'a few natural terms missing' rather than 5's comprehensive synonym set.	4 / 5
Distinctiveness Conflict Risk	'PyLabRobot' is a clear niche and the 'keep physical execution behind an explicit operator safety gate' boundary further narrows triggers, giving minimal conflict risk per the 5 anchor.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 9e8b0cb

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.