benchling-integration

Integrate with the Benchling R&D platform when you need to programmatically manage registry entities, inventory, ELN entries, workflows, events, or data warehouse analytics via API/SDK.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/benchling-integration/SKILL.md

Quality

Content

75%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 content-rich skill with excellent actionable, executable SDK examples and well-structured progressive disclosure into real reference files. Its main weakness is conciseness: duplicated generic section blocks and process boilerplate inflate the body without adding Claude-unknown information.

Suggestions

Remove the duplicate generic section block (the first 'When to Use / Key Features / Dependencies / Example Usage / Implementation Details') and keep only the substantive Benchling-specific versions to cut significant boilerplate.

Tighten or delete generic process prose ('Execution model: validate the request…', 'Output discipline: keep results reproducible…', 'Parameters to clarify first…') that restates what Claude already does, or replace it with concise Benchling-specific guidance.

Make the workflow validation checkpoint concrete for batch/destructive operations (e.g., dry-run a registry create or verify an entity exists before a transfer) instead of the abstract 'run a final validation pass', and replace the empty 'Quick Validation' block with a real verification step.

Dimension	Reasoning	Score
Conciseness	The body duplicates whole section groups (two 'When to Use', 'Key Features', 'Dependencies', 'Example Usage', 'Implementation Details' blocks) and carries generic process boilerplate ('Execution model: validate the request…', 'Output discipline…') that could be trimmed, though the substantive half avoids explaining concepts Claude already knows.	3 / 5
Actionability	Provides numerous concrete, copy-paste-ready SDK code examples spanning authentication, registry creation/updates, pagination, inventory transfers, async task polling, and retry configuration, covering the common cases comprehensively.	5 / 5
Workflow Clarity	A 'Recommended Workflow' gives a sequenced 4-step path with an explicit validation pass, and 'Validation and Safety Rules' plus 'Failure Handling' add checkpoints, but the validation is described abstractly ('run a final validation pass') rather than as a concrete executable check for batch/destructive registry operations.	4 / 5
Progressive Disclosure	SKILL.md acts as an overview and clearly signals one-level-deep reference files (references/authentication.md, sdk_reference.md, api_endpoints.md) that genuinely exist and hold the bulk API detail; the main gap is that SKILL.md still inlines a substantial amount of code rather than keeping purely to overview.	4 / 5
	Total	16 / 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, specific description that names the Benchling R&D platform and several concrete capability domains with an explicit 'when to use' clause. Minor gains are available by making per-area actions more concrete and adding natural trigger synonyms.

Suggestions

Replace the generic verb 'manage' with concrete per-area actions (e.g., 'create, update, archive, and search registry entities; move and transfer inventory') to lift specificity toward 5.

Add a few natural trigger synonyms/phrases users would say (e.g., 'Benchling API', 'Benchling SDK', 'register sequences', 'lab inventory automation') to broaden trigger-term coverage.

Make the 'when' clause more situational and explicit (e.g., 'Use when the user asks to automate Benchling registry, inventory, ELN, workflow, or data warehouse tasks from code').

Dimension	Reasoning	Score
Specificity	Enumerates several concrete capability domains (registry entities, inventory, ELN entries, workflows, events, data warehouse analytics) plus the API/SDK mechanism, but 'manage' is a generic verb rather than per-area concrete actions, so it sits just below the comprehensive 5 anchor.	4 / 5
Completeness	Clearly states both the 'what' (integrate with and programmatically manage Benchling R&D platform resources) and the 'when' (when you need to programmatically manage them), but the 'when' trigger could be more explicit with concrete situational cues.	4 / 5
Trigger Term Quality	Contains natural terms users would say (Benchling, API, SDK, registry, inventory, ELN) with an explicit 'when you need to' trigger clause, though it lacks some common synonyms and extension phrasing that would reach a 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clearly named, specific niche (the Benchling R&D platform) with distinct API/SDK triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: aipoch/medical-research-skills
Path: scientific-skills/Other/benchling-integration/SKILL.md
Commit: 63c61d3

Reviewed: 3 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.