ngs-analysis-router

Route BCL, FASTQ, BAM/CRAM, count-matrix, or VCF sequencing requests to the right public NGS analysis skill and ask only the missing assay-specific setup questions.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/ngs-analysis/skills/ngs-analysis-router/SKILL.md

Quality

Content

92%Weight 40%Scale 1-3

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

The body is a lean, highly actionable routing guide with a clear sequenced workflow and strong validation guard rails; its only weakness is progressive disclosure, where referenced files are signaled but not actually present in the bundle.

Suggestions

Provide the missing references/intake-schema.json and references/pipeline-registry.json files so the signaled one-level-deep navigation is real, or remove the references and inline the essential fields.

If keeping the references, use explicit markdown links (e.g. [intake-schema.json](references/intake-schema.json)) to clearly signal the one-level-deep disclosure.

Dimension	Reasoning	Score
Conciseness	Lean, dense bullets and command blocks assume Claude's competence without explaining what FASTQ, VCF, or NGS are, so every token earns its place.	3 / 3
Actionability	Provides concrete, executable bash commands with exact flags and a specific routing table mapping inputs to named skills; the <pipeline_key> placeholder is a justified parameter, not pseudocode.	3 / 3
Workflow Clarity	Clear Start Here -> Intake -> Routing -> Preflight -> Output Contract sequence with explicit guard rails and validation artifacts (install_plan.json as canonical, NGS_RUN_INSTALL_COMMANDS=1, --install-missing --yes only on explicit approval).	3 / 3
Progressive Disclosure	Sections are well organized and two reference files are signaled one level deep, but references/intake-schema.json and references/pipeline-registry.json are referenced yet do not exist, so the navigation is broken rather than cleanly loadable.	2 / 3
	Total	11 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 and clearly niched to NGS request routing, but it omits an explicit 'Use when...' trigger clause, which caps completeness and leaves trigger-term coverage at a good-but-not-excellent level.

Suggestions

Add an explicit 'Use when...' trigger clause to the description, e.g. 'Use when a sequencing-analysis request is ambiguous or spans BCL, FASTQ, BAM/CRAM, count-matrix, or VCF inputs.' to satisfy the completeness rubric.

Broaden trigger terms beyond format names to natural phrasings users say (e.g. 'sequencing data', 'NGS pipeline', 'RNA-seq', 'variant calling') to raise trigger-term quality.

Dimension	Reasoning	Score
Specificity	Names multiple concrete input formats (BCL, FASTQ, BAM/CRAM, count-matrix, VCF) and two specific actions (route to the right skill, ask only the missing assay-specific setup questions), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly states what the skill does, but the description has no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 2 even though the 'when' is implied by the routing framing.	2 / 3
Trigger Term Quality	Covers relevant format keywords users would say but leans on technical format names rather than broad natural phrasings, and the description lacks an explicit trigger clause that broader natural variations would provide.	2 / 3
Distinctiveness Conflict Risk	Targets a clearly distinct NGS-routing niche defined by specific sequencing formats, making it unlikely to trigger for the wrong leaf analysis skill.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/ngs-analysis/skills/ngs-analysis-router/SKILL.md
Commit: 11c74d6

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.