CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

medical-research-gap-finder

Identifies real, evidence-audited, topic-specific research gaps in medical research by first retrieving and verifying literature from trusted sources, then mapping the current evidence landscape, rejecting pseudo-gaps, and converting only medium/high-confidence gaps into study-ready research opportunities. Always require real literature retrieval before formal gap claims. Never fabricate references, metadata, or findings.

Quality

78%

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 ./awesome-med-research-skills/Evidence Insight/medical-research-gap-finder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 well-structured, gate-heavy workflow with strong sequencing, validation checkpoints, and clean progressive disclosure to real reference files. Its weaknesses are redundancy across the Hard Rules / Should-Not-Do / Quality Standard sections and one unreferenced bundle file.

Suggestions

Merge the 'Hard Rules', 'What This Skill Should Not Do', and 'Quality Standard' sections into a single non-redundant rules block; most Hard Rules restate Steps 2–8 verbatim in spirit.

Reference references/workflow-step-template.md where appropriate (or remove it) so every bundled file is reachable from SKILL.md.

Add one worked example of a completed gap-map row (taxonomy type, audit basis, confidence, rejection rationale) to make the output contract fully concrete.

Drop the 'Sample Triggers' section or fold it into Input Validation — its examples duplicate the ones already listed there.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and is directive throughout, but it has noticeable redundancy: 'Hard Rules' 2–8 restate Steps 2–6, 'What This Skill Should Not Do' restates Hard Rules 3–5 and 9, 'Quality Standard' restates the output contract, and 'Sample Triggers' overlaps the Input Validation examples. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; a 2 would require padded filler sections, which are absent.

3 / 5

Actionability

Guidance is concrete for an instruction-only skill: a verbatim redirect script for out-of-scope requests, per-gap required fields ('what the literature already covers... confidence level'), a required output structure A–I, and named delegation to reference protocols at each step. Minor gaps remain — no worked example of one completed gap-table row or a concrete search-query template inline. Fits 'mostly executable guidance with minor gaps'; 5 would require example outputs covering common cases.

4 / 5

Workflow Clarity

'Execution — 8 Steps (always run in order)' gives a clear sequence with explicit checkpoints: retrieval-before-claims gating (Step 2), pseudo-gap rejection (Step 5), confidence gating where 'only medium- or high-confidence gaps may enter the final gap map' (Step 6), and a self-critical review with a fallback path 'if the top gap collapses after closer review' (Step 8). This matches the anchor with explicit validation steps, feedback loops, and checklist-like Hard Rules.

5 / 5

Progressive Disclosure

SKILL.md is an overview that delegates detail to one-level-deep, well-signaled references cited at the exact step where each applies (all four cited files exist in references/). However, references/workflow-step-template.md ships in the bundle but is never mentioned anywhere in the body — an orphan file that breaks navigation expectations. 'Good structure... minor organization gaps' fits; 5 requires fully clean, easy navigation.

4 / 5

Total

16

/

20

Passed

Description

75%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 strong, specific, third-person description that clearly communicates a multi-action capability in a distinct medical-research niche. Its main weakness is the absence of any 'Use when...' trigger clause, which caps completeness, and modest synonym coverage of natural trigger phrases.

Suggestions

Append a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user asks to find, identify, or map research gaps, evidence gaps, or unanswered questions in a medical topic.'

Add natural synonyms users would actually say — 'evidence gaps', 'unanswered questions', 'what's still unknown', 'publishable directions' — to broaden trigger matching.

Consider naming the primary retrieval sources (e.g., PubMed) to sharpen distinctiveness against general literature-review skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'retrieving and verifying literature', 'mapping the current evidence landscape', 'rejecting pseudo-gaps', 'converting only medium/high-confidence gaps into study-ready research opportunities' — giving comprehensive, third-person coverage of the skill's capabilities. It matches the anchor for comprehensive specific actions; a 4 would require minor gaps in coverage, which are not present.

5 / 5

Completeness

The 'what' is explicit and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'Always require real literature retrieval before formal gap claims' is a behavioral rule, not a usage trigger. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3; the description has a clear what with 'when' only weakly implied, exactly matching the 3 anchor.

3 / 5

Trigger Term Quality

Natural user phrases like 'research gaps in medical research' and 'evidence' are present, plus domain terms ('pseudo-gaps', 'literature'). However, common variations users would say — 'evidence gaps', 'unanswered questions', 'find gaps', 'future directions' — are missing. Good coverage with a few natural terms missing fits the 4 anchor; it is clearly above 3 (which requires only 'some relevant keywords') but below 5 (comprehensive synonyms).

4 / 5

Distinctiveness Conflict Risk

The niche is clear ('topic-specific research gaps in medical research' with evidence-audit framing) and the triggers are distinctive; a request phrased this way would not naturally route to a generic literature-summary or clinical-decision skill. This matches the 'clear niche with distinct triggers; minimal conflict risk' anchor; 4 would require noticeable overlap with a closely related skill, which is absent.

5 / 5

Total

17

/

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

awesome-med-research-skills/Evidence Insight/medical-research-gap-finder/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.