CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gtars

A high-performance Rust toolkit (with Python bindings and a CLI) for genomic interval analysis; use it when you need fast overlap queries, coverage track generation, genomic tokenization for ML, reference sequence verification, or fragment processing.

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

Quality

Content

61%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 structured as a toolkit overview with three runnable examples and a genuine one-level-deep reference bundle, but it restates the same five capabilities across three separate sections and offers no validation steps for its batch operations. Tightening the redundancy, adding post-run verification guidance, and linking references per topic would lift it substantially.

Suggestions

Collapse 'Key Features' and 'Implementation Details' into one section: both restate the five capabilities already enumerated in 'When to Use', cutting roughly a third of the body without losing information.

Add a validation checkpoint after batch operations, e.g. after 'gtars uniwig generate' verify the output track opens and has the expected range (pyBigWig orwiggletools spot-check), and after fragment splitting confirm barcode partition counts sum to the input total.

Replace the single hedged pointer ('Additional module-specific guidance may be available in: ...') with per-topic links under each capability, e.g. under the coverage bullet: 'See references/coverage.md for formats and resolution details'.

DimensionReasoningScore

Conciseness

The 'When to Use', 'Key Features', and 'Implementation Details' sections each restate the same five capabilities (overlap, coverage, tokenizers, reference sequences, fragments), so roughly a third of the body is redundant restatement, plus filler like '(version not specified in the source document)'. It fits anchor 3 (mostly efficient, could be tightened) rather than 2 because there is no explanation of concepts Claude already knows, and rather than 4 because the redundancy spans multiple sections, not minor instances.

3 / 5

Actionability

Three concrete, copy-paste-ready examples are provided (the RegionSet overlap workflow, the 'gtars uniwig generate --input atac_fragments.bed --output coverage.wig --resolution 10' CLI commands, and the TreeTokenizer snippet), covering the common overlap, coverage, and tokenization cases. It falls short of anchor 5 because fragment processing and reference-sequence workflows, two of the five advertised use cases, have no inline executable example.

4 / 5

Workflow Clarity

The examples imply a sequence (load regions, operate, export) but no explicit step sequence or validation checkpoints exist anywhere in the body, and batch operations like 'uniwig' coverage generation and fragment splitting have no verification steps, invoking the guideline cap of 3 for batch operations without validation. It is above anchor 2 because the examples are coherent and unambiguous, not incoherent.

3 / 5

Progressive Disclosure

All six referenced files (references/overlap.md, coverage.md, tokenizers.md, refget.md, python-api.md, cli.md) exist, are substantive, and are exactly one level deep, with the body appropriately kept as an overview. It falls short of anchor 5 because the references are signaled by a single hedged prose line ('Additional module-specific guidance may be available in: ...') rather than well-signaled per-topic links, and it is above anchor 3 because the split itself is appropriate and complete.

4 / 5

Total

14

/

20

Passed

Description

87%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 that explicitly covers what the toolkit does and when to use it, with concrete capability enumeration and a clear niche. Its only deductions are the second-person 'use it when you need' phrasing (voice penalty on specificity) and the absence of common file-format trigger terms like BED, FASTA, and BigWig.

DimensionReasoningScore

Specificity

The description lists five concrete capabilities ('fast overlap queries, coverage track generation, genomic tokenization for ML, reference sequence verification, or fragment processing'), matching the comprehensive anchor 5, but the second-person phrasing 'use it when you need...' triggers the mandated 1-point specificity reduction for non-third-person voice.

4 / 5

Completeness

It clearly answers both questions: the 'what' ('A high-performance Rust toolkit (with Python bindings and a CLI) for genomic interval analysis') and an explicit 'when' clause with concrete trigger phrases ('use it when you need fast overlap queries, coverage track generation, ...'), exactly matching anchor 5; not anchor 4 since the 'when' is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Good natural domain keywords ('overlap', 'coverage track', 'tokenization', 'fragment processing') that genomics users would say, but common variations and file extensions users naturally mention (BED, FASTA, BigWig/WIG, ATAC-seq/ChIP-seq) are absent, fitting anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The genomic-interval niche with domain-specific triggers (tokenization for ML, refget-style verification, fragment processing) is clearly distinct from other skills with minimal conflict risk, matching anchor 5; no generic phrasing that would overlap with unrelated skills.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

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