CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

polars-bio

Fast genomic interval operations (overlap, nearest, merge, coverage, cluster, complement, subtract, count-overlaps), multi-format bioinformatics I/O, DataFusion SQL, and pileup on Polars DataFrames via polars-bio. A scalable bioframe/bedtools alternative.

Quality

77%

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/polars-bio/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 strongly actionable body: the CLI reference and gotchas are executable and empirically grounded, and the workflow validates inputs before running. Weaker on token discipline (marketing and Polars-primer material inlined) and progressive disclosure (most reference files are never linked from the body).

Suggestions

Link all bundle files from the body — add a short reference index pointing to interval_operations.md, pileup_operations.md, sql_processing.md, and configuration.md, so the reader can find them without listing the directory.

Trim the "Why This Exists" and "Polars & the Python ecosystem" sections to one or two lines each and defer the stack/pandas detail entirely to references/polars_primer.md, which already covers it.

Add an explicit error-recovery step to the Workflow (e.g. "if validation fails, report the specific missing input and ask or fall back to --demo"), turning the implicit checkpoints into a feedback loop.

DimensionReasoningScore

Conciseness

The core sections (CLI Reference, Gotchas, Example Output) are dense and earn their tokens, but "Why This Exists", "Polars & the Python ecosystem" (a stack diagram and pandas comparison that largely duplicate references/polars_primer.md), and the marketing-style performance paragraph pad the body with content Claude doesn't need inline. Mostly efficient but could be tightened — matches anchor 3 rather than 4 because several sections are over-explanation rather than isolated instances.

3 / 5

Actionability

The CLI Reference gives copy-paste-ready commands for every subcommand with exact flags (`overlap --a a.bed --b b.bed --output <dir>`, `--describe`, `--min-mapping-quality 20`), the demo fallback is a literal quoted action, and Example Output shows the actual result.json/report.md. Fully executable with common cases covered — matches the top anchor, not 4, since there are no gaps in the command surface.

5 / 5

Workflow Clarity

The four-step Workflow opens with an explicit Validate step ("confirm the subcommand and that required inputs exist (BED >=4 cols; BAM has a .bai)") and includes a mandatory demo fallback, and Gotcha 7 documents the error path for a missing BAM index. Not a 5 because there is no explicit validate→fix→retry feedback loop (e.g. what to do when validation fails); not a 3 because checkpoints are present and explicit, not merely implicit.

4 / 5

Progressive Disclosure

The body appropriately delegates detail to references/polars_primer.md and references/file_io.md (both real files, one level deep), but four of the six bundle files — configuration.md, interval_operations.md, pileup_operations.md, sql_processing.md — are never mentioned anywhere in SKILL.md, leaving them undiscoverable. That is more than a minor organization gap, so anchor 3 fits better than 4.

3 / 5

Total

15

/

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 highly specific, well-differentiated description that names its full operation set and positions itself clearly against bioframe/bedtools. Its main weakness is the absence of an explicit 'Use when…' trigger clause, which caps completeness and leaves activation timing only implied.

Suggestions

Append an explicit 'Use when…' clause, e.g. "Use when the user asks to intersect/merge/complement BED intervals, compute coverage or pileup, or run SQL on BED/VCF/BAM files."

Include natural synonyms and file extensions in the description itself (e.g. ".bed/.vcf/.bam", "intersect", "per-base depth"), since the rich trigger_keywords list in frontmatter metadata is separate from the description field the model sees.

Consider a one-phrase scope boundary in the description (e.g. "not for variant annotation or calling") to further reduce mis-triggering against sibling VCF skills.

DimensionReasoningScore

Specificity

Enumerates eight concrete interval operations ("overlap, nearest, merge, coverage, cluster, complement, subtract, count-overlaps"), plus "multi-format bioinformatics I/O, DataFusion SQL, and pileup on Polars DataFrames" — comprehensive and concrete, matching the top anchor. It is not a 4 because coverage of the skill's action surface is essentially complete rather than having minor gaps.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when…' clause or equivalent explicit trigger guidance in the description — timing is only weakly implied by "A scalable bioframe/bedtools alternative", which caps completeness at 3 per the judging guidelines. Not a 2 because the 'what' half is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Contains strong natural terms users would say — "overlap", "merge", "coverage", "genomic interval operations", "bioframe/bedtools alternative" — but misses common variations and file extensions like ".bed", "intersect", "pileup depth" in the description text itself. It is a 4 rather than 5 because the extension/synonym coverage is incomplete, and not a 3 because the terms present are the natural phrases genomics users actually use.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — DataFrame-native genomic interval arithmetic positioned explicitly against bioframe/bedtools — with triggers (overlap, pileup, DataFusion SQL) unlikely to fire for annotation, QC, or phylogenetics skills. Minimal conflict risk; clearly matches the top anchor rather than the 'minor overlap risk' anchor below it.

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

ClawBio/ClawBio

Path

skills/polars-bio/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.