CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cancer-genomics-analysis

Computational cancer genomics workflows. Somatic mutation detection and annotation, structural variation characterization, copy number analysis, tumor purity/ploidy estimation, NMF metagene extraction, and DNA damage response network analysis. For cancer mutation databases use cosmic-database; for variant clinical significance use clinvar-database.

Quality

72%

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 ./backend/cli/skills/biology/cancer-genomics-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 thorough, highly actionable body with executable code, clear sequenced workflows, and useful troubleshooting, weakened by monolithic inlining: it duplicates ~2,000 lines of standalone scripts in the bundle without a single pointer to them, and lacks inter-step validation checkpoints in the pipelines.

Suggestions

Reference the existing scripts/ bundle from the body (e.g., "Full CLI implementations: scripts/parse_vcf.py, scripts/calculate_tmb.py, scripts/nmf_metagenes.py, scripts/ddr_network.py") and move the bulk implementations out of SKILL.md, keeping only the Quick Start and one compact example per capability.

Add explicit validation checkpoints between pipeline steps (e.g., verify tumor.cnr/reference.cnn exist and are non-empty after each CNVkit stage before proceeding; check FilterMutectCalls output before annotation), matching the error-recovery pattern already used for Mutect2.

Delete the Overview paragraph that restates the frontmatter description, and make Workflow 4's placeholder constants (PATHWAY_GENES, DRIVER_GENE, GROUP) concrete with a worked example so the snippet is runnable as-is.

DimensionReasoningScore

Conciseness

The body is mostly task-specific code that earns its place, but at ~600 lines it is a monolith: the Overview paragraph restates the frontmatter description nearly verbatim, and full implementations (parse_vcf, calculate_tmb, NMF, DDR network) are inlined that duplicate the scripts/ bundle. Mostly efficient but could be tightened, which fits anchor 3 rather than the minor-trimming of 4.

3 / 5

Actionability

Concrete, largely executable code throughout — parse_vcf with quality filters, the Mutect2/CNVkit subprocess wrappers with error handling, the NMF metagene and TMB functions. Minor gaps keep it below fully copy-paste-ready: Workflow 4 uses undefined placeholders (PATHWAY_GENES, DRIVER_GENE, clin.GROUP), estimate_purity_ploidy is self-admittedly a "Rough heuristic", and external tools (GATK, SnpEff, CNVkit) are assumed installed with only a comment.

4 / 5

Workflow Clarity

Workflows 1–4 are clearly numbered and sequenced, subprocess calls surface errors (raise RuntimeError with Mutect2 stderr, check=True), and the Troubleshooting section gives problem/solution recovery guidance. Not 5 because there are no explicit validate-then-proceed checkpoints — e.g., the CNVkit pipeline never verifies intermediate outputs (tumor.cnr, reference.cnn) before the next step — placing it at clear sequence with minor validation gaps.

4 / 5

Progressive Disclosure

Section structure is good (Quick Start, Core Capabilities, Typical Workflows, Best Practices, Troubleshooting, Resources), but ~500 lines of implementation code are inlined in SKILL.md while a scripts/ bundle (calculate_tmb.py, ddr_network.py, nmf_metagenes.py, parse_vcf.py — ~2,000 lines covering the same capabilities) exists and is never referenced anywhere in the body. Scored against the actual bundle: references are absent, not merely unclear, which rules out 4; the genuine in-file structure rules out 2.

3 / 5

Total

14

/

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, well-scoped description that enumerates the skill's concrete capabilities and explicitly disambiguates the closest sibling skills. Its main weakness is the missing "Use when..." trigger clause, which caps completeness and leaves trigger-term coverage short of natural synonyms like VCF, MAF, and TMB.

Suggestions

Add an explicit trigger clause, e.g. "Use when analyzing tumor/normal sequencing data, somatic VCFs, or cohort mutation tables (MAF/cBioPortal format), or when estimating tumor purity, copy number, or mutational burden."

Include the natural keywords users actually say — "VCF", "MAF", "tumor mutational burden"/"TMB", "variant calling" — since TMB calculation is a core capability in the body but invisible in the description.

Keep the sibling-skill routing sentences but move them after the trigger clause so the description first states when this skill applies.

DimensionReasoningScore

Specificity

The description enumerates six concrete capabilities — "Somatic mutation detection and annotation, structural variation characterization, copy number analysis, tumor purity/ploidy estimation, NMF metagene extraction, and DNA damage response network analysis" — matching the anchor for multiple specific concrete actions with comprehensive coverage. Only the opener "Computational cancer genomics workflows" is generic, which is not enough to drop to 4.

5 / 5

Completeness

The "what" is explicit and concrete, but there is no "Use when..." clause or equivalent trigger guidance for this skill — the closing sentences ("For cancer mutation databases use cosmic-database; for variant clinical significance use clinvar-database") route users to sibling skills rather than stating when to invoke this one, so the "when" is only weakly implied. Per the judging guideline, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good coverage of natural domain terms ("somatic mutation", "copy number", "tumor purity/ploidy", "structural variation"), but common variations users would say are missing: "VCF", "MAF", "variant calling", and notably "tumor mutational burden"/"TMB", which is a full capability in the body yet absent from the description. Fits the anchor for good keyword coverage with a few natural terms missing, below the comprehensive synonym/extension coverage of 5.

4 / 5

Distinctiveness Conflict Risk

A clear cancer-genomics niche with explicit disambiguation from the two closest sibling skills (cosmic-database, clinvar-database). Minor overlap risk remains with general genomics or variant-annotation skills because no trigger context distinguishes this skill from them, which keeps it below the minimal-conflict anchor of 5.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

synthetic-sciences/openscience

Path

backend/cli/skills/biology/cancer-genomics-analysis/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.