CtrlK
BlogDocsLog inGet started
Tessl Logo

biopython

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

61

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 ./backend/cli/skills/biology/biopython/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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.

A well-structured, highly actionable overview with genuinely useful one-level-deep references, but the body is noticeably bloated: routing content is repeated across four sections, grep guidance appears twice, and a version-anchored claim (Biopython 1.85, January 2025) sits in the Overview. Workflow guidance also lacks validation checkpoints despite covering batch operations.

Suggestions

Collapse the 'When to Use This Skill', 'Core Capabilities', and 'Summary' sections into a single routing table — the same domain list is repeated four times and could cut the body roughly in half.

Remove the 'Biopython 1.85 (released January 2025)' version/date claim from the Overview, or move it to a dedicated versioning section, since time-sensitive details penalize conciseness and it conflicts with the frontmatter's biopython>=1.84 dependency floor.

Add explicit validation checkpoints to the batch workflows (e.g., verify record counts after Entrez batch downloads, retry on HTTPError with backoff) so the batch-operation workflow is not capped at 3.

DimensionReasoningScore

Conciseness

The same routing information is repeated four times ('When to Use This Skill' bullets, 'Core Capabilities', the per-domain 'Use for' lists, and the 'Summary'), the 'Quick Reference' grep block duplicates the one in 'General Workflow Guidelines', and the Overview embeds time-sensitive version info ('Biopython 1.85 (released January 2025)') outside any deprecated section. Several padded/duplicated sections place this at the 2 anchor; not 3 because the redundancy goes beyond 'some unnecessary explanation', and not 1 because the individual sections are not explaining concepts Claude already knows.

2 / 5

Actionability

Mostly executable, copy-adaptable code across every domain section and pattern (e.g., SeqIO.convert, PairwiseAligner, NCBIWWW.qblast, DistanceTreeConstructor), plus concrete grep commands for the references. Minor gaps keep it below 5: Pattern 3 calls NCBIWWW.qblast("blastn", "nt", sequence) with an undefined variable, and the error-handling example uses HTTPError without importing it from urllib.error.

4 / 5

Workflow Clarity

The documentation workflow (identify module → read reference → extract patterns → combine modules) and the writing principles form a clear sequence, but there are no validation or verification checkpoints anywhere, and the skill explicitly covers batch operations (batch downloading with rate limiting, batch processing) — which per the rubric caps workflow clarity at 3. Not 4 because checkpoints are absent rather than minor-gapped.

3 / 5

Progressive Disclosure

Each of the seven domains has a clearly signaled one-level-deep reference (references/sequence_io.md, alignment.md, databases.md, blast.md, structure.md, phylogenetics.md, advanced.md — all verified to exist), matching the good-structure anchor. Not 5 because the body still inlines four multi-domain 'Common Patterns' and duplicated grep guidance that belong in the references, leaving minor organization gaps.

4 / 5

Total

13

/

20

Passed

Description

92%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 actions, explicit use-when triggers, natural domain keywords, and explicit routing to sibling skills (gget, bioservices). The only gap is the absence of file extensions and a few common synonyms (e.g., FASTQ, alignment), which keeps trigger term quality at 4.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'sequence manipulation', 'file parsing (FASTA/GenBank/PDB)', 'phylogenetics', 'programmatic NCBI/PubMed access (Bio.Entrez)', 'BLAST automation' — with comprehensive coverage of the toolkit's domains, matching the score-5 anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

'Comprehensive molecular biology toolkit' plus the enumerated actions explicitly answer what it does, and 'Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics...' provides an explicit when-clause with concrete trigger phrases — clearly the 5 anchor. Not 4, since the when-guidance is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Strong natural keywords users would actually say (FASTA, GenBank, PDB, NCBI, PubMed, BLAST, bioinformatics pipelines), but no file extensions or common synonyms (.fasta, .gb, FASTQ, sequence alignment) — good coverage with a few natural terms missing, per the 4 anchor. Not 3, since the terms present are exactly the natural domain phrases, not generic.

4 / 5

Distinctiveness Conflict Risk

Beyond a clear niche, it actively disambiguates sibling skills ('For quick lookups use gget; for multi-service integration use bioservices'), giving minimal conflict risk — the 5 anchor. Not 4, since it does more than most skills by carving out adjacent tools explicitly.

5 / 5

Total

19

/

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

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
synthetic-sciences/openscience
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.