CtrlK
BlogDocsLog inGet started
Tessl Logo

ngs-dna-somatic-variants

Run or plan tumor-normal, tumor-only, WGS, WES, or cancer-panel somatic variant workflows with pairing, contamination, panel-of-normals, purity, QC, and annotation checks.

70

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable skill body with executable commands and well-organized sections. The main gap is the lack of an explicit error-recovery feedback loop for what is a batch operation.

Suggestions

Add an explicit validation/retry step, e.g. 'If qc/somatic_pair_review.json shows failed pairs or low purity, adjust filters and re-run before reporting.'

Note how to detect and recover from a swapped/missing normal (referenced in Decision Points) with a concrete re-run command.

DimensionReasoningScore

Conciseness

Lean and efficient with no concept-explanation fluff: it jumps straight to inputs, routing, executable commands, and outputs, assuming Claude's competence throughout.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands — the preflight, Mutect2 runner, and nf-core invocations — with concrete flags and realistic file paths.

3 / 3

Workflow Clarity

Sequenced routing and a Decision Points checklist provide checkpoints, but for a batch bioinformatics operation there is no explicit validate→fix→retry feedback loop, which caps this at 2 per the scoring notes.

2 / 3

Progressive Disclosure

A compact, well-organized single-purpose body with clearly labeled sections and no need for external bundle files; the skill is self-contained and easy to navigate.

3 / 3

Total

11

/

12

Passed

Description

82%Weight 40%Scale 1-3

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, well-triggered, distinctive description for a clearly scoped somatic-variant skill. Its one weakness is the absence of an explicit 'Use when...' trigger clause, which leaves the 'when to use it' half only implied.

Suggestions

Append an explicit trigger clause, e.g. 'Use when running or planning tumor-normal/tumor-only somatic SNV/indel calling from FASTQ, BAM, or CRAM.'

Add the common variation phrase 'somatic mutation calling' so users who say 'mutations' rather than 'variants' also match.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Run or plan ... workflows with pairing, contamination, panel-of-normals, purity, QC, and annotation checks' — matching the 'Lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers 'what' (run/plan somatic variant workflows) but 'when' is only implied; there is no 'Use when...' clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Natural terms a user would actually say are well covered: 'tumor-normal', 'tumor-only', 'WGS', 'WES', 'cancer-panel', 'somatic variant', with no reliance on opaque jargon.

3 / 3

Distinctiveness Conflict Risk

The somatic-variant niche with explicit assay types is clearly distinct from germline/family-analysis skills and unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.