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.

64

Quality

76%

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

85%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 content is highly actionable with executable commands and a clearly sequenced, validated workflow including the install/lock feedback loops the rubric rewards; the only weakness is moderate verbosity in the command and output-artifact catalogs.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the repeated command catalogs and enumerated output-artifact filenames (e.g. the plan/setup-plan/inventory/lock paragraphs) could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready bash invocations with concrete flags, pipeline names, and output paths rather than pseudocode or vague direction.

3 / 3

Workflow Clarity

The numbered Existence Check Order gives an explicit sequence with gating checkpoints, and install/lock operations include feedback loops (install plan before install, explicit approval gate, verify-lock drift report before reruns).

3 / 3

Progressive Disclosure

No bundle files are present, so navigation depth is not a factor; the body is cleanly sectioned (Existence Check Order, Script, Install Strategy, Report) with no nested references, satisfying the simple-skill allowance.

3 / 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 distinct within the NGS niche, but lacks an explicit 'Use when...' trigger clause and broad coverage of natural user phrasings, capping completeness and trigger quality at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when planning or validating an NGS/sequencing run, or before installing bioinformatics tools and databases.'

Broaden natural trigger terms to include common user phrasings like 'bioinformatics pipeline', 'conda/mamba environment check', or 'reference genome/database readiness'.

Keep the third-person action voice but pair it with the 'Use when...' form so both 'what' and 'when' are explicit.

DimensionReasoningScore

Specificity

Names concrete gating actions ('Check whether public NGS tools and packages already exist before downloading, installing, or running') tied to a specific domain, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

The 'what' is explicit, but the 'when' is only implied via the 'before...' precondition with no 'Use when...' clause, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

Relevant domain keywords ('NGS tools and packages', 'sequencing pipeline', 'downloading, installing') are present but common phrasing variations are missing and there is no explicit trigger clause listing user-facing terms.

2 / 3

Distinctiveness Conflict Risk

The NGS/sequencing-pipeline niche is narrow and the triggers are domain-specific, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.