benchling-integration

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

1.36x

Quality

66%

Does it follow best practices?

Impact

94%

1.36x

Average score across 3 eval scenarios

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/bio/benchling-integration/SKILL.md

Quality

Content

65%

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

The content is highly actionable with executable, copy-paste-ready SDK code, but it is over-long for a SKILL.md, lacks validation checkpoints for its batch/destructive workflows, and references bundle files that do not exist on disk.

Suggestions

Move the per-entity SDK code, OAuth details, and full use-case scripts into the referenced files (references/sdk_reference.md, references/authentication.md, scripts/) and keep SKILL.md as a concise overview with one-level-deep pointers.

Create the missing references/ and scripts/ bundles the body points to, or remove the dangling references, so progressive disclosure is not broken.

Add explicit validation/verification checkpoints to the batch and destructive workflows (bulk import, bulk workflow updates, transfers) — e.g., verify counts or dry-run before applying, and confirm after — to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The ~470-line body packs full inline SDK code for every entity type, OAuth blocks, and four complete use-case scripts that belong in reference files rather than SKILL.md. It mostly respects Claude's intelligence (no basic-concept filler) but is padded with reference-grade inline content, so it could be tightened considerably.	2 / 3
Actionability	Provides many complete, import-bearing, copy-paste-ready Python snippets with real method names and parameters (e.g., DnaSequenceCreate(...), wait_for_task(...), RetryStrategy(max_retries=3), a FASTA import loop). This matches the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Sequences are present (e.g., the numbered event Integration Pattern and CRUD ordering), but there are no validation/verification checkpoints for destructive or batch operations such as bulk entity import, bulk workflow updates, or the inventory audit. Per the rubric, missing validation in batch/destructive workflows caps this at 2.	2 / 3
Progressive Disclosure	The body signals references (authentication.md, sdk_reference.md, api_endpoints.md) and a scripts/ directory, but none of those files or directories actually exist, and the body itself is a monolithic wall of reference-grade inline code that should be split out. Clear section structure keeps it above 1; broken/absent references and inline bulk keep it below 3.	2 / 3
	Total	9 / 12 Passed

Description

67%

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

The description is specific and clearly niched to Benchling's life-sciences R&D platform, naming many concrete capabilities. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the activation condition implied.

Suggestions

Append an explicit 'Use when...' clause naming natural trigger phrases users would say (e.g., "Use when working with Benchling, managing lab inventory, registry sequences, or ELN entries").

Add common-synonym trigger terms ("lab notebook", "Benchling API", "biological sequences") alongside the more technical jargon to broaden natural phrasing coverage.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions across distinct Benchling domains ("Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse"), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	The 'what' is concretely answered, but there is no 'Use when...' clause or explicit trigger guidance, so 'when' is only implied ("for lab data management automation"). Per guidelines, a missing explicit trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Domain terms like "registry", "inventory", "ELN entries" are relevant but specialized, with incomplete coverage of natural phrasings a user would say and no plain synonyms. Not a 3 because natural-term coverage is partial; not a 1 because the jargon is domain-relevant rather than generic.	2 / 3
Distinctiveness Conflict Risk	Names a specific platform ("Benchling R&D platform integration") with a clear life-sciences-R&D niche and domain-specific triggers, making it unlikely to fire for an unrelated skill. Not a 2 because it is a named-platform niche rather than a generic overlapping category.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: wu-yc/LabClaw
Path: skills/bio/benchling-integration/SKILL.md
Commit: df37802

Reviewed: about 2 hours 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.