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.
65
52%
Does it follow best practices?
Impact
81%
1.28xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/benchling-integration/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent specificity and domain-specific trigger terms that clearly identify the Benchling R&D platform niche. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The description is concise and uses appropriate third-person voice.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions Benchling, lab notebooks, DNA/protein registries, or needs to interact with Benchling APIs or Data Warehouse.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Access registry (DNA, proteins)', 'inventory', 'ELN entries', 'workflows via API', 'build Benchling Apps', 'query Data Warehouse', 'lab data management automation'. These are concrete, domain-specific capabilities. | 3 / 3 |
Completeness | The 'what' is well-covered with specific capabilities, but there is no explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the nature of the capabilities listed, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Benchling', 'registry', 'DNA', 'proteins', 'inventory', 'ELN', 'workflows', 'API', 'Benchling Apps', 'Data Warehouse', 'lab data'. These cover the key terms a biotech/lab user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — 'Benchling' is a specific platform name, and the combination of R&D, registry, ELN, DNA, proteins, and Data Warehouse creates a very clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is overly long and tries to serve as both a quick-start guide and comprehensive reference, resulting in a bloated main file that undermines its reference file structure. While it provides some executable code examples for core SDK operations, several sections (Events, Data Warehouse, Notebooks) are too vague to be actionable. Critical gaps include missing validation/error-handling workflows for batch operations and unnecessary explanatory text throughout.
Suggestions
Move detailed code examples for each entity type (inventory, notebooks, workflows) into reference files, keeping only a concise quick-start with 1-2 core examples in the main SKILL.md
Add explicit validation and error-handling workflows for batch operations (e.g., bulk entity import should include try/except, progress tracking, and verification of created entities)
Remove or drastically shorten the 'When to Use This Skill' section and vague sections like Data Warehouse and Events that lack concrete code - either add real executable examples or defer entirely to reference docs
Cut explanatory prose that Claude already knows (e.g., 'Registry entities include DNA sequences, RNA sequences...' and 'Benchling is a cloud platform for life sciences R&D') to reduce token waste
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines. It explains concepts Claude already knows (what Benchling is, what ELN entries are, what pagination is), includes redundant 'Key Operations' summary lists after showing code examples, and has sections like Data Warehouse and Events that are mostly vague filler without actionable content. Many sections could be cut by 50%+ or moved to reference files. | 1 / 3 |
Actionability | The core SDK sections (authentication, entity creation, inventory) provide executable Python code examples which is good. However, several sections (Events & Integration, Data Warehouse, Notebook operations) are vague and lack concrete code. The 'entry_links.create' and 'containers.transfer' examples may not match actual SDK methods, and some placeholder IDs reduce copy-paste readiness. | 2 / 3 |
Workflow Clarity | There are no clear multi-step workflows with validation checkpoints. The bulk entity import example has no error handling or validation. The Events & Integration section lists steps at a high level without concrete implementation. For operations like bulk imports and inventory transfers (which are destructive/batch), there are no feedback loops or verification steps. | 1 / 3 |
Progressive Disclosure | The skill references external files (references/authentication.md, references/sdk_reference.md, references/api_endpoints.md) which is good progressive disclosure. However, the main file itself is a monolithic wall of content that should have much more pushed into those reference files. The overview tries to be both a quick-start guide and a comprehensive reference, defeating the purpose of the reference files. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- K-Dense-AI/claude-scientific-skills
- Commit
b58ad7e
- 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.