CtrlK
BlogDocsLog inGet started
Tessl Logo

ngs-dna-germline-variants

Run or plan deep germline WGS, WES, targeted-panel, cohort, or trio variant-calling workflows with reference-build, known-sites, QC, joint-calling, 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, actionable, well-organized skill body with concrete commands and clear sequencing, held back only by the absence of explicit validation feedback loops around the batch variant-calling execution.

Suggestions

Add an explicit validate→fix→retry checkpoint around execution (e.g., 'Run preflight; if it reports missing tools/resources, resolve them before --execute; re-run preflight to confirm readiness').

State the expected QC pass/fail thresholds that gate proceeding (e.g., contamination, coverage, Ti/Tv) so the validation step is actionable rather than listed among outputs.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's genomics competence — no concept padding explaining WGS/BQSR/gVCF — with every section serving the workflow despite a few advisory caveats.

3 / 3

Actionability

Provides concrete, copy-paste-ready commands (ngs_preflight, run_dna_variant_calling, run_dna_germline_variants) with specific flags like --emit-gvcf, --joint-call, --known-sites, --execute.

3 / 3

Workflow Clarity

Sequence is clear (confirm inputs → preflight → route → run → QC/outputs) with a preflight readiness gate, but lacks explicit validate→fix→retry feedback loops for the batch calling run, capping workflow clarity at 2.

2 / 3

Progressive Disclosure

Self-contained single-file skill with no nested/2+-level references, organized into clear sections (Essential Inputs, Route, Decision Points, Outputs); referenced plugin scripts are external, not bundle files.

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-scoped description with strong trigger terms and low conflict risk, weakened only by the absence of an explicit 'Use when...' trigger clause.

Suggestions

Add an explicit 'Use when...' clause naming the user situations that should trigger this skill (e.g., 'Use when running or planning germline WGS/WES/panel or cohort/trio variant calling from FASTQ, BAM, or CRAM.').

Mirror the body's exclusivity guidance in the description (e.g., 'For tumor-only, tumor-normal, or UMI-panel calling, use a somatic or UMI-panel skill instead.') to further reduce conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (run/plan, variant-calling, reference-build, known-sites, QC, joint-calling, annotation checks) across named data types and sample models.

3 / 3

Completeness

Clearly states what the skill does, but lacks an explicit 'Use when...' trigger clause; the 'when' is only implied, which caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Covers natural domain keywords users would say — germline, WGS, WES, targeted-panel, cohort, trio, variant-calling — with good breadth of common variations.

3 / 3

Distinctiveness Conflict Risk

Scoped to germline WGS/WES/panel/cohort/trio variant calling with distinct terminology, making it unlikely to trigger for the wrong (e.g., somatic) 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.