CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

biopython

Primary Python toolkit for molecular biology. Preferred for Python-based PubMed/NCBI queries (Bio.Entrez), sequence manipulation, file parsing (FASTA, GenBank, FASTQ, PDB), advanced BLAST workflows, structures, phylogenetics. For quick BLAST, use gget. For direct REST API, use pubmed-database.

Quality

72%

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 ./skills_all/biopython/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 is well-organized with abundant concrete code examples, but it is undermined by a broken reference bundle — every referenced file is missing — plus duplicated sections, a version/date stamp that will age, and batch network workflows lacking validation or error-recovery steps.

Suggestions

Ship the seven referenced files under references/ (or remove the pointers and inline the essential content) so the clearly-signaled navigation actually resolves.

Add error handling and validation to batch workflows, e.g. wrap Pattern 3's fetch loop in try/except with retry/backoff and verify each record parsed before proceeding.

Trim the duplicated grep-pattern sections and the redundant Summary section, and move the 'Biopython 1.85 (released January 2025)' version stamp into a version-compatibility note so it does not silently age.

DimensionReasoningScore

Conciseness

The body is mostly efficient and code-focused, but it duplicates grep search patterns in both "General Workflow Guidelines" and "Quick Reference", adds a redundant "Summary" section restating earlier guidance, and embeds time-sensitive version info ("Biopython 1.85 (released January 2025)") outside any deprecated/old-patterns section. This matches 'mostly efficient but could be tightened' rather than the minor-trim level.

3 / 5

Actionability

Concrete, largely executable code appears throughout (per-module quick examples, four full patterns, setup instructions), but there are minor gaps: Pattern 3 references an undefined `sequence` variable, and the error-handling example uses `HTTPError` without importing it from urllib.error. This sits at 'mostly executable with minor gaps', short of copy-paste-ready.

4 / 5

Workflow Clarity

The "Reading Documentation" section gives a clear 4-step sequence with concrete grep commands, but no validation checkpoints exist, and batch operations (Pattern 3's loop of NCBI fetches; "Batch downloading with proper rate limiting") run without any error handling or verification. The batch-operation cap limits this to 3.

3 / 5

Progressive Disclosure

References are clearly signaled and one level deep with a consistent per-module structure, which is good — but none of the seven referenced files (references/sequence_io.md, alignment.md, databases.md, blast.md, structure.md, phylogenetics.md, advanced.md) actually exist in the bundle, so navigation is broken, and substantial content (patterns, troubleshooting, best practices) is inlined in a ~440-line SKILL.md. Structure is better than 'minimal' but the dangling references and inlining keep it below 'good structure'.

3 / 5

Total

13

/

20

Passed

Description

75%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, specific description with excellent domain coverage and explicit conflict-avoidance routing to sibling skills. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the activation condition only weakly implied.

Suggestions

Add an explicit trigger clause, e.g. "Use when working with biological sequences, bioinformatics file formats (FASTA, GenBank, FASTQ, PDB), or running BLAST/NCBI queries in Python."

Include common user phrasings and extensions such as "bioinformatics", "sequence alignment", ".fasta", and ".fastq" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities with named modules and formats — "PubMed/NCBI queries (Bio.Entrez), sequence manipulation, file parsing (FASTA, GenBank, FASTQ, PDB), advanced BLAST workflows, structures, phylogenetics" — which is comprehensive coverage of the domain, matching the top anchor rather than the 'minor gaps' level below.

5 / 5

Completeness

The 'what' is clear and concrete, but there is no explicit 'Use when...' clause; "Preferred for Python-based PubMed/NCBI queries" only weakly implies a trigger and the routing sentences ("For quick BLAST, use gget") describe when not to use it. Per the judging guidelines, a missing explicit use-when clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("BLAST", "FASTA", "GenBank", "PDB", "PubMed", "phylogenetics") that users would actually say, but common variations like "bioinformatics", "sequence alignment", and file extensions (.fasta, .fastq) are missing — noticeably above the midpoint but short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche ("Primary Python toolkit for molecular biology") and explicitly disambiguates from adjacent skills ("For quick BLAST, use gget. For direct REST API, use pubmed-database"), giving minimal conflict 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: 11 missing

Warning

Total

15

/

16

Passed

Repository

Microck/ordinary-claude-skills

Path

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