CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cnv-caller-plotter

Detect copy number variations from whole genome sequencing data and generate publication-quality genome-wide CNV plots. Supports CNV calling, segmentation, and visualization for cancer genomics and rare disease analysis.

Quality

56%

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/cnv-caller-plotter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

31%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 dominated by generic genomics textbook content and duplicated template boilerplate rather than lean, skill-specific instruction, and its code examples do not fully match the bundled placeholder script. Progressive disclosure is inverted: heavy inline reference material while the one existing reference file is mislabeled as absent.

Suggestions

Move Common Patterns, Common Pitfalls, Troubleshooting, and the quality checklists into files under references/ and link them from a short overview; also fix the false claim that no reference files exist (references/runtime_checklist.md is present).

Cut the duplicated boilerplate sections (When to Use / Key Features / Dependencies / Example Usage / Implementation Details overlap) and repair the broken "See ## Prerequisites/Usage/Workflow above" cross-references and out-of-order sections.

Align examples with the actual script: define or remove the undefined identify_somatic call, disclose prominently that call_cnvs/plot_genome_wide are placeholders (or implement them), and replace commented-out '# Example invocation' lines with real, runnable commands using actual file inputs.

DimensionReasoningScore

Conciseness

The ~1180-line body extensively explains domain concepts Claude already knows — "Somatic vs Germline Classification" tables, a full "BED Format Specification", "CNV Detection Methods Comparison", pages of "Common Pitfalls" and "Troubleshooting" for standard genomics issues — and is heavily padded with duplicated boilerplate sections ("See `## Prerequisites` above", "See `## Usage` above", "See `## Workflow` above") for a script that is 68 lines. This matches the 'severely verbose; extensively explains concepts Claude already knows; heavily padded' anchor.

1 / 5

Actionability

There is real, executable-style guidance: concrete Python API examples ("caller.call_cnvs(...)", "caller.save_bed(...)"), CLI commands whose flags match the actual script (--input, --reference, --output, --bin-size, --plot-format), and a runnable quick check. But guidance is incomplete: the "Complete Workflow Example" calls an undefined "identify_somatic" function, "plot_genome_wide" in the bundled script only prints a path without creating a plot (undisclosed except as a buried 'Known Issues' note), and example invocations are commented-out placeholders with nonsense inputs ("--input 'Audit validation sample with explicit symptoms...'"), matching the 'some concrete guidance but incomplete' anchor.

3 / 5

Workflow Clarity

Sequences and checkpoints exist — a 5-step "## Workflow" with fallback, a 4-step "Complete Workflow Example", and pre/during/post-analysis checklists with critical items. But the workflow is fragmented across at least four overlapping sections (Workflow, Example Usage run plan, Implementation Details, Complete Workflow Example) with broken "See ## X above" cross-references and out-of-order sections (Usage and Prerequisites appear near the end), so checkpoints are scattered rather than clearly sequenced — between the 'validation gaps' (3) and 'most checkpoints present' (4) anchors, landing at 3.

3 / 5

Progressive Disclosure

The body claims "(No reference files currently available for this skill)" while references/runtime_checklist.md actually exists and is never linked, and "Reference material available in `references/`" is contradicted one section later. Meanwhile ~900 lines of reference-grade material (Common Patterns, Quality Checklist, Common Pitfalls, Troubleshooting, method comparisons) that clearly belongs in separate reference files are inlined in SKILL.md, matching the 'content that clearly belongs in separate files is inlined' anchor; structure via headers keeps it above 1.

2 / 5

Total

9

/

20

Passed

Description

66%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, specific description with good natural trigger terminology for the CNV/WGS domain. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness, plus minor gaps in format-level keywords.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions CNVs, copy number analysis, copy number variations, or needs genome-wide CNV plots from WGS data".

Include common trigger variations and file extensions such as WGS, BAM, VCF, and .bed to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Detect copy number variations from whole genome sequencing data", "generate publication-quality genome-wide CNV plots", "Supports CNV calling, segmentation, and visualization" — going beyond naming the domain. It falls short of the 5 anchor only because coverage has minor gaps (no input formats like BAM/VCF or export output mentioned), matching 'lists several specific actions; minor gaps in coverage'.

4 / 5

Completeness

The 'what' is clearly and explicitly stated (CNV detection, segmentation, visualization, plotting), but there is no "Use when..." clause or equivalent explicit trigger guidance; the 'when' is only weakly implied by "for cancer genomics and rare disease analysis". Per the rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural domain terms are present: "copy number variations", "whole genome sequencing", "CNV", "CNV calling", "segmentation", "cancer genomics", "rare disease" — phrases a genomics user would actually say. Not a 5 because common variations/extensions are missing ("WGS", "BAM", ".bam", "structural variants").

4 / 5

Distinctiveness Conflict Risk

Phrases like "copy number variations", "CNV calling", and "genome-wide CNV plots" establish a clear niche that would rarely trigger for unrelated skills. Minor overlap risk remains with closely related genomics skills (e.g., general variant callers or circos/heatmap plotters), matching the 'mostly distinct' anchor rather than the 'clear niche with minimal conflict' anchor.

4 / 5

Total

15

/

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

skill_md_line_count

SKILL.md is long (1180 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/cnv-caller-plotter/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.