CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

molecular-review-workflow

Generates academic reviews for molecules in diseases using PubMed research. Invoke when user needs biomedical literature review with Vancouver citation format.

Quality

65%

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/Academic Writing/molecular-review-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 skill's core content (inputs, five-step PubMed workflow, Vancouver citation quality rules, NCBI credentials) is sound, but it is buried in ~130 lines of generic boilerplate with duplicated and conflicting validation sections, and every reference to the implementing scripts points at files absent from the bundle. The body reads as padded template output rather than lean, executable guidance.

Suggestions

Cut the generic boilerplate sections (When to Use, Key Features, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Required Inputs, Deterministic Output Rules, Completion Checklist) — they restate what Claude already knows and duplicate each other; keep only the skill-specific Inputs, Workflow Process, Quality Rules, and Usage sections.

Merge the two conflicting validation sections ("Validation Shortcut" running `scripts/validate_skill.py --help` and "Quick Validation" running `python scripts/pubmed_api.py --help`) into one canonical pre-flight check, and include the concrete end-to-end invocation instead of the vague "Then invoke the skill with disease and molecule parameters".

Fix broken references: `scripts/pubmed_api.py`, `scripts/validate_skill.py`, and the `cd "20260316/scientific-skills/Academic Writing/molecular-review-workflow"` path do not exist in this bundle — either ship the scripts or replace the references with inline, self-contained commands; also correct "See `## Usage` above" in Example Usage, since the Usage section appears later in the file.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with several padded boilerplate sections that restate what Claude already knows: "Validate the request against the skill boundary", "Keep the output safe, reproducible", a "Key Features" section that only re-quotes the description, and duplicated generic checklists ("Recommended Workflow", "Output Contract", "Validation and Safety Rules", "Completion Checklist"). It avoids the severely-verbose score-1 pattern of explaining basic external concepts, but the padding is substantial.

2 / 5

Actionability

Some concrete guidance exists (NCBI env-var exports, `python scripts/pubmed_api.py --help`, required inputs disease/molecule, explicit Vancouver citation rules), but there is no runnable end-to-end example, "Then invoke the skill with disease and molecule parameters" gives no actual invocation, and the referenced scripts (`scripts/pubmed_api.py`, `scripts/validate_skill.py`) do not exist in the bundle, so the documented commands are not executable as shipped. This lands at concrete-but-incomplete rather than the mostly-executable guidance of a 4.

3 / 5

Workflow Clarity

A clear 5-step sequence is listed (Input Translation, Search Term Generation, PubMed Search, Result Processing, Review Generation), but validation is scattered and contradictory: "Validation Shortcut" runs `scripts/validate_skill.py --help` while "Quick Validation" runs `python scripts/pubmed_api.py --help`, with no concrete error-recovery loop, and actual execution is delegated to scripts missing from the bundle. Checkpoints exist but are duplicated and implicit, matching the steps-listed-but-checkpoints-missing anchor rather than the clean sequence of a 4.

3 / 5

Progressive Disclosure

The bundle contains no scripts/, references/, or assets/ directories, yet the body points to `scripts/pubmed_api.py`, `scripts/validate_skill.py`, "1 additional script(s)", and a `cd "20260316/scientific-skills/..."` path — none of which exist, so navigation to the real implementation is impossible. All content is inlined monolithically in SKILL.md with generic filler that belongs in no file, matching the minimal-structure/broken-references anchor of 2.

2 / 5

Total

10

/

20

Passed

Description

78%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 well-formed: third person, concrete about what the skill does, and includes an explicit when-to-invoke clause with natural trigger phrases. Its weaknesses are modest missing synonym coverage and slight trigger breadth that could overlap general literature-review requests.

DimensionReasoningScore

Specificity

"Generates academic reviews" plus "using PubMed research" names the domain with 1-2 concrete actions, but the description does not list several discrete capabilities (searching, term generation, citation assembly). This matches the anchor for naming a domain and 1-2 concrete actions without comprehensive coverage; it is more concrete than the score-2 anchor's minimal generic action, and less comprehensive than the multi-action lists at scores 4-5.

3 / 5

Completeness

It explicitly answers both "what" ("Generates academic reviews for molecules in diseases using PubMed research") and "when" ("Invoke when user needs biomedical literature review with Vancouver citation format") with a concrete trigger phrase. This mirrors the top anchor; the when-clause is explicit and specific, not merely present with room for improvement as at score 4.

5 / 5

Trigger Term Quality

Natural user phrasing is present: "PubMed", "biomedical literature review", "academic reviews", "Vancouver citation format", "molecules", "diseases". A few natural synonyms are missing (e.g., "systematic review", "research summary", "citations"), so it sits at good coverage with minor gaps rather than the comprehensive synonym-level coverage of a 5, and well above the sparse keyword sets of 3.

4 / 5

Distinctiveness Conflict Risk

The molecule-in-disease review niche with Vancouver citations is mostly distinct from other skills. Minor overlap risk remains because the trigger "user needs biomedical literature review" could fire for general (non-molecule/disease) literature review requests, so it is not the fully conflict-free clear niche of a 5.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 7 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/molecular-review-workflow/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.