CtrlK
BlogDocsLog inGet started
Tessl Logo

adaptyv

Cloud laboratory platform for automated protein testing and validation; use when you have designed protein sequences and need wet-lab experimental validation (e.g., binding, expression, thermostability, enzyme activity) and API-based submission/status/result retrieval.

60

Quality

76%

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/adaptyv/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 Adaptyv-specific core is strong - a runnable submit/poll/retrieve example with error handling and clear async-workflow timing guidance - but the body is a merge of two documents, with a generic boilerplate wrapper that duplicates sections, contradicts itself (dependency versions, whether script validation is required), and inflates token cost. The four cited reference/*.md files are missing from the bundle, breaking the progressive-disclosure structure.

Suggestions

Delete the generic template wrapper sections (the first 'When to Use', 'Key Features', 'Dependencies', 'Example Usage', 'Implementation Details', 'Validation Shortcut' plus the boilerplate tail sections: Output Contract, Validation and Safety Rules, Failure Handling, Quick Validation, Deterministic Output Rules, Completion Checklist) - they duplicate the domain content, contradict it (python>=3.9 vs 3.10+, script validation required vs not required), and cost hundreds of tokens without domain value.

Ship the four referenced files (reference/experiments.md, reference/protein_optimization.md, reference/api_reference.md, reference/examples.md) or remove the dangling pointers; as-is, every 'see reference/...' citation dead-ends and the authoritative endpoint/field details the code example defers to are unavailable.

Resolve the workflow contradictions: pick one dependency spec, one validation instruction, and remove the irrelevant date-stamped path in the wrapper's Example Usage ('cd "20260316/scientific-skills/Others/adaptyv"').

DimensionReasoningScore

Conciseness

Roughly half the body is generic template boilerplate that adds nothing Claude does not already know: 'Use this skill when the request matches its documented task boundary', 'Keep the output safe, reproducible, and within the documented scope at all times', and entire sections (Completion Checklist, Deterministic Output Rules, Output Contract) of behavioral padding. The Adaptyv-specific core (sections 1-5) is tight, but the padded wrapper sections ('several unnecessary explanations or padded sections') match the score-2 anchor; it is not score 1 because the domain content itself is efficient and free of concept explanations.

2 / 5

Actionability

The core guidance is mostly executable: a complete runnable Python example (env var setup, pip install, bearer auth headers, submit/poll/fetch with raise_for_status and timeouts) plus concrete parameter documentation ('sequences', 'experiment_type', 'webhook_url'). It stops short of score 5 because the example hedges ('Adjust endpoint paths/fields to match reference/api_reference.md', 'endpoint/format may vary') and the authoritative details live in reference files that are not in the bundle.

4 / 5

Workflow Clarity

The experiment workflow is a clear sequence with embedded checkpoints: set credentials -> install -> submit -> poll (or webhook) -> download, with explicit error handling in the code (missing-key RuntimeError, raise_for_status, failure/canceled status break). Not score 5 because validation guidance is inconsistent across the document: the wrapper's 'Validation Shortcut' says to run 'python scripts/validate_skill.py --help' while the later 'Quick Validation' section states 'No local script validation step is required for this skill', and dependencies conflict (3.10+ vs >=3.9).

4 / 5

Progressive Disclosure

The body signals one-level-deep references clearly ('reference/experiments.md', 'reference/api_reference.md', etc.), which is the right pattern, but none of the four referenced files exist in the bundle (only scripts/validate_skill.py is present), so the navigation path is broken and the detail those files should hold (assay types, endpoints, schemas) is only vaguely inline. 'Content that should be separate is inline' from the score-3 anchor applies; it stays at 3 rather than 2 because the signaling and in-body section structure are genuinely clear.

3 / 5

Total

13

/

20

Passed

Description

87%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 description: concrete capabilities, an explicit 'use when' clause with specific assay-type triggers, and a distinct niche. Its only flaws are second-person voice ('use when you have designed') and missing natural terms like the platform name 'Adaptyv' and 'assay'.

Suggestions

Rewrite in third person to match the voice guideline, e.g., 'Validates designed protein sequences via wet-lab assays (binding, expression, thermostability, enzyme activity) through the Adaptyv cloud laboratory API; use when protein sequences need experimental validation or API-based experiment submission, status tracking, and result retrieval.'

Add natural trigger synonyms users would say, such as 'Adaptyv', 'assay', 'protein design validation', and 'experiment results', to strengthen trigger-term coverage to comprehensive.

DimensionReasoningScore

Specificity

Names the domain ('Cloud laboratory platform for automated protein testing and validation') and multiple concrete actions: 'wet-lab experimental validation (e.g., binding, expression, thermostability, enzyme activity)' and 'API-based submission/status/result retrieval'. This is comprehensive, matching the score-5 anchor, but the second-person phrasing 'use when you have designed protein sequences' triggers the mandatory 1-point voice penalty, bringing it to 4.

4 / 5

Completeness

Explicitly answers both questions: the 'what' ('Cloud laboratory platform for automated protein testing and validation') and a concrete 'use when' trigger clause ('use when you have designed protein sequences and need wet-lab experimental validation... and API-based submission/status/result retrieval'). This matches the score-5 anchor's structure of what + explicit when with concrete triggers.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'protein sequences', 'wet-lab experimental validation', 'binding', 'expression', 'thermostability', 'enzyme activity', 'submission', 'status', 'result retrieval'. It falls short of the score-5 anchor because it omits the platform name 'Adaptyv' and common synonyms a user might say (e.g., 'assay', 'protein design', 'test my protein'), but it is well above the generic-keyword anchors.

4 / 5

Distinctiveness Conflict Risk

Clear niche: API-driven wet-lab protein validation is highly unlikely to overlap with any other skill, and the enumerated assay types act as distinct triggers. Minimal conflict risk, matching the score-5 anchor.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
aipoch/medical-research-skills
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.