CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

drug-repurposing-study-planner

Design evidence-discovery and validation workflows for drug repurposing studies by integrating disease mechanisms, drug-target logic, expression reversal, real-world evidence, and validation routes into a closed-loop study blueprint.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./awesome-med-research-skills/Protocol Design/drug-repurposing-study-planner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 instruction skill: the execution logic, mandatory output structure, and hard rules give Claude a precise, actionable planning procedure, and the 10 reference modules are real and clearly signaled. The main costs are redundancy — boundary rules repeated across three sections and duplicated in reference files — and the lack of a worked example or explicit feedback loop for route failure.

Suggestions

Consolidate the overlapping boundary content in 'Important Distinctions', 'Hard Rules', and 'What This Skill Should Not Do' into one section and delegate detail to references/10-hard-rules.md, keeping only a one-line pointer inline.

Replace the duplicated Mandatory Output Structure / Formatting Expectations detail with a brief summary plus a pointer to references/09-output-section-rules.md, which already restates these rules.

Add a compact worked mini-example (one disease, one route, a three-layer evidence chain) to make the A–L output structure concrete, and add an explicit feedback loop in Step 3 or Step 8 for when evidence weakens and the primary route must be reconsidered.

DimensionReasoningScore

Conciseness

The body is mostly tight, decision-oriented bullets with no filler prose, but boundary rules repeat across 'Important Distinctions', 'Hard Rules', and 'What This Skill Should Not Do' (e.g., 'Never collapse these layers into one conclusion' vs. 'Never collapse disease association, mechanistic plausibility, and therapeutic effect into one sentence'), and the Hard Rules section substantially duplicates references/10-hard-rules.md. This matches anchor 3 — mostly efficient but could be tightened — rather than anchor 4, where only minor instances of over-explanation would remain.

3 / 5

Actionability

For an instruction-only skill the guidance is concrete and executable: an 8-step execution logic with worked selection heuristics ('If the user starts from a pathway or target, prefer a target/mechanism-led route'), an explicit DESeq2/limma decision rule ('count data → DESeq2 (recommended default); non-count normalized data → limma'), and a mandatory A–L output structure. It sits below anchor 5 only because no worked mini-example of a finished blueprint is provided to anchor the output format.

4 / 5

Workflow Clarity

The 8-step sequence is clearly ordered, opens with input validation, marks each evidence layer as necessary/recommended/optional, and closes with a risk-audit step and go/no-go gates — most checkpoints are present. It falls short of anchor 5 because there is no explicit feedback loop for error recovery, e.g., instructions for revisiting route selection when the primary route weakens; it is above anchor 3 because checkpoints like Step 8's fallback review are explicit rather than implicit.

4 / 5

Progressive Disclosure

All 10 referenced files exist in references/, are one level deep, and each is clearly signaled with a specific 'Use to...' purpose annotation — good structure per anchor 4. It does not reach anchor 5 because sizable content inlined in SKILL.md (Hard Rules, Mandatory Output Structure, Formatting Expectations) duplicates the corresponding reference modules, which is more than a minor placement gap; references are clearly signaled, keeping it above anchor 3.

4 / 5

Total

15

/

20

Passed

Description

70%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 specific, domain-grounded description that clearly states what the skill does and is well differentiated from neighboring skills. Its main weakness is the complete absence of 'when to use it' trigger guidance, which both caps completeness and slightly limits trigger discoverability.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to design or plan a drug repurposing study, build a repurposing evidence route, or connect disease omics to candidate drugs for repositioning.'

Include common synonyms such as 'drug repositioning' or 'repurpose approved drugs' so users' natural phrasings match the description.

State the boundary in one clause (e.g. 'for study design, not clinical prescribing advice') to further sharpen distinctiveness from protocol-writing and clinical skills.

DimensionReasoningScore

Specificity

The description gives one concrete action ('Design evidence-discovery and validation workflows for drug repurposing studies') plus five named evidence components ('disease mechanisms, drug-target logic, expression reversal, real-world evidence, and validation routes'), which is several specific elements with minor coverage gaps. It falls below anchor 5 because it describes a single design action with integrated inputs rather than multiple distinct concrete actions, and above anchor 3 because the components enumerated are concrete rather than generic.

4 / 5

Completeness

The 'what' is clear and concrete (designing evidence-discovery and validation workflows into a closed-loop study blueprint), but there is no 'Use when...' clause or any equivalent explicit trigger guidance for when to invoke the skill. Per the judging guideline, a missing trigger clause caps completeness at 3; the description is not vague enough to fall to anchor 2 or rise to anchor 4.

3 / 5

Trigger Term Quality

Natural user phrases like 'drug repurposing', 'repurposing studies', 'real-world evidence', and 'validation' are present, giving good keyword coverage. A few natural terms are missing — e.g., the common synonym 'drug repositioning' and phrasings like 'repurpose approved drugs' — so it does not reach anchor 5's comprehensive synonym coverage, while clearly exceeding anchor 3's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — designing drug repurposing study blueprints — with distinct triggers ('drug repurposing', 'expression reversal', 'real-world evidence') unlikely to fire for generic document, coding, or protocol-writing skills. It matches anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

16

/

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/Protocol Design/drug-repurposing-study-planner/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.