CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clinical-question-clarifier

Clarifies a vague clinical or biomedical research idea into a structured, bounded, searchable, researchable, and testable question. Always use this skill whenever a user has an early-stage clinical or research thought, an over-broad topic, an ill-defined evidence question, or an unclear problem statement that must be translated into a question framing suitable for literature retrieval, evidence synthesis, gap analysis, study design, or downstream protocol planning. Never jump straight to answering the substantive medical question unless the user explicitly asks for that. Focus first on question framing, boundary setting, and downstream-ready formulation.

Quality

81%

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

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, highly actionable instruction skill with a clear 8-step workflow, explicit guided-focusing feedback loops, and a real one-level-deep reference bundle. Its main weaknesses are meaningful redundancy across sections and a section-lettering mismatch between output-section-guidance.md and the body's mandatory A-K structure, which together cost it on conciseness and workflow clarity.

Suggestions

Deduplicate the body: remove the inline "Supported Question Types" list (it duplicates references/question-type-taxonomy.md), merge the Interactive Refinement Rule into the Guided Focusing Mode section, and collapse the Downstream Routing Standard into Step 8 / Section J — this alone would cut the body substantially.

Fix the section-lettering mismatch: references/output-section-guidance.md defines only Sections A-J with letters offset from the body's mandatory A-K structure (e.g., its Section D is framing rationale while the body's Section D is guided focusing). Realign it to A-K or switch both to unambiguous section names.

Add one worked example (a vague input mapped to a filled-in A-K output) to lift actionability from mostly-executable to copy-paste-ready, and trim abstract quality statements like "reveal the real question behind the vague prompt" in favor of concrete checks.

DimensionReasoningScore

Conciseness

The ~330-line body is mostly efficient and does not explain concepts Claude already knows, but contains notable redundancy that could be tightened: the question-type list is duplicated between the body's "Supported Question Types" and references/question-type-taxonomy.md; guided focusing is described three times (Guided Focusing Mode, Decision Logic Step 4, Interactive Refinement Rule); downstream routing appears in the Downstream Routing Standard, Step 8, and Section J; and the "do not answer the question" rule is restated four times. It is above a 2 because the padding is repetition rather than educational filler, but below a 4 because several sections restate one another.

3 / 5

Actionability

For an instruction-only skill the guidance is largely executable: a mandatory A-K output structure with per-section content requirements, an exact table header for Section F, a verbatim out-of-scope redirect template, explicit framework-to-question-type mappings, and concrete limits ("2-5 concise, high-yield narrowing questions", question ordering, stopping rules). It falls short of a 5 because there is no worked example showing a completed A-K output, and some guidance such as the Quality Standard ("reveal the real question behind the vague prompt") remains abstract.

4 / 5

Workflow Clarity

The 8-step Decision Logic is clearly sequenced with each step tied to a reference module, and the guided-focusing loop has explicit entry conditions, question ordering, and stop rules; out-of-scope input has a validate-and-stop redirect. However, references/output-section-guidance.md defines sections A-J whose lettering is offset from the body's A-K structure (its Section D covers framing rationale while the body's Section D is guided focusing questions), so the instruction to use that file "as the section-level formatting and content control standard for Sections A-K" is internally inconsistent — a real validation gap that keeps this below 5.

4 / 5

Progressive Disclosure

The bundle structure is genuinely good: all ten files referenced in the body exist in references/, are one level deep, and each is explicitly mapped to a specific output section with a "use when" signal. Two minor gaps hold it below 5: the question-type taxonomy content is duplicated inline in the body rather than left in its reference file, and output-section-guidance.md's misaligned A-J lettering breaks navigation for that one reference.

4 / 5

Total

15

/

20

Passed

Description

87%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 description that clearly states what the skill does and when to use it, with explicit trigger conditions and negative boundary guidance that sharply distinguishes it from adjacent literature-review or protocol skills. The only weakness is that the capability list leans on adjective-stacked variants of a single transformation and misses a few natural user phrasings.

DimensionReasoningScore

Specificity

The description names the domain and several concrete actions — "Clarifies a vague clinical or biomedical research idea into a structured, bounded, searchable, researchable, and testable question", "translated into a question framing suitable for literature retrieval, evidence synthesis, gap analysis, study design", "question framing, boundary setting, and downstream-ready formulation". It stops short of a 5 because these are largely adjectival variants of one transformation rather than a comprehensive list of distinct capabilities, and it is above a 3 because more than 1-2 concrete actions are named.

4 / 5

Completeness

It explicitly answers both questions: the 'what' ("Clarifies a vague clinical or biomedical research idea into a structured, bounded, searchable, researchable, and testable question") and the 'when' with concrete trigger phrases ("Always use this skill whenever a user has an early-stage clinical or research thought, an over-broad topic, an ill-defined evidence question, or an unclear problem statement"), plus explicit negative guidance ("Never jump straight to answering the substantive medical question unless the user explicitly asks for that").

5 / 5

Trigger Term Quality

Good natural keyword coverage: "early-stage clinical or research thought", "over-broad topic", "ill-defined evidence question", "unclear problem statement", "literature retrieval", "evidence synthesis", "gap analysis", "study design", "protocol planning". A 5 is withheld because common user phrasings like "narrow my topic", "too broad", "formulate a research question", or "PICO" are absent, though coverage clearly exceeds the 'some relevant keywords' level of a 3.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers: it explicitly separates question clarification from question answering ("Never jump straight to answering the substantive medical question"), from literature answers, and from protocol planning, distinguishing it from sibling evidence-review and protocol skills. Conflict risk is minimal.

5 / 5

Total

18

/

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/clinical-question-clarifier/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.