CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reagent-substitute-scout

Find validated alternative reagents based on literature citation data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/reagent-substitute-scout/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers genuinely actionable material — runnable commands, flags, config, and a disciplined workflow with fallback handling — but it is buried in heavy boilerplate and duplicated, circularly-referenced sections that inflate token cost. Splitting detail into references and cutting meta-checklists would raise both conciseness and progressive disclosure.

Suggestions

Remove the circular cross-reference sections ("See `## Features` above", "See `## Usage` above", "See `## Workflow` above") that point to content placed later in the same file, and merge the duplicated When-to-Use/Features/Usage material into single sections.

Move the full configuration schema, output-format examples, and scoring algorithm into files under references/, keeping SKILL.md a lean overview with clearly signaled links as done for audit-reference.md.

Cut boilerplate that adds tokens without guiding execution — the unchecked Security Checklist, Risk Assessment table, Lifecycle Status, Version History, and Evaluation Criteria sections — or collapse them into the existing audit reference file.

DimensionReasoningScore

Conciseness

The ~360-line body is noticeably padded: circular self-references ("See `## Features` above" placed before that section, "See `## Usage` above"), duplicated workflow material, and boilerplate sections (Risk Assessment, unchecked Security Checklist, Lifecycle Status with review dates, Version History). It avoids explaining concepts Claude already knows, so it sits above anchor 1 but clearly below the midpoint.

2 / 5

Actionability

Commands are concrete and mostly executable — `python -m py_compile scripts/main.py`, `python scripts/main.py --reagent "TRIzol Reagent" --limit 10`, a full config JSON, and an explicit scoring formula. Minor gaps keep it below anchor 5: inconsistent paths (`skills/reagent-substitute-scout/...` vs a `20260318/scientific-skills/...` cd target) and references to files not in the bundle (`requirements.txt`, `config.example.json`).

4 / 5

Workflow Clarity

The Workflow section gives a clear 5-step sequence with checkpoints: confirm inputs, validate scope and stop early if unsupported, a py_compile quick check before execution, a structured result template, and an explicit fallback path on failure. It is not a destructive or batch operation so the cap does not apply, but there is no validate→fix→retry feedback loop, keeping it at anchor 4.

4 / 5

Progressive Disclosure

One reference exists and is clearly signaled one level deep ([references/audit-reference.md](references/audit-reference.md), verified to exist), but the monolithic 360-line body inlines substantial content that belongs in separate files — full config schema, output format examples, scoring algorithm, security checklists, lifecycle metadata — matching 'content that should be separate is inline'.

3 / 5

Total

13

/

20

Passed

Description

53%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 specific to its domain and clearly states what the skill does, but it reads as a bare capability statement: no 'when to use' trigger, no synonyms for the request phrasing users would naturally employ. Adding an explicit trigger clause and terms like 'substitute'/'replacement'/'discontinued reagent' would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when a reagent is discontinued or out of stock and the user needs a validated substitute or replacement reagent."

Include the natural synonyms users would say — substitute, replacement, out of stock, discontinued — in the description text.

Enumerate the concrete actions (similarity matching, validation scoring, report generation) rather than the single 'find' action.

DimensionReasoningScore

Specificity

"Find validated alternative reagents based on literature citation data" names the domain and one concrete action, matching the '1-2 concrete actions, not comprehensive' anchor; it omits the skill's other capabilities (similarity matching, scoring, report generation) so it does not reach anchor 4.

3 / 5

Completeness

The description has a clear 'what' but no 'Use when...' clause or equivalent trigger guidance; per the judging guidelines a missing explicit trigger caps completeness at 3, matching the anchor example of a capabilities-only description.

3 / 5

Trigger Term Quality

Terms like "reagent", "alternative reagents", and "literature citation data" are relevant, but the natural phrases a user would say — "substitute", "replacement", "discontinued", "out of stock" — are absent, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"validated alternative reagents based on literature citation data" carves a clear niche with distinct triggers, with only minor overlap risk against general literature-search skills, matching 'mostly distinct; minor overlap risk'.

4 / 5

Total

13

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/reagent-substitute-scout/SKILL.md

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.