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.
Clarifies a vague clinical or biomedical research idea into a structured, bounded, searchable, researchable, and testable question.
$ npx skills add aipoch/medical-research-skills --skill clinical-question-clarifier -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aipoch/medical-research-skills clinical-question-clarifier --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "clinical-question-clarifier" agent skill from https://github.com/aipoch/medical-research-skills/tree/main/awesome-med-research-skills/Evidence%20Insight/clinical-question-clarifier into .claude/skills/clinical-question-clarifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-question-clarifier", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aipoch/medical-research-skills/tree/main/awesome-med-research-skills/Evidence%20Insight/clinical-question-clarifierType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aipoch/medical-research-skills --skill clinical-question-clarifier -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aipoch/medical-research-skills clinical-question-clarifier --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aipoch/medical-research-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/'awesome-med-research-skills/Evidence Insight/clinical-question-clarifier' .agents/skills/clinical-question-clarifier && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clinical-question-clarifier" agent skill from https://github.com/aipoch/medical-research-skills/tree/main/awesome-med-research-skills/Evidence%20Insight/clinical-question-clarifier into .agents/skills/clinical-question-clarifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-question-clarifier", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aipoch/medical-research-skills --skill clinical-question-clarifier -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aipoch/medical-research-skills clinical-question-clarifier --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aipoch/medical-research-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/'awesome-med-research-skills/Evidence Insight/clinical-question-clarifier' .cursor/skills/clinical-question-clarifier && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "clinical-question-clarifier" agent skill from https://github.com/aipoch/medical-research-skills/tree/main/awesome-med-research-skills/Evidence%20Insight/clinical-question-clarifier into .cursor/skills/clinical-question-clarifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-question-clarifier", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aipoch/medical-research-skills.git --path 'awesome-med-research-skills/Evidence Insight/clinical-question-clarifier'--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aipoch/medical-research-skills --skill clinical-question-clarifier -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aipoch/medical-research-skills clinical-question-clarifier --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aipoch/medical-research-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/'awesome-med-research-skills/Evidence Insight/clinical-question-clarifier' .gemini/skills/clinical-question-clarifier && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "clinical-question-clarifier" agent skill from https://github.com/aipoch/medical-research-skills/tree/main/awesome-med-research-skills/Evidence%20Insight/clinical-question-clarifier into .gemini/skills/clinical-question-clarifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-question-clarifier", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aipoch/medical-research-skills clinical-question-clarifierInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aipoch/medical-research-skills --skill clinical-question-clarifier -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aipoch/medical-research-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/'awesome-med-research-skills/Evidence Insight/clinical-question-clarifier' .github/skills/clinical-question-clarifier && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "clinical-question-clarifier" agent skill from https://github.com/aipoch/medical-research-skills/tree/main/awesome-med-research-skills/Evidence%20Insight/clinical-question-clarifier into .github/skills/clinical-question-clarifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-question-clarifier", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aipoch/medical-research-skills --skill clinical-question-clarifier -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aipoch/medical-research-skills clinical-question-clarifier --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aipoch/medical-research-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/'awesome-med-research-skills/Evidence Insight/clinical-question-clarifier' .opencode/skills/clinical-question-clarifier && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "clinical-question-clarifier" agent skill from https://github.com/aipoch/medical-research-skills/tree/main/awesome-med-research-skills/Evidence%20Insight/clinical-question-clarifier into .opencode/skills/clinical-question-clarifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-question-clarifier", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
clinical-question-clarifierClarifies 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. 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.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 686e09d. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from aipoch/medical-research-skills at commit 686e09d, republished under its MIT licence (© aipoch). 1,933 words, ~3,934 tokens.
.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.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:
This skill must not confuse question clarification with question answering.
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.
Valid input: one or more of the following:
Examples:
Out-of-scope — respond with the redirect below and stop:
"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]."
This skill should:
This skill should not:
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:
When guided focusing mode is triggered:
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.
The skill must first classify the dominant question type. Typical categories include:
If the user’s prompt contains multiple possible question types, explicitly identify the dominant one and list secondary ones.
Choose the framing model based on question type, not habit.
Typical mappings:
Never force a mechanistic or exploratory research problem into a rigid intervention template if that would distort the real question.
Identify what the user is probably trying to figure out, not just the literal surface wording.
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.
Explicitly identify missing or underspecified items such as:
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.
Use the most appropriate framework instead of defaulting to PICO. Use references/framing-framework-library.md to justify the selected structure.
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.
Generate at least:
references/question-rewrite-rules.md and references/searchable-formulation-rules.md for this step.State whether the question is:
references/researchability-assessment-rules.md and references/downstream-routing-rules.md here.Always output the following sections.
Explain how the user’s input is being interpreted and what the central intent appears to be.
State the dominant question type and any important secondary types. Follow references/question-type-taxonomy.md.
List the major ambiguities, underspecified variables, and scope problems.
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.
Name the selected framework and explain why it fits better than alternative framings. Follow references/framing-framework-library.md.
Provide a table with:
Provide at least three forms:
State what the clarified question does cover and what it does not cover.
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:
references/downstream-routing-rules.md.Explain the most likely ways this question could be framed incorrectly or too broadly.
Use structured markdown and compact tables where helpful.
At minimum, Section F must include a table like this:
| Element | Current Interpretation | Needs Narrowing? | Proposed Definition |
|---|
When useful, add a second comparison table for multiple candidate question versions.
After clarifying the question, always suggest the best next move.
Typical routing:
A strong output should:
A weak output would:
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:
© aipoch, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 11 other files (references) in awesome-med-research-skills/Evidence Insight/clinical-question-clarifier of aipoch/medical-research-skills.
Open the folder on GitHubat commit 686e09d
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Clinical Question Clarifier this skillaipoch/medical-research-skills | 1.9k | — | ~3.9k | Automated safety check: Pass | MIT | |
| Claim-Driven Experiment PlannerzjYao36/Auto-Research-Refine | 128 | 6 repos | ~2.3k | Automated safety check: Notes | None | |
| Metabolic Study Planneraiming-lab/AutoResearchClaw | 15k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Research RefinezjYao36/Auto-Research-Refine | 128 | 6 repos | ~6.9k | Automated safety check: Notes | None | |
| Scientific BrainstormingOleafly/Oleafly | 212 | 2 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Academic GrillExekiel179/psyclaw | 103 | — | ~2k | Automated safety check: Pass | MIT |
zjYao36/Auto-Research-Refine
Turns a refined research proposal into a claim-to-evidence-to-run-order roadmap instead of a sprawling benchmark wishlist.
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.
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.
Oleafly/Oleafly
Facilitates evidence-aware scientific ideation with independent generation, structured discussion, explicit assumptions, transparent evaluation, adversarial review, and decision logs.
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…
davila7/claude-code-templates
Multiagent AI system for scientific research assistance that automates research workflows from data analysis to publication.
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…
aipoch/medical-research-skills
Analyzes clinical diagnostic accuracy studies for bias using the QUADAS-2 tool.
aipoch/medical-research-skills
Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats.
aipoch/medical-research-skills
A toolkit for preparing ISO 13485:2016 certification documentation for medical device QMS.
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…
aipoch/medical-research-skills
Creates academic-poster writing packages for LaTeX using beamerposter, tikzposter, or baposter.
Categories
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.
Clinical Question Clarifier fits situations like: A user has an early-stage clinical; research thought; an over-broad topic; an ill-defined evidence question.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Clinical Question Clarifier is instructions for the agent only.
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.
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.
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.
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.
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.
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.