CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

78%

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 ./plugins/ngs-analysis/skills/ngs-analysis-router/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, highly actionable router skill with clean sequencing and sensible approval gating. Its main weakness is progressive disclosure: the body points to reference and script files that are absent from the skill bundle.

Suggestions

Ship references/intake-schema.json and references/pipeline-registry.json (or inline the essential fields) so the 'Read ... when forming the route' instruction is satisfiable.

Add an explicit preflight-failure recovery step (e.g. 'if --emit-install-plan reports missing tools, resolve and re-run') to close the workflow feedback loop.

Clarify that plugins/ngs-analysis/scripts/ngs_preflight.py lives outside the skill bundle, or bundle a local copy, to avoid a broken-path impression.

DimensionReasoningScore

Conciseness

Lean, list-driven body that assumes Claude's competence (no explanations of what FASTQ/BAM are) with copy-paste commands; only minor overlap between 'Start Here' and 'Intake Rules' keeps it from a 5.

4 / 5

Actionability

Provides fully executable, copy-paste-ready preflight commands with concrete flags (--pipeline, --emit-install-plan, --manager micromamba, --install-plan-outdir), specific file-glob inputs to look for, and an explicit enumerated routing table mapping assay types to leaf skills.

5 / 5

Workflow Clarity

Clear Start Here → Intake → Routing → Preflight → Output Contract sequence with an explicit approval gate (NGS_RUN_INSTALL_COMMANDS=1) and a canonical review artifact, but lacks an explicit preflight-fail/fix/retry feedback loop so it stops short of 5.

4 / 5

Progressive Disclosure

Sections are well-organized and references are clearly signaled ('Read references/intake-schema.json and references/pipeline-registry.json'), but no references/, scripts/, or assets/ directories exist in the bundle, so those references are dangling and not navigable.

3 / 5

Total

16

/

20

Passed

Description

77%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, specific description with excellent trigger terms and a distinct NGS-router niche, undermined only by the absence of an explicit 'Use when' clause. Adding trigger guidance would lift completeness.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when a sequencing-analysis request is ambiguous or spans BCL/FASTQ/BAM/CRAM/count-matrix/VCF inputs and the right downstream pipeline is unclear.'

Consider stating the top-level-entrypoint role (already in the body) in the description to sharpen the 'when'.

DimensionReasoningScore

Specificity

Names the NGS domain and two concrete actions ('Route ... to the right public NGS analysis skill', 'ask only the missing assay-specific setup questions') plus an enumerated set of input types (BCL, FASTQ, BAM/CRAM, count-matrix, VCF), with only minor coverage gaps.

4 / 5

Completeness

It clearly states what the skill does (route requests, ask missing questions) but provides no explicit 'Use when...' trigger clause; the 'when' is only weakly implied by 'sequencing requests', so per the guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Comprehensive natural terms users actually say for NGS work — BCL, FASTQ, BAM/CRAM, VCF, count-matrix — including format synonyms, so a user requesting sequencing analysis would naturally hit these triggers.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche as an NGS analysis router with distinct format-specific triggers (BCL/FASTQ/BAM/CRAM/VCF/count-matrix), making conflict with unrelated skills minimal.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
openai/plugins
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.