CtrlK
BlogDocsLog inGet started
Tessl Logo

medical-research-gap-to-study-planner

Converts an audited medical research gap into a complete, structured, gap-traceable study design. Always use this skill whenever a user already has one or more candidate research gaps and wants to transform them into an executable biomedical research plan rather than re-run broad topic ideation. Covers six gap-to-design patterns (evidence-completion, mechanism-resolution, cell-state/context-mapping, translation-bridge, causality-upgrade, population/stage-specific) and always outputs one recommended primary protocol, a gap-to-design dependency map, step-by-step workflow, figure plan, validation strategy, minimal executable version, publication upgrade path, and verified design-support literature rules. Never fabricate references. Preserve claim-evidence discipline and do not replace a topic-specific gap with a generic workflow.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 well-structured, actionable instruction-only skill with excellent workflow sequencing, validation checkpoints, and clean progressive disclosure into verified reference files. Its main weakness is conciseness: the Hard Rules and "What This Skill Should Not Do" sections substantially duplicate content already present in the execution steps.

Suggestions

Consolidate the 13 Hard Rules into the steps that already state them (e.g., merge Rule 11 into Step 7, Rule 8 into Step 3.5, Rule 3 into Step 4), or replace the Hard Rules list with a short cross-reference rather than restating each rule.

Merge "What This Skill Should Not Do" into the existing Input Validation out-of-scope section and Hard Rules, since it largely reiterates both; keep only items that add genuinely new anti-patterns.

Tighten Step 6's section A-J descriptions, which repeat scope concepts already covered in Steps 1-5, to a one-line template per section.

DimensionReasoningScore

Conciseness

Mostly directive and free of basic-concept over-explanation, but contains substantial structural redundancy: the 13 Hard Rules restate guidance already in the steps (e.g., DESeq2/limma in Step 7 and Rule 11; never-fabricate in Step 3.5 and Rule 8; traceability in Step 4 and Rule 3) and "What This Skill Should Not Do" largely reiterates the Hard Rules and out-of-scope section.

3 / 5

Actionability

Provides concrete, actionable guidance for an instruction-only skill: a 7-step ordered workflow, a pattern-selection table with explicit "when to use" criteria, specific method rules (count data → DESeq2, non-count normalized → limma), defined output sections A-J, and numeric retrieval targets (2-4 gap-background, 1-2 method refs). Minor execution detail (8-field template, module library) is deferred to references rather than fully specified inline.

4 / 5

Workflow Clarity

Clear ordered 7-step sequence ("always run in order") with explicit mandatory checkpoints (Step 3.5, Step 4, Step 7), a dependency-check checklist in Step 4, and a feedback loop ("If any inconsistency is found, revise the plan before outputting"). This is not a destructive/batch skill, so the validation cap does not apply.

5 / 5

Progressive Disclosure

Body serves as a well-organized overview that splits detail into 9 real one-level-deep reference files, each clearly signaled with an arrow marker (e.g., "→ Detailed pattern logic: [references/gap-to-design-patterns.md]"). All referenced paths verified to exist; navigation is easy and nothing is nested beyond one level.

5 / 5

Total

17

/

20

Passed

Description

92%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 highly specific, complete, and distinct, written in correct third-person voice with both a clear what and an explicit when clause. Its only weakness is slightly limited trigger-term synonym coverage for a specialized domain.

DimensionReasoningScore

Specificity

Lists multiple concrete outputs ("one recommended primary protocol, a gap-to-design dependency map, step-by-step workflow, figure plan, validation strategy, minimal executable version, publication upgrade path") and names six specific design patterns, giving comprehensive coverage of concrete actions rather than vague language.

5 / 5

Completeness

Explicitly answers both what ("Converts an audited medical research gap into a complete, structured, gap-traceable study design") and when ("Always use this skill whenever a user already has one or more candidate research gaps and wants to transform them into an executable biomedical research plan rather than re-run broad topic ideation") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good domain keyword coverage ("candidate research gaps", "study design", "biomedical research plan", "protocol", "topic ideation") with natural phrasings, but limited synonyms and no file-extension-style triggers; a few common variations a user might say are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (audited gap → study design) and explicitly differentiates from adjacent work ("rather than re-run broad topic ideation", "do not replace a topic-specific gap with a generic workflow"), minimizing conflict with broad research-planning skills.

5 / 5

Total

19

/

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.

Validation15 / 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
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.