CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

62

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 ./plugins/ngs-analysis/skills/ngs-dna-somatic-variants/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, largely executable skill body with concrete commands, real validation checkpoints, and disciplined brevity. The main improvement opportunities are specifying the sample-sheet format, adding failure-handling feedback loops around the preflight and resource checks, and splitting the longer reference-style lists into a separate file.

Suggestions

Show the expected somatic_pairs.tsv column format (or point to an example/template file) so the runner command is fully executable end-to-end.

Add brief feedback-loop guidance for checkpoint failures — e.g. what to do when the preflight install plan is incomplete or the resource readiness check reports missing bundles.

Consider moving the resource-plan bundle details (resource_plan.json, manifest, env, readiness flags) into a reference file to keep SKILL.md closer to a lean overview.

DimensionReasoningScore

Conciseness

The body is tight, imperative, and free of explanations of concepts Claude already knows, but a few rationale sentences in Decision Points ("A swapped or missing normal changes the biological meaning of the calls", "explicitly state the false-positive risk") could be trimmed, matching the efficient-with-minor-trimmable-instances anchor.

4 / 5

Actionability

Two executable command blocks with real script paths and flags (preflight with --emit-install-plan; the Mutect2 runner with --sample-sheet, --germline-resource, --panel-of-normals) plus the sarek runner command give mostly copy-paste-ready guidance, but the somatic_pairs.tsv format is never specified and the sarek command has no example arguments, keeping it below fully-executable.

4 / 5

Workflow Clarity

A clear sequence (confirm inputs → preflight → route → run → outputs) with genuine checkpoints (preflight install plan, "Verify tumor-normal pair metadata before execution", advisory-vs-blocking resource readiness) earns the clear-sequence anchor, but there are no explicit feedback loops for what to do when preflight or the resource check fails, which the top anchor requires.

4 / 5

Progressive Disclosure

Sections are well organized with no dangling references and no bundle files to coordinate, but at roughly 63 lines — above the under-50-line simple-skill exception — the dense Outputs and Decision Points lists and the resource-plan paragraph could be split into a reference file, matching the good-structure-with-minor-gaps anchor.

4 / 5

Total

16

/

20

Passed

Description

71%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, domain-rich description with strong natural trigger terms and clear distinctiveness within the somatic-variant niche. Its main weakness is the absence of an explicit "Use when..." trigger clause, which leaves the "when to use" half of completeness only weakly implied.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions somatic SNV/indel calling, tumor-normal pairs, tumor-only analysis, or cancer variant detection from WGS/WES/panel data."

Include common user-facing synonyms and tool names in the description, such as "SNV/indel", "Mutect2", "matched normal", and "VCF", to broaden natural trigger coverage.

Add a one-line negative boundary in the description (e.g. "For inherited germline or family analysis, use the germline skill instead") to further reduce overlap risk with the adjacent germline-variants skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ("pairing, contamination, panel-of-normals, purity, QC, and annotation checks") across the full range of workflow designs and assays ("tumor-normal, tumor-only, WGS, WES, or cancer-panel"), matching the comprehensive-coverage anchor; no gaps are evident within the stated scope.

5 / 5

Completeness

The "what" is clear and concrete (run or plan somatic variant workflows with named checks), but there is no "Use when..." clause or equivalent explicit trigger guidance — "Run or plan" only weakly implies when to use the skill, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms like "tumor-normal", "WGS", "WES", "cancer-panel", "somatic variant", "panel-of-normals", and "purity" are present, but common variations users would say are missing ("SNV/indel", "Mutect2", "matched normal", "VCF"), matching the good-coverage-with-a-few-missing anchor rather than the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

"Somatic" plus tumor/purity terminology carves a mostly distinct niche, but the body itself routes germline requests to a sibling germline skill and broad terms ("WGS", "WES", "QC") carry minor overlap risk with closely related NGS skills, matching the mostly-distinct anchor rather than minimal-conflict.

4 / 5

Total

16

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openai/plugins

Path

plugins/ngs-analysis/skills/ngs-dna-somatic-variants/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.