CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bioservices

Primary Python tool for 40+ bioinformatics services. Preferred for multi-database workflows: UniProt, KEGG, ChEMBL, PubChem, Reactome, QuickGO. Unified API for queries, ID mapping, pathway analysis. For direct REST control, use individual database skills (uniprot-database, kegg-database).

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills_all/bioservices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 delivers strong, concrete, largely executable guidance for the main bioservices capabilities, organized into clear sections. Its weaknesses are duplicated identifier-mapping examples, absent validation/feedback loops in batch and async workflows, and a progressive-disclosure structure whose referenced files and scripts do not actually exist in the bundle.

Suggestions

Ship the referenced bundle files or remove the references: references/services_reference.md, references/workflow_patterns.md, references/identifier_mapping.md, and the four scripts/*.py files are cited in the body but absent from the bundle, so every pointer is a dead end.

Consolidate the identifier-mapping material: sections 1, 3, and 5 repeat the same UniProt mapping and UniChem get_compound_id_from_kegg examples; keep one section in SKILL.md and defer the rest to references/identifier_mapping.md.

Add validation checkpoints to batch and async workflows: verify BLAST job status with a retry loop before fetching results, and have batch_id_converter.py report input/output ID counts so failures surface before results are reported as complete.

DimensionReasoningScore

Conciseness

The body is mostly concrete API usage rather than explanations of known concepts, but the UniProt/UniChem mapping code appears nearly verbatim in sections 1, 3, and 5, and the generic try-except boilerplate plus the "Integration with Other Tools" list add padding. It could be meaningfully tightened through deduplication.

3 / 5

Actionability

Concrete, executable code with real method names and parameters (e.g., `u.mapping(fr="UniProtKB_AC-ID", to="KEGG", query="P43403")`, `s.query("mint", "ZAP70 AND species:9606")`) plus runnable script invocations. Minor gaps keep it from 5: the BLAST example references an undefined `protein_sequence` variable and placeholder email, and a few method signatures cannot be verified.

4 / 5

Workflow Clarity

Sequences are present (numbered compound workflow, pipeline script step list, "Check status before retrieving results" for BLAST), but there are no validation or feedback loops — the batch_id_converter.py batch operation and the async BLAST flow describe no verification of outputs, which caps this dimension at 3 per the rubric.

3 / 5

Progressive Disclosure

In-body structure and reference signaling are good ("Reference: `references/services_reference.md` for complete UniProt API details"), but every referenced bundle file — the three references/*.md docs and all four scripts/*.py — is missing from the bundle, so navigation dead-ends. Duplicated mapping content is also inlined rather than living in the referenced files.

3 / 5

Total

13

/

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 that names concrete capabilities, specific databases as natural trigger terms, and an explicit preference boundary against competing single-database skills. The main improvement would be converting the "Preferred for multi-database workflows" routing into concrete user-facing trigger phrases and covering more of the package's capabilities (sequences, interactions, compounds).

DimensionReasoningScore

Specificity

"Unified API for queries, ID mapping, pathway analysis" lists several concrete actions alongside named databases ("UniProt, KEGG, ChEMBL, PubChem, Reactome, QuickGO") in correct third-person voice. It falls short of a 5 because "queries" is generic and capabilities the body covers (sequence similarity, interactions, compound search) are absent from the description.

4 / 5

Completeness

Both "what" ("Unified API for queries, ID mapping, pathway analysis") and "when" ("Preferred for multi-database workflows") are present. The "when" is explicit routing guidance rather than an implied trigger, so it clears the cap at 3, but it lacks concrete user-facing trigger phrases (e.g., "when the user mentions UniProt entries") needed for a 5.

4 / 5

Trigger Term Quality

Users needing this skill would naturally say "UniProt", "KEGG", "ChEMBL", "ID mapping", or "pathway analysis" — all present. A few common natural terms are missing (e.g., "protein sequence", "BLAST", "gene ontology"), keeping it below the comprehensive-synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

It carves a clear aggregator niche and actively resolves conflicts with named sibling skills: "For direct REST control, use individual database skills (uniprot-database, kegg-database)". Database-specific names double as distinct triggers, giving minimal overlap risk.

5 / 5

Total

17

/

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

referenced_paths_exist

Referenced path issues: 9 missing

Warning

Total

15

/

16

Passed

Repository

Microck/ordinary-claude-skills

Path

skills_all/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.