CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

biopython-advanced

Advanced Biopython modules for motifs, population genetics, sequence utilities, restriction analysis, clustering, and GenomeDiagram visualization; use when you need extended bioinformatics analysis beyond basic sequence I/O and alignment.

Quality

78%

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

Quality

Content

67%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-organized body with genuinely executable, convention-consistent examples and an appropriate split of detail into references/advanced.md. The main costs are repetition of the workflow conventions across three sections, examples that assume an uncreated outputs/ directory, and advertised features (PopGen, clustering, GenomeDiagram) lacking inline examples or explicit pointers to the reference file.

Suggestions

State the workflow conventions (config path, UTF-8, ensure_ascii=False) once and remove the duplicates in Key Features and Implementation Details.

Have example scripts create the outputs directory (os.makedirs("outputs", exist_ok=True)) or note that it must exist, so the copy-paste examples run without failure.

In "When to Use" or "Key Features", link each advertised area (PopGen, clustering, GenomeDiagram) to the relevant section of references/advanced.md so users can navigate directly.

DimensionReasoningScore

Conciseness

The workflow conventions (config/task_config.json, UTF-8 encoding, ensure_ascii=False) are stated three times across "Key Features", the "Example Usage" preamble, and "Implementation Details > I/O requirements", and Implementation Details largely restates what the examples already show. Mostly efficient but with noticeable repetition that could be consolidated into one statement.

3 / 5

Actionability

Three complete, copy-paste-ready scripts with config files and run commands (e.g. motif_stats.py with RestrictionBatch search and JSON output) are fully executable. Minor gaps: scripts write to an outputs/ directory they never create, and PopGen, clustering, and GenomeDiagram — advertised in "When to Use" — get no example or code pointer in the body.

4 / 5

Workflow Clarity

A clear, uniform sequence is shown per task: write config/task_config.json, run python scripts/<task>.py, read outputs/*.json. Validation is present only as advisory notes ("Validate CDS frame and stop codons"), not as explicit steps, so it matches the 4 anchor of clear sequence with minor validation gaps; these are non-destructive single-sequence analyses so the destructive-cap does not apply.

4 / 5

Progressive Disclosure

Good structure: overview sections plus runnable examples inline, with the bulk of module detail (577 lines covering PopGen, Cluster, GenomeDiagram, CodonTable, etc.) correctly split into the single, one-level-deep, clearly described reference references/advanced.md, which exists and matches what the body promises. Minor gaps: the reference is signposted only once at the very end, and PopGen/clustering/GenomeDiagram are never linked to it from the sections that advertise them.

4 / 5

Total

15

/

20

Passed

Description

82%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 explicit what-and-when structure, a concrete scope boundary against basic Biopython usage, and good domain keywords. Its main weaknesses are the second-person voice in the trigger clause and trigger terms limited to module-area names rather than task-oriented synonyms users would say.

Suggestions

Rewrite in third-person voice to avoid the second-person penalty, e.g. "...visualization; use when extended bioinformatics analysis beyond basic sequence I/O and alignment is needed" or "Use when performing extended bioinformatics analysis...".

Add task-oriented trigger synonyms users would naturally say, such as "codon usage", "restriction enzyme cut sites", "PWM/consensus motifs", or "GC content".

Frame capabilities as concrete actions (e.g. "Finds restriction enzyme cut sites", "Computes codon usage frequencies") rather than listing module-area nouns.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas ("motifs, population genetics, sequence utilities, restriction analysis, clustering, and GenomeDiagram visualization"), which fits the 4 anchor, but the trigger clause "use when you need" uses second-person voice, which the guidelines penalize by reducing specificity by 1. The capability areas are named as module topics rather than actions, which keeps it from scoring higher.

3 / 5

Completeness

It clearly answers "what" (module areas enumerated) and explicitly answers "when" with a concrete boundary: "use when you need extended bioinformatics analysis beyond basic sequence I/O and alignment". This matches the 5 anchor of explicit what-and-when with concrete trigger phrasing; it is above the 4 anchor because the when-clause is specific rather than generic.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "bioinformatics", "motifs", "restriction analysis", "population genetics" are phrases users would naturally say. A few common variations are missing, e.g. "codon usage", "restriction enzymes"/"cut sites", "PWM", or "GC content", so it falls short of the comprehensive-synonym 5 anchor.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (advanced Biopython analyses) and explicitly distinguishes it from basic usage ("beyond basic sequence I/O and alignment"), minimizing risk of triggering for a general Biopython or basic-sequence skill. Minimal conflict risk fits the 5 anchor.

5 / 5

Total

17

/

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

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

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