CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

igv-validator

Read-level validation of variant calls from any VCF, tumor/normal or tumor-only: counts read support in the BAMs (SNVs, indels, SV breakpoints), compares it with the caller's reported counts, flags artifact patterns, takes one IGV screenshot per variant and writes a report.

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/igv-validator/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 dense, highly actionable body with an exemplary prescriptive workflow, concrete commands, expected outputs, and an unusually strong Gotchas section of domain-specific failure modes. Its weaknesses are repetition of the same cautionary examples across sections and a broken progressive-disclosure structure: the repeatedly-cited GUIDE.md (plus examples/ and demo/) is missing from the bundle.

Suggestions

Ship GUIDE.md in the bundle (or inline the ten modes and the step-by-step walkthrough) — the body directs agents to read it three times, but the file does not exist; likewise verify examples/ and demo/ are present as referenced.

Consolidate the MAPQ-0/alt-contig material (Why This Exists, and two Gotchas entries) into one place, and merge the two DRAGEN chr4 caller-disagreement examples — the same story is told three and two times respectively.

Split the ~400-word Core Capabilities #8 summary paragraph into shorter bullets or move its curated-calls rules into a reference file, and drop the Trigger section that duplicates the frontmatter trigger_keywords.

DimensionReasoningScore

Conciseness

Mostly skill-specific and free of explanations of known concepts, but noticeably repetitious: the GRCh38 alt-contig MAPQ-0 story is told in full three times ("Why This Exists", "Check how the BAMs were aligned", "Losses called from MAPQ-filtered depth"), the DRAGEN chr4 repeat example appears twice ("Caller counts differ", "Caller disagreement is a question"), the Trigger section duplicates the frontmatter trigger_keywords, and Core Capabilities #8 is a ~400-word run-on paragraph. Not 4: the redundancy spans whole sections, beyond "minor instances that could be trimmed".

3 / 5

Actionability

Copy-paste ready commands throughout: four executable CLI invocations in CLI Reference, a demo command with expected output ("7 captioned screenshots in about 10 seconds"), a diagnostic command ("samtools view -H tumor.bam | grep '^@PG'"), a full example report table, and concrete output-structure trees. Not 4: the common cases (single check, whole project, demo, cluster without IGV) are each covered by a specific runnable command.

5 / 5

Workflow Clarity

The seven-step Workflow is clearly sequenced with prescriptive/flexible labels, an explicit validation gate in step 1 ("Stop with a clear message otherwise"), render verification with a retake loop in step 6, and run-level checks referenced from methodology.md. Not 5: the ten Modes section defers its prompts and commands entirely to GUIDE.md, which is not in the bundle, so those sub-workflows cannot actually be followed; "Agents: read GUIDE.md before running the skill" points nowhere.

4 / 5

Progressive Disclosure

Good in principle — SKILL.md as overview, one-level-deep references to references/methodology.md and references/cli-options.md, both real files, clearly signaled with link syntax and read-when guidance — but scored against the actual bundle: GUIDE.md is referenced three times as required reading and does not exist, and examples/ and demo/ are also referenced but absent. Not 4: the most heavily promoted reference is dangling, which breaks navigation for the modes and the whole-project walkthrough; not 2: the two references that do exist are real, substantive, and well-signaled.

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 specific, third-person, action-dense description that clearly conveys what the skill does and occupies a distinct niche. Its main weakness is the missing explicit "Use when..." trigger clause in the description itself, capping completeness, with natural trigger phrases deferred to the trigger_keywords metadata.

Suggestions

Append an explicit when-clause to the description, e.g. "Use when validating somatic variant calls (Mutect2, Strelka, DRAGEN, Manta) against tumor/normal BAMs, or when the user asks whether a mutation is real or wants IGV screenshots of variants."

Fold one or two natural trigger phrasings (e.g. "is this mutation real", "check my calls in IGV") into the description text instead of keeping them only in the separate trigger_keywords list.

DimensionReasoningScore

Specificity

The description lists five concrete actions with per-type detail — "counts read support in the BAMs (SNVs, indels, SV breakpoints), compares it with the caller's reported counts, flags artifact patterns, takes one IGV screenshot per variant and writes a report" — matching the comprehensive multi-action anchor. Not 4: coverage of the skill's capability surface is complete rather than having minor gaps.

5 / 5

Completeness

The "what" is explicit and concrete, but there is no "Use when..." clause or equivalent trigger guidance in the description — applicability is only weakly implied by "from any VCF, tumor/normal or tumor-only", so the guideline cap of 3 applies. Not 4: the when-clause is absent from the description field, not merely under-specified.

3 / 5

Trigger Term Quality

Strong domain keywords a genomics user would naturally say: "VCF", "tumor/normal", "tumor-only", "BAMs", "read support", "IGV screenshot", "SNVs, indels, SV breakpoints". Not 5: common natural synonyms such as "mutation", "somatic", or phrase-style triggers ("is this call real?") are relegated to the separate trigger_keywords field rather than the description itself.

4 / 5

Distinctiveness Conflict Risk

A clear niche — read-level validation of somatic calls against BAMs with IGV screenshots — with distinct triggers (VCF + BAM + read support + IGV) that do not overlap variant calling, annotation, or QC skills. Not 4: no meaningful overlap risk with closely related skills; the tooling and input combination is unique.

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

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

ClawBio/ClawBio

Path

skills/igv-validator/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.