CtrlK
BlogDocsLog inGet started
Tessl Logo

building-genomics-pipelines

This skill should be used when the user asks to "build a genomics pipeline", "call variants", "analyze RNA-seq", "run ChIP-seq analysis", "annotate variants", "QC sequencing data", "detect CNVs", or when writing any bioinformatics pipeline code involving NGS data. Provides expert guidance on pipeline frameworks (Nextflow, Snakemake, WDL), alignment, variant calling, and production-ready nf-core workflows.

90

1.13x
Quality

92%

Does it follow best practices?

Impact

78%

1.13x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A concise, actionable overview with excellent progressive disclosure and real reference files. The main gap is workflow clarity: it gives principles and tool picks rather than an end-to-end sequenced pipeline with validation checkpoints.

Suggestions

Add a short ordered canonical pipeline (e.g., FASTQ → FastQC/MultiQC → align → mark-duplicates → call → annotate) with explicit PASS/FAIL validation gates between stages.

Include one concrete QC threshold example (read depth, mapping rate, contamination) so the 'set clear PASS/FAIL thresholds' principle becomes actionable.

Show a one-line resume/checkpointing command or flag, since reproducibility and resume are named as principles but not demonstrated.

DimensionReasoningScore

Conciseness

Lean, token-efficient body — terse opinionated defaults ('Use BWA-MEM2', 'prefer CRAM over BAM (30-50% smaller)') that assume Claude's competence and avoid explaining what FASTQ/BAM/VCF are beyond a one-line role label.

3 / 3

Actionability

Concrete executable guidance throughout: specific tool names per task, a runnable nf-core command with flags, and concrete file-format conventions (bgzip + tabix, .bai/.crai/.tbi/.csi indexing).

3 / 3

Workflow Clarity

Pipeline-design principles are listed and workflow types are routed to references, but there is no explicit sequenced pipeline procedure with validation checkpoints (e.g., FASTQ→QC→align→call→annotate with PASS/FAIL gates); the PASS/FAIL thresholds are mentioned as a principle but not wired into a step sequence.

2 / 3

Progressive Disclosure

Clear overview that splits detail into one-level-deep, well-signaled references (references/rnaseq.md, references/annotation.md, references/cnv.md), all of which exist; the nf-core table keeps the overview scannable.

3 / 3

Total

11

/

12

Passed

Description

100%

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, well-structured description: explicit trigger clauses, concrete actions, and a clearly bounded NGS/bioinformatics niche. It is slightly long but every clause earns its place.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and domains — 'build a genomics pipeline', 'call variants', 'annotate variants', 'QC sequencing data', 'detect CNVs' — plus specific frameworks (Nextflow, Snakemake, WDL) and tasks (alignment, variant calling).

3 / 3

Completeness

Explicitly states both what ('Provides expert guidance on pipeline frameworks... alignment, variant calling, and production-ready nf-core workflows') and when ('when the user asks to...', 'or when writing any bioinformatics pipeline code involving NGS data').

3 / 3

Trigger Term Quality

Quotes natural phrases a user would say verbatim ('build a genomics pipeline', 'analyze RNA-seq', 'call variants') with broad coverage of common NGS requests.

3 / 3

Distinctiveness Conflict Risk

Narrow bioinformatics/NGS niche with domain-specific triggers unlikely to fire for unrelated skills; the named tools and assays reinforce the distinct scope.

3 / 3

Total

12

/

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
provectus/awos-recruitment
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.