CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ngs-bcl-to-fastq

Validate Illumina BCL run folders and sample sheets, plan demultiplexing, review index/UMI/lane choices, run BCL-to-FASTQ conversion, and interpret demux metrics while surfacing license/download boundaries.

65

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 dense, well-structured operational skill: executable commands, a genuine validation checklist, an explicit user-confirmation gate before a batch operation, and a post-run metrics gate. The main improvement opportunities are merging the overlapping input/validation lists, naming the concrete metrics artifacts to inspect, and moving deep detail (sample-sheet formats, metrics file layouts) into a reference file.

Suggestions

Merge 'Essential Inputs' and 'Validation Checklist' — index lengths, UMI layout, dual-index orientation, and lane handling are listed in both sections; a single checklist with the preflight command would cut ~10 lines of duplication.

In 'Metrics Review', name the concrete artifacts to inspect (e.g., the Demultiplex_Stats output, Reports directory, per-sample FASTQ filenames) so the review step is executable rather than a list of metric concepts.

Move sample-sheet format/version specifics and metrics-file layout details into a single one-level-deep reference file, keeping SKILL.md as the overview with a clearly signaled link.

DimensionReasoningScore

Conciseness

The body is lean, command-first, and assumes domain competence (e.g., no explanation of what demultiplexing is, terse boundary statement 'do not auto-download without explicit user approval'). It is not score 5 because the 'Essential Inputs' list and the 'Validation Checklist' partially duplicate each other (index lengths, UMI layout, dual-index orientation, lane handling appear in both) and could be merged.

4 / 5

Actionability

Concrete, executable commands throughout — the preflight invocation, `test -f` checks, the full runner invocation with flags, and the bcl-convert kickoff command. It is not score 5 because the Metrics Review section says what to inspect ('total clusters', 'top undetermined index sequences') without naming the actual artifacts to read (e.g., Demultiplex_Stats files, per-sample FASTQ paths), and no example metrics-file interpretation is given.

4 / 5

Workflow Clarity

A clear sequence (confirm inputs → preflight → validation checklist → user-confirmed kickoff → execution → metrics review → downstream gate) with an explicit Validation Checklist section, a preflight validation step, an explicit confirmation gate ('run conversion only after the user confirms', 'Add --execute only when conversion is requested'), and a post-run verification stage. This matches the 'explicit validation steps... checklists for complex processes' anchor; the batch-operation validation cap at 3 does not apply since validation is thorough.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the body is a well-sectioned ~85-line overview — appropriate for a single-file skill. It is not score 5 because the body invokes plugin scripts ('plugins/ngs-analysis/scripts/ngs_preflight.py', 'run_bcl_to_fastq.py') that are not part of this skill bundle, and detail like sample-sheet format specifics or metrics-file layouts would justify a one-level-deep reference file rather than inline enumeration.

4 / 5

Total

17

/

20

Passed

Description

75%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, information-dense description with excellent specificity and near-zero conflict risk, written in third person. Its only real defect is the absence of an explicit 'Use when...' trigger clause, which caps completeness and leaves natural tool-name synonyms (bcl-convert, bcl2fastq) unused.

Suggestions

Append an explicit trigger clause such as: 'Use when the input is an Illumina run folder (BCL files, RunInfo.xml) or the user asks to demultiplex, run bcl-convert/bcl2fastq, or convert BCL to FASTQ.'

Add the natural tool-name synonyms users actually say — 'bcl-convert', 'bcl2fastq', 'demux' — to improve trigger-term coverage and distinguish this from generic FASTQ/QC skills.

Optionally name a concrete file extension or artifact (e.g., 'SampleSheet.csv', 'Demultiplex_Stats') so file-oriented requests match the description.

DimensionReasoningScore

Specificity

The description lists multiple concrete, comprehensive actions covering the full pipeline — 'Validate Illumina BCL run folders and sample sheets', 'plan demultiplexing', 'review index/UMI/lane choices', 'run BCL-to-FASTQ conversion', 'interpret demux metrics' — plus a boundary clause. This matches the comprehensive-coverage anchor; it is not score 4 because there are no meaningful gaps in the action inventory.

5 / 5

Completeness

The 'what' is clearly and comprehensively stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description; the 'when' is only weakly implied by the domain nouns. The judging guideline explicitly caps completeness at 3 for a missing 'Use when' clause, so this cannot be 4 even though the 'what' is excellent.

3 / 5

Trigger Term Quality

Good natural keyword coverage — 'Illumina', 'BCL run folders', 'demultiplexing', 'sample sheets', 'demux metrics' — but common user synonyms and tool names are missing: users would naturally say 'bcl-convert', 'bcl2fastq', or '.fastq'. Not score 5 because the anchor requires synonyms and file extensions, which are absent; not score 3 because domain keywords are well beyond just 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Illumina BCL demultiplexing) with distinct, domain-specific triggers; it would not plausibly fire for any other skill. Matches the 'clear niche with distinct triggers; minimal conflict risk' anchor and is clearly not the 'minor overlap risk' anchor at 4.

5 / 5

Total

17

/

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-bcl-to-fastq/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.