CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nfcore-scrnaseq-wrapper

Wrapper skill for running nf-core/scrnaseq 4.1.0 upstream single-cell RNA-seq preprocessing from FASTQ with strict preflight, reproducibility outputs, and downstream handoff to ClawBio scRNA skills.

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 ./skills/nfcore-scrnaseq-wrapper/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 excels at actionability and workflow clarity — commands are copy-paste executable, the seven-step pipeline is strictly ordered with structured error codes, fix hints, and validation at every checkpoint. Its weaknesses are token efficiency (heavy duplication and rationale-laden gotcha paragraphs across ~425 lines) and progressive disclosure (everything, including a 70-row flag reference, is inlined in a single monolithic file).

Suggestions

Move the full CLI flag table, the nf-core 4.1.0 compatibility policy, and the detailed gotchas into one-level-deep reference files (e.g. references/cli.md, references/compatibility.md, references/gotchas.md), keeping SKILL.md as a lean overview with pointers.

De-duplicate policy explanations that currently appear in multiple sections — igenomes_ignore (Algorithm, flag table, gotcha, Safety), remote inputs (Path Policy, Safety), and conda/CellRanger restrictions (Algorithm, gotcha, flags) — stating each rule once in its canonical section.

Tighten gotcha entries to the actionable rule plus the error code, trimming internal implementation rationale (zero-padding comparisons, subprocess timeout constants, sibling-wrapper parity notes) that an executing agent does not need.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: policy explanations are duplicated across sections (igenomes_ignore appears in Algorithm step 4, the flag table, a gotcha, and Safety; remote-input policy in both the Path Policy section and Safety; conda/CellRanger rules in three places), and several multi-hundred-word gotcha paragraphs carry internal implementation rationale (version-tuple zero-padding rationale, subprocess timeout constants, sibling-wrapper parity notes, upstream nf-schema warning forensics) that a executing agent does not need. While nothing explains generic concepts Claude already knows, several padded sections could be cut by half or more, matching anchor 2 rather than 3.

2 / 5

Actionability

The CLI Reference provides fully executable, copy-paste-ready commands covering the common cases (standard run, --check preflight, --demo, runner invocation, fasta+gtf, prebuilt index, RNA velocity, CMO multiplexing, air-gapped iGenomes mirror), plus a complete flag table with types, defaults, and preset-conditional requirements. This matches the anchor for fully executable guidance covering common cases.

5 / 5

Workflow Clarity

The workflow is a "strictly ordered 7-step pipeline" where "a failure at any step raises a structured SkillError with an error_code and a fix hint; no subsequent step runs" — explicit validation checkpoints (preflight gates before Nextflow, post-run required-output validation, checksum-verified --resume) with error-code/fix feedback loops for recovery, matching the top anchor.

5 / 5

Progressive Disclosure

The document is well-sectioned with clear headers, but it is monolithic: the ~70-row flag table, the compatibility policy, and roughly 150 lines of gotchas are all inlined content that clearly belongs in separate reference files, and no bundle files (references/, scripts/, assets/) exist. This matches anchor 3 (good structure, but content that should be separate is inline) rather than 4, since no content is split out at all.

3 / 5

Total

15

/

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.

The description is specific, correctly third-person, and clearly positions the skill in a well-defined niche (upstream FASTQ-to-h5ad preprocessing via a pinned nf-core pipeline). Its main weaknesses are the absence of any explicit "Use when..." trigger guidance and missing natural synonyms like scRNA, 10x, and h5ad that users would commonly say.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to run nf-core/scrnaseq, preprocess 10x Chromium FASTQs, or generate .h5ad from raw single-cell FASTQs" — this would raise completeness from 3 to 5.

Include natural synonyms users actually say — "scRNA", "10x", "h5ad", "single cell" — alongside "single-cell RNA-seq" to broaden trigger-term coverage.

Briefly state the boundary (e.g. "not for clustering or embedding analysis on existing .h5ad") to further reduce overlap risk with the downstream ClawBio scRNA skills.

DimensionReasoningScore

Specificity

Names the exact pipeline and version ("running nf-core/scrnaseq 4.1.0 upstream single-cell RNA-seq preprocessing from FASTQ") plus several concrete actions ("strict preflight", "reproducibility outputs", "downstream handoff to ClawBio scRNA skills"). It lists several specific actions rather than 1-2, but coverage is not fully comprehensive (presets, aligner choices, and output resolution are unmentioned), matching anchor 4 rather than 5.

4 / 5

Completeness

The "what" is clear and concrete (run nf-core/scrnaseq preprocessing from FASTQ with preflight, reproducibility, and handoff), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes natural terms users would say — "scrnaseq", "single-cell RNA-seq preprocessing", "FASTQ" — giving good keyword coverage, but misses common variations and synonyms such as "scRNA", "10x", "h5ad", and unhyphenated "single cell", so it falls short of anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

"upstream ... from FASTQ" combined with the pinned "nf-core/scrnaseq 4.1.0" establishes a clear niche distinct from downstream analysis skills, but without explicit when-guidance there is minor overlap risk with the closely related ClawBio scRNA skills it hands off to (scrna-orchestrator, scrna-embedding), matching anchor 4 rather than 5.

4 / 5

Total

15

/

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 (501 lines); consider splitting into references/ and linking

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

ClawBio/ClawBio

Path

skills/nfcore-scrnaseq-wrapper/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.