CtrlK
BlogDocsLog inGet started
Tessl Logo

ngs-runtime-env

Check whether public NGS tools and packages already exist before downloading, installing, or running a sequencing pipeline.

65

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-runtime-env/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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, command-driven skill body that is highly actionable, well-sequenced with approval and verification gates, and cleanly sectioned. Its main limitation is mild over-explanation in the per-command prose and the absence of external reference files that could offload the long reference-manager command catalog.

DimensionReasoningScore

Conciseness

The body is largely lean operational guidance and executable commands with no padding of concepts Claude already knows; the per-command 'Use X when...' paragraphs are functional rather than filler, with only minor over-explanation that could be trimmed, placing it just below the fully lean anchor.

4 / 5

Actionability

Copy-paste-ready executable commands are given throughout (ngs_preflight.py, ngs_reference_manager.py, run_nfcore_pipeline.py invocations) with specific flags and output paths covering the common cases, matching the fully-executable anchor.

5 / 5

Workflow Clarity

A clear 6-step 'Existence Check Order' sequence with explicit approval/validation gates ('Emit an install plan before installing', 'Install only when explicitly requested', the NGS_RUN_INSTALL_COMMANDS=1 guard, and verify-lock --fail-on-mismatch drift feedback) avoids the destructive/batch cap; not a 5 because not every workflow spells out an if-fails-then-fix-and-retry loop.

4 / 5

Progressive Disclosure

Well-organized section headers structure a single SKILL.md with one-level-deep, clearly signaled command catalogs and no nested references; no bundle files are provided so it scores on this inline structure, which is appropriate for a CLI-driven skill, with only minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

73%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 concise, third-person description that clearly states a single concrete capability and an explicit trigger context for an NGS-specific niche. It is stronger on distinctiveness and trigger terms than on action breadth, since it describes one gating action rather than a suite of operations.

DimensionReasoningScore

Specificity

Names the NGS domain and a concrete gating action ('Check whether public NGS tools and packages already exist'), but the skill's real capability is a single existence-check action rather than a list of several distinct actions, so it sits at the '1-2 concrete actions' anchor rather than the 'several specific actions' level above.

3 / 5

Completeness

The 'what' (check whether NGS tools/packages already exist) and an equivalent 'when' clause ('before downloading, installing, or running a sequencing pipeline') are both explicit, so it clears the missing-trigger cap; not a 5 because it lacks the canonical multi-phrase 'Use when...' trigger list.

4 / 5

Trigger Term Quality

Natural terms a bioinformatics user would say are present ('NGS tools', 'packages', 'sequencing pipeline', 'downloading, installing'), giving good keyword coverage with only minor synonyms missing (e.g. 'bioinformatics', specific formats like FASTQ).

4 / 5

Distinctiveness Conflict Risk

The NGS/sequencing-pipeline niche is highly specific with distinct triggers, making overlap with unrelated skills minimal.

5 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.