CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bioservices

Unified Python access to 40+ bioinformatics web services; use when you need to query multiple databases (e.g., UniProt/KEGG/ChEMBL/Reactome) with one consistent API in a single workflow, especially for cross-database analysis and identifier mapping.

Quality

80%

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/Data Analysis/bioservices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 an excellent runnable multi-service example and concrete operational guidance, and it is mostly token-efficient. Its one significant structural flaw is progressive disclosure: a rich bundle of reference docs and ready-made scripts exists but is never referenced from SKILL.md, while overlapping API detail is inlined in the body.

Suggestions

Add a 'References' / 'Advanced' section linking the bundle files, e.g., 'Complete service API reference: see references/services_reference.md; identifier mapping guide: see references/identifier_mapping.md; workflow patterns: see references/workflow_patterns.md', and link the four ready-made scripts in scripts/.

Move the inlined per-service method signatures from 'Implementation Details' into references/services_reference.md, keeping only the 2-3 most common patterns in SKILL.md.

Show one concrete error-handling/retry pattern (try/except with backoff) in the example to close the validation gap flagged in the operational considerations.

DimensionReasoningScore

Conciseness

Mostly efficient: the example script is dense and every API fact earns its place, and there is no padding explaining concepts Claude already knows. The 'Key Features' section (7 marketing-style bullets) and 'When to Use' partially duplicate each other and the description, which is the trimmable over-explanation keeping it below the lean anchor.

4 / 5

Actionability

Fully executable, copy-paste-ready script covering six common workflows with real identifiers ('P43403', 'hsa04660', 'C11222'), an install command ('uv pip install bioservices pandas'), concrete method signatures, and specific data-handling guidance (pandas.read_csv(io.StringIO(text), sep='\t')). The single omission (BLAST) is explicitly justified as staying lightweight.

5 / 5

Workflow Clarity

The example is a clearly numbered 1-6 sequence with operational checkpoints (rate limits, TIMEOUT, 'design workflows to degrade gracefully (try/except, fallbacks)'). Below the top anchor because validation is advised rather than demonstrated — the example itself contains no error handling. The destructive/batch validation cap does not apply since these are read-only remote queries.

4 / 5

Progressive Disclosure

Scored against the actual bundle: references/ contains three substantial docs (identifier_mapping.md, services_reference.md, workflow_patterns.md) and scripts/ contains four workflow scripts, but SKILL.md never links to or mentions any of them — the bundle's detail material is undiscoverable from the main file. Meanwhile per-service method signatures that duplicate services_reference.md are inlined under 'Implementation Details'. This matches the 'references are buried / content that belongs in separate files is inlined' anchor; it is not a 3 because anchor 3 presumes references are at least present but poorly signaled, whereas here they are absent from the document entirely.

2 / 5

Total

15

/

20

Passed

Description

78%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 with an explicit and specific when-clause, concrete database-name triggers, and a clear multi-service niche. Its main faults are second-person voice in the trigger clause (explicitly penalized by the rubric) and a few missing natural trigger terms like 'pathway', 'sequence', and 'BLAST'.

Suggestions

Rewrite the when-clause in third person to avoid the specificity penalty, e.g., 'Use when querying multiple databases... in a single workflow' instead of 'use when you need to query...'.

Add one or two high-frequency natural trigger terms such as 'pathway analysis', 'protein sequences', or 'BLAST' to broaden keyword coverage.

DimensionReasoningScore

Specificity

Base 4: 'Unified Python access to 40+ bioinformatics web services', 'query multiple databases (e.g., UniProt/KEGG/ChEMBL/Reactome)', 'cross-database analysis and identifier mapping' list several concrete actions with minor gaps (pathway parsing, sequence analysis, and interaction queries are unmentioned). Reduced by 1 per the rubric's voice rule because the when-clause uses second person ('use when you need to query...').

3 / 5

Completeness

Explicitly answers both what ('Unified Python access to 40+ bioinformatics web services... with one consistent API') and when ('use when you need to query multiple databases... especially for cross-database analysis and identifier mapping') with concrete trigger phrases and named databases. The when-clause is already specific and example-anchored, so the anchor-4 caveat ('could be more explicit') does not apply.

5 / 5

Trigger Term Quality

Good natural-keyword coverage: 'Python', 'bioinformatics', 'UniProt', 'KEGG', 'ChEMBL', 'Reactome', 'cross-database', 'identifier mapping'. A few natural terms users would say are missing, e.g. 'pathway', 'protein sequence', 'BLAST', 'interactions', so it falls short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche — unified multi-database bioinformatics access via one package — anchored by named databases (UniProt/KEGG/ChEMBL/Reactome). Minor overlap risk with single-database skills (e.g., a dedicated UniProt or KEGG skill), keeping it below the minimal-conflict anchor.

4 / 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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/bioservices/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.