CtrlK
BlogDocsLog inGet started
Tessl Logo

research-router-skill

Route broad or ambiguous life-sciences research requests to the right skills, normalize core entities, optionally parallelize independent evidence gathering with subagents when available, and synthesize a concise evidence-backed answer. Use when a user asks a general life-sciences question that could span multiple sources or analysis types.

72

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 is a lean, highly actionable orchestration guide: concrete lane taxonomy, entity-to-skill mappings, ready-made skill sets per task type, and a structured output contract. It loses a point only on workflow_clarity (no explicit feedback loop) and progressive_disclosure (single inline file with no reference split).

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of what genes, diseases, or pathways are, no padded prose; every section (lane taxonomy, entity→skill maps, subagent guidance, output contract) earns its place with scannable lists.

5 / 5

Actionability

For an instruction-only orchestration skill the guidance is concrete and specific: named downstream skills per entity type, ready-made skill sets per task type (e.g. "clinvar-variation-skill, gnomad-graphql-skill, ensembl-skill" for variant interpretation), bounded subagent objectives, and a structured output contract covering common cases.

5 / 5

Workflow Clarity

A clear 5-step sequence (understand → normalize → select → gather → synthesize) is present with one explicit gate ("Do not start broad evidence collection until the important entities are stable"), but there is no validate-then-retry feedback loop, so it stops short of the score-5 anchor; not capped at 3 because routing is not a destructive or batch operation.

4 / 5

Progressive Disclosure

No bundle files exist and the body is well-organized into clearly headed sections with no deep nesting or buried references, but it is a single self-contained ~100-line file (over the 50-line simple-skill threshold) with inline skill catalogs that could arguably live in a reference, leaving minor organization gaps rather than the clean file-split structure of the score-5 anchor.

4 / 5

Total

18

/

20

Passed

Description

88%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 strong: it states four concrete actions, gives an explicit "Use when" trigger, and carves a clear broad-vs-narrow niche. The only soft spot is trigger-term coverage, which stays at the domain-generic level and omits the entity-specific synonyms that live in the body.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Route ... requests to the right skills", "normalize core entities", "parallelize independent evidence gathering with subagents", and "synthesize a concise evidence-backed answer" — giving comprehensive coverage of what the router does, matching the score-5 anchor of multiple specific concrete actions.

5 / 5

Completeness

Explicitly answers both "what" (route, normalize, parallelize, synthesize) and "when" ("Use when a user asks a general life-sciences question that could span multiple sources or analysis types") with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Includes natural triggers like "general life-sciences question" and "span multiple sources or analysis types", which are above the generic single-keyword level, but it lacks the domain-specific synonyms (gene, disease, variant) that appear only in the body, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

The "broad or ambiguous" / "span multiple sources" framing carves a clear niche distinct from narrow single-source skills, but "general life-sciences question" still risks minor overlap with the many specific life-sciences skills it routes to, so it sits at mostly-distinct rather than minimal-conflict.

4 / 5

Total

18

/

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.