CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

50%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 contains a genuinely useful, executable benchling-sdk reference (auth, registry CRUD, pagination, inventory, async tasks, retry), but it is wrapped in a duplicated set of auto-generated template sections that pad the file with boilerplate. Workflow guidance and validation are generic no-ops, and the three bundled reference files are only weakly signaled rather than integrated.

Suggestions

Delete the first (auto-generated) set of "When to Use", "Key Features", "Dependencies", "Example Usage", and "Implementation Details" sections and the generic "Output Contract"/"Quick Validation" filler — they duplicate sections 1–5 and state nothing specific.

Replace the hedged "Additional reference docs may exist in references/..." with explicit per-topic links, e.g., in the Authentication section: "See [references/authentication.md](references/authentication.md)" and in Registry/Inventory: "See [references/sdk_reference.md](references/sdk_reference.md) and [references/api_endpoints.md](references/api_endpoints.md)".

Add a concrete validation checkpoint to the workflow (e.g., verify auth by listing one registry entity before bulk operations, and confirm task completion via wait_for_task before reporting success) instead of the no-op "No local script validation step is required".

DimensionReasoningScore

Conciseness

Nearly half the body is auto-generated template boilerplate that duplicates the real content: two each of "When to Use", "Key Features", "Dependencies", "Example Usage", and "Implementation Details", plus filler like "Use this skill when the request matches its documented task boundary", "Skill directory: 20260316/scientific-skills/...", and a "Quick Validation" section stating "No local script validation step is required for this skill". This matches anchor 2 ("Noticeably verbose; several unnecessary explanations or padded sections"). It is not 3 because the duplication is extensive whole-section padding rather than occasional slack, and not 1 because the substantive sections 1–5 are themselves reasonably tight with no concept explanations Claude already knows.

2 / 5

Actionability

Sections 1–5 deliver concrete, executable benchling-sdk code for auth (API key and OAuth), entity create/update, pagination, inventory containers/boxes/transfers, async task waiting, and retry strategy, with env-var setup and a runnable main example — anchor 4 ("Mostly executable guidance; concrete code or commands with minor gaps"). It is not 5 because of real gaps: the Events/Data Warehouse section is prose-only with no code or steps, the second registry snippet combines entity_registry_id with naming_strategy while its own comment says not to, and snippets reference a benchling instance that isn't shown. It is not 3 because the code is genuinely copy-paste executable, not pseudocode.

4 / 5

Workflow Clarity

A sequence exists ("Recommended Workflow": validate request → select execution path → produce output → final validation pass) but the steps are generic template language with no Benchling-specific checkpoints, and the "Quick Validation" section explicitly says no validation is required — matching anchor 3 ("Steps listed but validation gaps; sequence present but checkpoints missing or implicit"). It is not 4 because no concrete, actionable validation checkpoint exists anywhere (the one validation section is a no-op), and the duplicated When-to-Use/Implementation-Details sections blur which path to follow. It is not 2 because the steps are listed and coherent, and the SDK snippets embed small correctness cues (e.g., poll intervals, the entity_registry_id note).

3 / 5

Progressive Disclosure

The bundle has three real reference files (references/api_endpoints.md, references/authentication.md, references/sdk_reference.md), but the body only hedges at them once — "Additional reference docs may exist in references/ (e.g., ...)" — with no per-topic links, while substantial SDK/API detail is inlined in the body. Scored against the actual bundle structure, this matches anchor 3 ("Some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline"). It is not 4 because references are neither definitely asserted nor woven into navigation, and not 2 because the files do exist, are named, and the body has clear section organization.

3 / 5

Total

12

/

20

Passed

Description

73%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 domain-distinct and covers the Benchling capability areas with a reasonable natural-keyword set, giving it solid trigger quality and near-zero conflict risk. Its weaknesses are the generic single-verb action framing ("manage" a noun list) and a when-clause that restates the what instead of naming user-side triggers, plus the second-person "when you need to" phrasing.

Suggestions

Replace the single generic verb "manage" with varied concrete actions, e.g., "Create and update registry entities (DNA/AA sequences, mixtures), automate inventory transfers and check-in/out, write ELN entries, poll workflow tasks, and query the data warehouse".

Rewrite the when-clause with user-side trigger phrases: "Use when the user mentions Benchling, registry IDs (e.g., bfid/src_), ELN or notebook entries, or syncing Benchling data with external systems".

Use third person: change "Integrate with... when you need to" to "Integrates with the Benchling R&D platform when the task requires...".

DimensionReasoningScore

Specificity

"programmatically manage registry entities, inventory, ELN entries, workflows, events, or data warehouse analytics" names the domain and enumerates several capability areas, but the only action verbs are the generic "Integrate" and "manage" applied to a noun list (no create/update/transfer-style concrete actions), which matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") better than anchor 4's varied specific actions. It is not 2 because the enumerated objects are far more concrete than "Processes PDF files", and not 4 because the verbs are generic rather than several distinct specific actions. Additionally, the second-person phrase "when you need to" triggers the 1-point voice penalty (4 → 3).

3 / 5

Completeness

Both "what" ("Integrate with the Benchling R&D platform... via API/SDK") and "when" ("when you need to programmatically manage...") are present, so the anchor-3 cap for a missing trigger clause does not apply. It is not 5 because the when-clause is circular — it restates the what rather than giving user-side trigger phrases like "when the user mentions Benchling, registry IDs, or ELN entries" — matching anchor 4's "'when' could be more explicit or specific". It is not 3 because an explicit when-clause does exist.

4 / 5

Trigger Term Quality

Natural Benchling-domain terms users would say are well covered: "Benchling", "registry entities", "inventory", "ELN entries", "workflows", "events", "data warehouse", "analytics", "API/SDK" — good keyword coverage matching anchor 4. It falls short of anchor 5 because common synonyms/variants are missing (e.g., "notebook" for ELN, "sequences", "containers", "Benchling SDK" as a standalone phrase), but it is well above anchor 3 since multiple natural phrases are present.

4 / 5

Distinctiveness Conflict Risk

"Benchling R&D platform" plus domain-specific triggers (registry entities, ELN entries, data warehouse analytics) form a clear niche with minimal overlap risk — no other skill category would be invoked by these terms, matching anchor 5. It is clearly not 4, since even closely related bioinformatics or lab-tools skills would not collide on "Benchling", "ELN entries", or "registry entities".

5 / 5

Total

16

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

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.