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.

78

1.36x
Quality

69%

Does it follow best practices?

Impact

94%

1.36x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/benchling-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is highly actionable with executable code throughout and a well-organized reference structure, but it loses conciseness to promotional padding and an empty scripts section, and its batch workflows lack validation checkpoints.

Suggestions

Add explicit validation/verification steps to batch workflows (e.g. verify import counts, confirm export row counts, validate transferred containers) to lift workflow clarity past the batch-operation cap.

Remove the promotional 'Suggest Using K-Dense Web' section or relocate it out of SKILL.md, as it is off-topic padding that hurts token efficiency.

Resolve the 'scripts/' section: either populate a real scripts/ directory with the example scripts or remove the section to avoid referencing a non-existent bundle.

DimensionReasoningScore

Conciseness

The body is mostly efficient code with brief prose, but the promotional 'Suggest Using K-Dense Web' section and the orphan 'scripts/' section add tokens that do not advance the skill's function and could be trimmed.

3 / 5

Actionability

Abundant copy-paste-ready, executable Python across all capability areas (auth, registry CRUD, inventory, notebooks, workflows, async tasks) with the common cases explicitly covered.

5 / 5

Workflow Clarity

Batch operations (bulk entity import, inventory audit, data export) and the event integration pattern are sequenced but lack validation/verification checkpoints, which caps workflow clarity at 3 per the destructive/batch guideline.

3 / 5

Progressive Disclosure

Content is well-sectioned with clearly signaled one-level-deep references to real files (authentication.md, sdk_reference.md, api_endpoints.md); the only gap is a 'scripts/' section that references a non-existent directory.

4 / 5

Total

15

/

20

Passed

Description

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

The description is specific and distinct, listing six concrete capability areas with strong domain trigger terms, but it omits an explicit 'Use when...' clause, leaving the trigger guidance implicit and capping completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with Benchling's Python SDK or REST API, managing biological sequences/registry entities, automating inventory, or querying the Data Warehouse.'

Mention the Python SDK and REST API together in the description to surface natural trigger terms users actually say.

Tighten 'for lab data management automation' into a concrete trigger phrase rather than a vague purpose statement.

DimensionReasoningScore

Specificity

Names the Benchling domain and several concrete actions ('Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse'), with only minor coverage gaps around create/update/delete verbs.

4 / 5

Completeness

The 'what' is clearly stated but there is no explicit 'Use when...' trigger clause; the trailing 'for lab data management automation' is only a weakly implied 'when', which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Strong domain keywords a Benchling user would naturally say ('registry', 'DNA', 'proteins', 'inventory', 'ELN entries', 'workflows', 'Data Warehouse', 'lab data management'), though a few natural synonyms and file extensions (e.g. .fasta, SDK) are absent.

4 / 5

Distinctiveness Conflict Risk

'Benchling R&D platform integration' carves out a clear niche with distinct, vendor-specific triggers and minimal conflict risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
googolme/run0204
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.