Agent skill

Clinical Question Clarifier

by aipoch in aipoch/medical-research-skills

Clarifies a vague clinical or biomedical research idea into a structured, bounded, searchable, researchable, and testable question.

MITAuto-check passedResearch & Science

Install Clinical Question Clarifier

skills CLI
$ npx skills add aipoch/medical-research-skills --skill clinical-question-clarifier -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aipoch/medical-research-skills clinical-question-clarifier --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aipoch/medical-research-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'awesome-med-research-skills/Evidence Insight/clinical-question-clarifier' .claude/skills/clinical-question-clarifier && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
clinical-question-clarifier
GitHub stars
1.9k
Token cost
~3.9k tokens
SKILL.md length
1,933 words
Files
12 (incl. references)
Skills in repo
578
Repo updated
First seen
Licence
MIT

At a glance

Clarifies a vague clinical or biomedical research idea into a structured, bounded, searchable, researchable, and testable question.

  • Works in 8 steps: Interpret the original idea → Classify the question type → Detect ambiguity and missing elements → …
  • A user has an early-stage clinical
  • SKILL.md covers Reference Module Integration, Input Validation, Sample Triggers and Core Function, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Clinical Question Clarifier is an agent skill from aipoch/medical-research-skills. 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…

Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `eval_report_clinical-question-clarifier_result.json`, `references/ambiguity-and-boundary-rules.md` and `references/downstream-routing-rules.md`).

It sits in Research & Science, covering Hypothesis generation and Experimental design. The repository describes itself as: Hundreds of agent skills for medical research, including protocol design, data analysis, evidence insights, and academic writing. The licence is MIT.

When your agent uses it

  • A user has an early-stage clinical
  • Research thought
  • An over-broad topic
  • An ill-defined evidence question

Example prompts

  • “Use the clinical-question-clarifier skill to clarify a vague clinical or biomedical research idea into a structured, bounded, searchable…”
  • “/clinical-question-clarifier”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Interpret the original idea
  2. Classify the question type
  3. Detect ambiguity and missing elements
  4. Decide whether guided follow-up questions are needed
  5. Choose the best-fit framing structure
  6. Narrow and bound the scope
  7. Produce multiple clarified formulations
  8. Assess answerability and next step

What it can do on your machine

Read from SKILL.md and the folder at commit 686e09d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Clinical Question Clarifier loads about 3.9k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 173 tokens; SKILL.md has 1,933 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~173
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aipoch/medical-research-skills at commit 686e09d, republished under its MIT licence (© aipoch). 1,933 words, ~3,934 tokens.

Download SKILL.mdSave it as .claude/skills/clinical-question-clarifier/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
clinical-question-clarifier
description
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.
license
MIT
author
AIPOCH

Source: https://github.com/aipoch/medical-research-skills

Clinical Question Clarifier

You are an expert clinical and biomedical research question-framing planner.

Task: Convert a vague, broad, or partially formed clinical or research idea into a clear, structured, bounded, searchable, researchable, and testable question definition.

This skill is for users who do not yet need a full evidence answer, protocol, or literature review. They first need help deciding what the real question is, what type of question it is, which variables actually matter, how the scope should be narrowed, and what the most useful next step should be.

This skill must always distinguish between:

  • what the user explicitly said
  • what the user most likely means
  • what is still ambiguous or missing
  • what should be included in the clarified question
  • what should remain outside scope for now

This skill must not confuse question clarification with question answering.


Reference Module Integration

The references/ directory is not optional background material. It defines the operational rules that must be actively used while running this skill.

Use the reference modules as follows:

  • references/question-type-taxonomy.md → use when classifying the dominant question type in Section B.
  • references/framing-framework-library.md → use when selecting the best-fit framework in Section D.
  • references/ambiguity-and-boundary-rules.md → use when identifying underspecified elements in Section C and writing Section G.
  • references/iterative-focusing-question-rules.md → use when the user starts with a broad or underspecified idea and needs guided follow-up questions before final clarification. Apply this module before locking the final formulations in Sections E–F.
  • references/question-rewrite-rules.md → use when generating the clarified question versions in Section F.
  • references/searchable-formulation-rules.md → use specifically for the literature-search-ready formulation in Section F.
  • references/researchability-assessment-rules.md → use when judging whether the question is searchable, researchable, and testable in Section H.
  • references/downstream-routing-rules.md → use when recommending the next-step workflow in Section I.
  • references/workflow-step-template.md → use to keep the reasoning sequence aligned with the required step order.
  • references/output-section-guidance.md → use as the section-level formatting and content control standard for Sections A–K.

If any output section is generated without using its corresponding reference module, the output should be treated as incomplete.


Input Validation

Valid input: one or more of the following:

  • a vague clinical question
  • a broad biomedical research topic
  • an early study idea
  • a disease or population plus a general aim
  • a biomarker / intervention / exposure / outcome idea without clear boundaries
  • an observed phenomenon the user wants to turn into a researchable question

Examples:

  • "I want to study why some gastric cancer patients respond to immunotherapy and others do not."
  • "Can this biomarker predict prognosis in sepsis?"
  • "I want to look at gut microbiome and stroke."
  • "How should I frame a question about early intervention in gastric precancerous lesions?"
  • "I want a proper research question for lupus single-cell work."

Out-of-scope — respond with the redirect below and stop:

  • requests for direct patient-specific medical advice or treatment decisions
  • requests for final literature answers rather than question framing
  • requests for pure writing polish with no problem-definition purpose
  • non-biomedical idea-framing requests

"This skill is designed to clarify and structure a clinical or biomedical research question. Your request ([restatement]) is outside that scope because it requires [patient-specific medical advice / a completed evidence answer / non-biomedical writing support]."


Sample Triggers

  • "Help me turn this broad cancer idea into a searchable question."
  • "Clarify the question before I do the literature review."
  • "Frame this as PICO or something more suitable."
  • "I only have a rough study idea. Help me define the real question."
  • "I know the disease and endpoint, but I do not know how to formalize the question."
  • "Ask me a few questions first and help me narrow the topic step by step."

Core Function

This skill should:

  1. interpret the user's actual intent
  2. classify the question type
  3. identify ambiguity and missing elements
  4. decide whether iterative focusing questions are needed before formal framing
  5. select the most appropriate framing structure
  6. break the question into structured components
  7. narrow and bound the scope
  8. generate clarified question versions for different downstream uses
  9. assess whether the question is searchable, researchable, and testable
  10. recommend the best downstream next step

This skill should not:

  • answer the medical question itself unless explicitly asked
  • force every question into PICO
  • over-specify details with false certainty
  • leave the scope so broad that the next step remains unusable
  • ask long, unfocused questionnaires when 2–5 targeted follow-up questions would be enough

Guided Focusing Mode

This skill may use targeted follow-up questions to gradually help the user focus the problem before producing the final clarified question.

Use guided focusing mode when the user's input is any of the following:

  • too broad to define a single dominant question
  • missing two or more core elements
  • mixing multiple question types in one request
  • clearly exploratory and early-stage (for example: "I want to study X somehow")
  • explicitly asking to be guided step by step

When guided focusing mode is triggered:

  1. ask 2–5 concise, high-yield narrowing questions, not a long questionnaire
  2. prioritize the questions that will most reduce ambiguity
  3. ask in a logical order: question type → population/context → exposure/intervention/mechanism → outcome/use-case → boundary
  4. after each user reply, briefly restate the updated understanding before asking the next question if needed
  5. stop asking once the question is sufficiently bounded for a usable formulation

Do not keep asking questions unnecessarily. If the problem is already specific enough, clarify directly.

If the user wants a one-shot output instead of back-and-forth refinement, state the assumptions clearly and proceed.

Supported Question Types

The skill must first classify the dominant question type. Typical categories include:

  • treatment / intervention
  • diagnosis / diagnostic test accuracy
  • prognosis
  • prediction / biomarker stratification
  • exposure / risk factor
  • causality / etiology
  • mechanism / biology
  • implementation / health services
  • epidemiology / burden / distribution
  • translational / bench-to-bedside
  • exploratory research-planning question

If the user’s prompt contains multiple possible question types, explicitly identify the dominant one and list secondary ones.


Framing Model Selection Logic

Choose the framing model based on question type, not habit.

Typical mappings:

  • PICO → treatment / intervention / comparative effectiveness
  • PECO → exposure / risk / epidemiology / etiologic association
  • PICOTS → when time horizon, setting, or study type is central
  • diagnostic framing → target condition, index test, reference standard, performance outcomes
  • prognostic framing → baseline factor / marker → future outcome
  • mechanistic framing → biological system, process, perturbation, context, expected mechanistic readout
  • implementation framing → setting, stakeholders, workflow, barriers, outcomes
  • translational framing → biological finding, clinical use-case, validation need, intended application boundary

Never force a mechanistic or exploratory research problem into a rigid intervention template if that would distort the real question.


Decision Logic

Step 1 — Interpret the original idea

Identify what the user is probably trying to figure out, not just the literal surface wording.

Step 2 — Classify the question type

State whether the problem is primarily treatment, diagnosis, prognosis, risk/exposure, causality, mechanism, implementation, translational, or exploratory. Use references/question-type-taxonomy.md to anchor this classification.

Step 3 — Detect ambiguity and missing elements

Explicitly identify missing or underspecified items such as:

  • population
  • disease stage or subtype
  • exposure / intervention
  • comparator
  • outcome
  • timeframe
  • setting
  • subgroup
  • evidence goal
  • intended use-case
Step 4 — Decide whether guided follow-up questions are needed

If the input is still too broad or underspecified, ask a small number of focused follow-up questions before fixing the final framing. Use references/iterative-focusing-question-rules.md to choose which questions to ask and when to stop.

Show full SKILL.md (762 more words)Show less
Step 5 — Choose the best-fit framing structure

Use the most appropriate framework instead of defaulting to PICO. Use references/framing-framework-library.md to justify the selected structure.

Step 6 — Narrow and bound the scope

Convert the topic from broad direction into a manageable question definition. State what is in scope and what remains outside scope. Use references/ambiguity-and-boundary-rules.md when drawing boundaries.

Step 7 — Produce multiple clarified formulations

Generate at least:

  • a plain-language clarified question
  • a research-ready question
  • a searchable version for literature retrieval Use references/question-rewrite-rules.md and references/searchable-formulation-rules.md for this step.
Step 8 — Assess answerability and next step

State whether the question is:

  • searchable
  • researchable
  • testable
  • more suitable for evidence review, gap analysis, study design, or protocol development Use references/researchability-assessment-rules.md and references/downstream-routing-rules.md here.

Mandatory Output Structure

Always output the following sections.

A. Original Idea Interpretation

Explain how the user’s input is being interpreted and what the central intent appears to be.

B. Question Type Classification

State the dominant question type and any important secondary types. Follow references/question-type-taxonomy.md.

C. Ambiguity and Missing Elements

List the major ambiguities, underspecified variables, and scope problems.

D. Guided Focusing Questions (when needed)

If the original prompt is too broad, list the highest-yield follow-up questions used or that should be asked to narrow the topic. Keep them concise and prioritized. Follow references/iterative-focusing-question-rules.md. If guided focusing was not needed, say so explicitly.

E. Best-Fit Framing Structure

Name the selected framework and explain why it fits better than alternative framings. Follow references/framing-framework-library.md.

F. Structured Question Breakdown

Provide a table with:

  • element
  • current interpretation
  • whether narrowing is needed
  • proposed definition
G. Clarified Question Versions

Provide at least three forms:

  • plain-language version
  • research-ready version
  • searchable version
H. Scope and Boundary Statement

State what the clarified question does cover and what it does not cover.

I. Researchability and Answerability Assessment

State whether the question is currently searchable, researchable, and testable, and what evidence mode would likely be needed. Follow references/researchability-assessment-rules.md.

Recommend the most suitable next-step skill or workflow, such as:

  • evidence review / literature search
  • gap finder
  • protocol planner
  • algorithm matcher Follow references/downstream-routing-rules.md.
K. Risk of Misframing

Explain the most likely ways this question could be framed incorrectly or too broadly.


Formatting Expectations

Use structured markdown and compact tables where helpful.

At minimum, Section F must include a table like this:

ElementCurrent InterpretationNeeds Narrowing?Proposed Definition

When useful, add a second comparison table for multiple candidate question versions.


Hard Rules

  1. Do not answer the clinical or research question itself unless explicitly asked. Focus on clarifying the question.
  2. Do not force every question into PICO. Select the framework that best matches the problem type.
  3. Always identify the main ambiguity before rewriting the question.
  4. Always distinguish between what is explicit, what is inferred, and what remains undefined.
  5. When the question is too broad, narrow it before formalizing it.
  6. Provide at least one searchable formulation and one research-ready formulation.
  7. Always state what the clarified question does not cover.
  8. Do not invent highly specific assumptions unless necessary to make the question usable; if you do, state them transparently.
  9. Do not collapse clinical, causal, prognostic, diagnostic, and mechanistic questions into the same framing logic.
  10. Always recommend the most appropriate downstream next step.

Downstream Routing Standard

After clarifying the question, always suggest the best next move.

Typical routing:

  • If the user needs a search-ready evidence question → route to literature retrieval / evidence review
  • If the user needs to identify what is missing in the field → route to gap finder
  • If the user already has a high-confidence gap and needs a study design → route to gap-to-study planner
  • If the user already has a study concept and needs a method strategy → route to algorithm matcher

Quality Standard

A strong output should:

  • reveal the real question behind the vague prompt
  • use the right framing structure
  • make the question narrower and more usable
  • preserve the user’s actual intent
  • produce wording suitable for downstream search or study planning
  • clearly expose what is still uncertain

A weak output would:

  • merely rewrite the sentence more elegantly
  • use PICO mechanically even when inappropriate
  • remain too broad to search or study
  • silently assume crucial details
  • drift into answering the substantive medical question instead of framing it

Interactive Refinement Rule

When the user explicitly wants step-by-step narrowing, or when the topic remains materially ambiguous after the first pass, prefer a short guided dialogue over a premature one-shot formalization. In that case:

  • ask the minimum number of high-yield follow-up questions needed
  • update the working question after each answer
  • stop once the question becomes usable for search, study design, or gap analysis

© aipoch, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (references) in awesome-med-research-skills/Evidence Insight/clinical-question-clarifier of aipoch/medical-research-skills.

  • SKILL.md
  • eval_report_clinical-question-clarifier_result.json
  • references/ambiguity-and-boundary-rules.md
  • references/downstream-routing-rules.md
  • references/framing-framework-library.md
  • references/iterative-focusing-question-rules.md
  • references/output-section-guidance.md
  • references/question-rewrite-rules.md
  • references/question-type-taxonomy.md
  • references/researchability-assessment-rules.md
  • references/searchable-formulation-rules.md
  • references/workflow-step-template.md

Open the folder on GitHubat commit 686e09d

Compare with similar skills

Clinical Question Clarifier next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Clinical Question Clarifier compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Clinical Question Clarifier this skillaipoch/medical-research-skills1.9k—~3.9kAutomated safety check: PassMIT
Claim-Driven Experiment PlannerzjYao36/Auto-Research-Refine1286 repos~2.3kAutomated safety check: NotesNone
Metabolic Study Planneraiming-lab/AutoResearchClaw15k—~1.9kAutomated safety check: PassMIT
Research RefinezjYao36/Auto-Research-Refine1286 repos~6.9kAutomated safety check: NotesNone
Scientific BrainstormingOleafly/Oleafly2122 repos~3.5kAutomated safety check: PassMIT
Academic GrillExekiel179/psyclaw103—~2kAutomated safety check: PassMIT

Similar skills

  • Claim-Driven Experiment Planner

    zjYao36/Auto-Research-Refine

    Turns a refined research proposal into a claim-to-evidence-to-run-order roadmap instead of a sprawling benchmark wishlist.

    128 GitHub starsUsed in 6 repos~2.3k tokens
    Research & ScienceAuto-check: notes
  • Metabolic Study Planner

    aiming-lab/AutoResearchClaw

    Turns a broad metabolic modelling topic into a concrete, paper-shaped plan with organism, model, perturbations, metrics and figures before any FBA code is written.

    15k GitHub stars~1.9k tokensUpdated 1 mo ago
    Research & ScienceAuto-check passed
  • Research Refine

    zjYao36/Auto-Research-Refine

    Turns a vague research direction into a focused, problem-anchored method plan through up to five review rounds with a second model.

    128 GitHub starsUsed in 6 repos~6.9k tokens
    Research & ScienceAuto-check: notes
  • Facilitates evidence-aware scientific ideation with independent generation, structured discussion, explicit assumptions, transparent evaluation, adversarial review, and decision logs.

    212 GitHub starsUsed in 2 repos~3.5k tokens
    Research & ScienceAuto-check passed
  • Academic Grill

    Exekiel179/psyclaw

    Stress-test an academic research question, proposal, study design, analysis plan, manuscript claim, review protocol, or AI research project through a one-question-at-a-time interview until its…

    103 GitHub stars~2k tokensUpdated yesterday
    Research & ScienceAuto-check passed
  • Denario

    davila7/claude-code-templates

    Multiagent AI system for scientific research assistance that automates research workflows from data analysis to publication.

    33k GitHub starsUsed in 8 repos~1.5k tokens
    Research & ScienceAuto-check: notes

More from aipoch/medical-research-skills

All 578 skills in this repo
  • Academic Poster Generator

    aipoch/medical-research-skills

    Complete workflow for generating academic research posters from PDF literature; use when you need to extract paper content from PDFs and produce a LaTeX-based poster…

    1.9k GitHub stars~2.2k tokensUpdated 23 days ago
    Auto-check passed
  • Diagnostic Study Quality Assessment Quadas

    aipoch/medical-research-skills

    Analyzes clinical diagnostic accuracy studies for bias using the QUADAS-2 tool.

    1.9k GitHub stars~1.4k tokensUpdated 23 days ago
    Auto-check passed
  • Exploratory Data Analysis

    aipoch/medical-research-skills

    Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats.

    1.9k GitHub stars~3.7k tokensUpdated 23 days ago
    Auto-check passed
  • Iso Certification

    aipoch/medical-research-skills

    A toolkit for preparing ISO 13485:2016 certification documentation for medical device QMS.

    1.9k GitHub stars~1.8k tokensUpdated 23 days ago
    Auto-check passed
  • Journal Skills

    aipoch/medical-research-skills

    Recommends target journals for manuscript submission by analyzing the paper topic/abstract and the journal distribution of similar PubMed literature; use when users ask for journal…

    1.9k GitHub stars~1.7k tokensUpdated 23 days ago
    Auto-check passed
  • Latex Posters

    aipoch/medical-research-skills

    Creates academic-poster writing packages for LaTeX using beamerposter, tikzposter, or baposter.

    1.9k GitHub stars~1.3k tokensUpdated 23 days ago
    Auto-check passed

Questions about Clinical Question Clarifier

What does Clinical Question Clarifier do?

Clarifies a vague clinical or biomedical research idea into a structured, bounded, searchable, researchable, and testable question. Clinical Question Clarifier is an agent skill from aipoch/medical-research-skills. Clarifies a vague clinical or biomedical research idea into a structured, bounded, searchable, researchable, and testable question.

When should I use Clinical Question Clarifier?

Clinical Question Clarifier fits situations like: A user has an early-stage clinical; research thought; an over-broad topic; an ill-defined evidence question.

How do I install Clinical Question Clarifier in Claude Code?

Run `npx skills add aipoch/medical-research-skills --skill clinical-question-clarifier -a claude-code`. Or copy the skill folder (awesome-med-research-skills/Evidence Insight/clinical-question-clarifier in aipoch/medical-research-skills) into .claude/skills/clinical-question-clarifier in your project. Claude Code loads it when a task matches its description.

How do I install Clinical Question Clarifier in Codex?

Run `npx skills add aipoch/medical-research-skills --skill clinical-question-clarifier -a codex`. Or copy the skill folder (awesome-med-research-skills/Evidence Insight/clinical-question-clarifier in aipoch/medical-research-skills) into .agents/skills/clinical-question-clarifier in your project. Codex loads it when a task matches its description.

Can I use Clinical Question Clarifier in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aipoch/medical-research-skills --skill clinical-question-clarifier -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clinical-question-clarifier, .gemini/skills/clinical-question-clarifier, .github/skills/clinical-question-clarifier and .opencode/skills/clinical-question-clarifier in your project.

What does Clinical Question Clarifier need to run?

SKILL.md names no scripts, command-line tools or credentials: Clinical Question Clarifier is instructions for the agent only.

Does Clinical Question Clarifier access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Clinical Question Clarifier safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Clinical Question Clarifier use?

Clinical Question Clarifier is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clinical Question Clarifier use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.6k tokens, read only when the agent opens those files.

What are the alternatives to Clinical Question Clarifier?

Skills that share tags, products or a category with Clinical Question Clarifier: Claim-Driven Experiment Planner (zjYao36/Auto-Research-Refine, 128 stars), Metabolic Study Planner (aiming-lab/AutoResearchClaw, 15k stars), Research Refine (zjYao36/Auto-Research-Refine, 128 stars) and Scientific Brainstorming (Oleafly/Oleafly, 212 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clinical Question Clarifier?

aipoch (a GitHub organization) maintains it in aipoch/medical-research-skills, which has 1,937 GitHub stars. The repository holds 578 skills in this directory. The repository was last updated on September 17, 2026.

Source: aipoch/medical-research-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.