CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pysam

Genomic file toolkit. For reading/writing SAM/BAM/CRAM alignment files, VCF/BCF variant files, FASTA/FASTQ sequences, extracting regions, calculating coverage, suitable for NGS data processing pipelines.

Quality

70%

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

The second half of the body is a genuinely good pysam reference — executable quick-start code, accurate coordinate-system and indexing guidance, real pitfalls, and well-organized references to four substantial bundle files. However, the first half is auto-generated template boilerplate (duplicated lowercased description, a directory listing as 'Example Usage', self-referential filler) that wastes tokens and confuses navigation.

Suggestions

Delete the auto-generated boilerplate sections ('When to Use' through 'Implementation Details', lines ~11–54): they duplicate the description in lowercase, present a directory listing as 'Example Usage', and reference a 'documented workflow' that does not exist.

Add one concrete end-to-end workflow with validation checkpoints, e.g., index a BAM (pysam.index), verify the .bai exists, fetch a region, and handle the missing-index error — turning the generic 'Example run plan' into real sequenced guidance.

Inline one write-side example (e.g., creating a BAM or VCF with the correct header) since the description promises 'reading/writing' but all quick-start examples are read-only.

DimensionReasoningScore

Conciseness

Roughly the first half of the body is auto-generated boilerplate: 'Use this skill when you need genomic file toolkit. for reading/writing sam/bam/cram...' merely lowercases the description, and 'Key Features', 'Dependencies', 'Example Usage' (a directory listing: 'Skill directory: 20260316/scientific-skills/...'), and 'Implementation Details' add generic filler ('Execution model: validate the request...') with no pysam-specific value. This matches 'Noticeably verbose; several unnecessary explanations or padded sections'; it is not a 3 because the padding is extensive structural filler rather than occasional tightening opportunities, though the second half is genuinely lean.

2 / 5

Actionability

The latter half provides complete, executable code for the common cases: AlignmentFile fetch, VariantFile iteration, FastaFile extraction, and samtools/bcftools invocations with error handling ('try: pysam.samtools.sort... except pysam.SamtoolsError'). It is not a 5 because the examples cover only a narrow slice (no write-side or pileup examples inline) and the 'Command-Line Tools' snippets assume pre-existing inputs the user doesn't yet have (e.g., creating an index first).

4 / 5

Workflow Clarity

The skill is reference-oriented rather than workflow-driven: sections progress from installation to examples to capabilities to pitfalls, but there is no sequenced multi-step workflow with validation checkpoints — the 'Example run plan' is generic template filler ('Follow the documented workflow exactly') referencing a workflow that is never documented, and no 'check the index exists before fetch()' style checkpoint appears. This matches 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The structure from '## Overview' onward is exemplary: an overview with quick-start code, capability sections each pointing to a real, verified one-level-deep reference file (alignment_files.md, variant_files.md, sequence_files.md, common_workflows.md), plus a 'Getting Help' routing section. It falls short of 5 because the boilerplate front half buries this structure — e.g., 'See `## Overview` above for related details' appears before the Overview section even exists — muddying navigation.

4 / 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, concrete description that names specific file formats and actions across the genomics domain with excellent distinctiveness. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and slightly limits trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g., 'Use when working with BAM/SAM/CRAM alignment files, VCF/BCF variants, or FASTA/FASTQ sequences, or when calculating coverage or extracting genomic regions.'

Include a few natural synonyms users would say, such as 'bioinformatics', 'sequencing data', 'pileup', or 'samtools', to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — 'reading/writing SAM/BAM/CRAM alignment files, VCF/BCF variant files, FASTA/FASTQ sequences, extracting regions, calculating coverage' — covering all of the toolkit's major file-format families. This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage'; it is not score 4 because the action list is broader and more complete than 'minor gaps in coverage' would imply.

5 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance — only the weak suitability phrase 'suitable for NGS data processing pipelines'. Per the judging guidelines, a missing explicit 'Use when' clause caps completeness at 3; it is not a 2 because the 'what' is concrete and detailed, not vague.

3 / 5

Trigger Term Quality

Natural domain terms are well covered (SAM, BAM, CRAM, VCF, BCF, FASTA, FASTQ, NGS, coverage, alignment files, variant files), which are the phrases genomics users actually say. It falls short of the 5 anchor because a few common synonyms are missing (e.g., 'bioinformatics', 'sequencing reads/alignments', 'samtools', 'pileup').

4 / 5

Distinctiveness Conflict Risk

'Genomic file toolkit' with SAM/BAM/CRAM/VCF/BCF/FASTA/FASTQ triggers carves out a clear niche with minimal overlap risk against other skills; these format-specific terms would not naturally trigger a non-genomics skill. This squarely matches the 5 anchor 'Clear niche with distinct triggers; minimal conflict risk'.

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: 2 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

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