CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

56

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/biology/benchling-integration/SKILL.md
SKILL.md
Quality
Evals
Security

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 extensive executable SDK examples and well-organized reference files, but it is verbose and lacks validation/feedback checkpoints for its batch and destructive operations. Progressive disclosure is diluted because most detail lives inline in SKILL.md rather than being delegated to the available references.

Suggestions

Add explicit validate→fix→retry checkpoints to batch examples (bulk import, bulk workflow automation), e.g. confirming created entities or re-fetching failed tasks before proceeding.

Tighten SKILL.md into a lean overview and move the per-capability deep dives into the existing references (sdk_reference.md, api_endpoints.md), reducing the inline ~470 lines.

Trim redundant 'Key Points'/'Key Operations' lists that restate the preceding code, and replace Data Warehouse prose with a concrete connection/query example.

DimensionReasoningScore

Conciseness

The body is largely efficient executable code, but it carries redundant paraphrasing ('Key Points', 'Key Operations' lists restate the code) and prose that explains the obvious (Data Warehouse 'provides SQL access… for analytics and reporting'). Not a 1 because it avoids explaining concepts Claude already knows; not a 3 because of notable repetition and padded lists.

2 / 3

Actionability

Most sections give copy-paste-ready, executable code with real imports and parameters (e.g. DnaSequenceCreate creation, wait_for_task). The few prose-only spots (Data Warehouse, Events) do not pull it below the fully-executable anchor; not a 2 because the dominant guidance is real code rather than pseudocode.

3 / 3

Workflow Clarity

Capabilities are organized into sequenced sections, but batch/destructive operations (bulk entity import, bulk workflow automation) lack explicit validation or error-recovery checkpoints, capping the score per the feedback-loops guideline. Not a 1 because steps are present and ordered; not a 3 because there are no validate→fix→retry checkpoints for these risky operations.

2 / 3

Progressive Disclosure

Real one-level-deep references exist (authentication.md, sdk_reference.md, api_endpoints.md) and are signaled in the Resources section, but SKILL.md itself is a ~470-line monolith covering all seven capabilities inline rather than staying a lean overview. Not a 1 because references are genuine and not nested 2+ levels; not a 3 because the overview is not lean — too much detail lives inline instead of being delegated.

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 distinctive for the Benchling platform, naming many concrete capabilities. Its main weakness is the absence of an explicit 'Use when…' trigger clause, which caps completeness and weakens trigger-term naturalness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to automate Benchling registry, inventory, ELN notebooks, workflows, or Data Warehouse queries.'

Soften jargon in the description (e.g. 'ELN entries') toward terms users actually say, like 'lab notebook entries'.

Keep the action list but lead with the strongest natural triggers (Benchling API, DNA/protein registry, sample inventory) to improve fireability.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse' — matching the anchor for enumerating several specific actions. Not a 2 because it goes beyond naming a domain plus a few actions.

3 / 3

Completeness

Clearly states what the skill does, but the only 'when' guidance is the bare phrase 'for lab data management automation' with no explicit trigger clause. Per the judging guidelines, a missing 'Use when…' clause caps completeness at 2; not a 3 because triggers are not explicit, and not a 1 because the 'what' is clearly stated.

2 / 3

Trigger Term Quality

Contains relevant keywords (Benchling, registry, inventory, workflows, Data Warehouse) but leans on jargon (ELN entries, Data Warehouse) and omits natural user phrasings a person would actually say. Not a 3 because there is no 'Use when…' phrasing or common-term variations; not a 1 because several meaningful domain terms are present.

2 / 3

Distinctiveness Conflict Risk

The Benchling-specific product framing ('Benchling R&D platform integration', 'build Benchling Apps', 'query Data Warehouse') carves a clear niche unlikely to fire for other skills. Not a 2 because it is not merely a generic 'works with data' description.

3 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
synthetic-sciences/openscience
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.