Clinical Trials Database
google-deepmind/science-skills
Query ClinicalTrials.gov via APIv2. An agent skill from google-deepmind/science-skills.
Clinical research workflow guide for protocol design, endpoint selection, evidence grading, reporting-guideline selection, statistical planning, and clinical-trial evidence synthesis.
Install Clinical Research Tools
$ npx skills add DrugClaw/DrugClaw --skill clinical-research-tools -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install DrugClaw/DrugClaw clinical-research-tools --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/DrugClaw/DrugClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/medical/clinical-research-tools .claude/skills/clinical-research-tools && 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-research-tools" agent skill from https://github.com/DrugClaw/DrugClaw/tree/main/skills/medical/clinical-research-tools into .claude/skills/clinical-research-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-research-tools", 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/DrugClaw/DrugClaw/tree/main/skills/medical/clinical-research-toolsType 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 DrugClaw/DrugClaw --skill clinical-research-tools -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install DrugClaw/DrugClaw clinical-research-tools --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DrugClaw/DrugClaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/medical/clinical-research-tools .agents/skills/clinical-research-tools && 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-research-tools" agent skill from https://github.com/DrugClaw/DrugClaw/tree/main/skills/medical/clinical-research-tools into .agents/skills/clinical-research-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-research-tools", 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 DrugClaw/DrugClaw --skill clinical-research-tools -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install DrugClaw/DrugClaw clinical-research-tools --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DrugClaw/DrugClaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/medical/clinical-research-tools .cursor/skills/clinical-research-tools && 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-research-tools" agent skill from https://github.com/DrugClaw/DrugClaw/tree/main/skills/medical/clinical-research-tools into .cursor/skills/clinical-research-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-research-tools", 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/DrugClaw/DrugClaw.git --path skills/medical/clinical-research-tools--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 DrugClaw/DrugClaw --skill clinical-research-tools -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install DrugClaw/DrugClaw clinical-research-tools --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DrugClaw/DrugClaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/medical/clinical-research-tools .gemini/skills/clinical-research-tools && 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-research-tools" agent skill from https://github.com/DrugClaw/DrugClaw/tree/main/skills/medical/clinical-research-tools into .gemini/skills/clinical-research-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-research-tools", 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 DrugClaw/DrugClaw clinical-research-toolsInstalls 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 DrugClaw/DrugClaw --skill clinical-research-tools -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/DrugClaw/DrugClaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/medical/clinical-research-tools .github/skills/clinical-research-tools && 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-research-tools" agent skill from https://github.com/DrugClaw/DrugClaw/tree/main/skills/medical/clinical-research-tools into .github/skills/clinical-research-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-research-tools", 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 DrugClaw/DrugClaw --skill clinical-research-tools -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install DrugClaw/DrugClaw clinical-research-tools --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DrugClaw/DrugClaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/medical/clinical-research-tools .opencode/skills/clinical-research-tools && 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-research-tools" agent skill from https://github.com/DrugClaw/DrugClaw/tree/main/skills/medical/clinical-research-tools into .opencode/skills/clinical-research-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-research-tools", 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.
Facts
- Skill name
clinical-research-tools- GitHub stars
- 126
- Token cost
- ~1.2k tokens
- SKILL.md length
- 479 words
- Files
- 1
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Clinical research workflow guide for protocol design, endpoint selection, evidence grading, reporting-guideline selection, statistical planning, and clinical-trial evidence synthesis.
- Works in 5 steps: Keep the task at the study or cohort… → Separate confirmed study facts from… → State assumptions behind endpoint,… → …
- The user asks to design
- SKILL.md covers Working Rules, Study Design Map, Reporting Guideline Map and Protocol Workflow, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Clinical Research Tools is an agent skill from DrugClaw/DrugClaw. Clinical research workflow guide for protocol design, endpoint selection, evidence grading, reporting-guideline selection, statistical planning, and clinical-trial evidence synthesis. Use when the user asks to design or review human-subjects research, trial analyses, observational studies, study protocols, CSRs, or clinical evidence summaries without requesting patient-specific diagnosis or treatment decisions.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Clinical and healthcare research. The repository describes itself as: 💊 AI Research Assistant for Accelerated Drug Discovery. 🦞. The licence is Apache-2.0.
When your agent uses it
- The user asks to design
- Review human-subjects research
- Observational studies
- Study protocols
Example prompts
- “/clinical-research-tools”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Keep the task at the study or cohort level.
- Separate confirmed study facts from proposed design choices.
- State assumptions behind endpoint, power, and statistical-model choices.
- Call out data leakage, immortal-time bias, selection bias, and confounding whenever relevant.
- Do not present DrugClaw as giving medical advice, treatment recommendations, or diagnostic decisions.
What it can do on your machine
Read from SKILL.md and the folder at commit 960a6e0. 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 Research Tools loads about 1.2k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 479 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.
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 DrugClaw/DrugClaw at commit 960a6e0, republished under its Apache-2.0 licence (© DrugClaw). 479 words, ~1,163 tokens.
Download SKILL.mdSave it as
.claude/skills/clinical-research-tools/SKILL.md (or your agent's skills folder).- name
- clinical-research-tools
- description
- Clinical research workflow guide for protocol design, endpoint selection, evidence grading, reporting-guideline selection, statistical planning, and clinical-trial evidence synthesis. Use when the user asks to design or review human-subjects research, trial analyses, observational studies, study protocols, CSRs, or clinical evidence summaries without requesting patient-specific diagnosis or treatment decisions.
Clinical Research Tools
Use this skill for group-level human research work, not bedside care.
Typical triggers:
- choose between RCT, cohort, case-control, cross-sectional, diagnostic, or single-arm designs
- define primary and secondary endpoints, estimands, eligibility criteria, or subgroup analyses
- select the right reporting guideline such as CONSORT, STROBE, PRISMA, STARD, TRIPOD, SPIRIT, or CARE
- draft protocol, SAP, CSR, or evidence-summary outlines
- review bias, confounding, missing data, and sample-size assumptions
- prepare trial or real-world-evidence summaries for drug-discovery programs
Working Rules
- Keep the task at the study or cohort level.
- Separate confirmed study facts from proposed design choices.
- State assumptions behind endpoint, power, and statistical-model choices.
- Call out data leakage, immortal-time bias, selection bias, and confounding whenever relevant.
- Do not present DrugClaw as giving medical advice, treatment recommendations, or diagnostic decisions.
Study Design Map
Use this quick routing:
RCT: intervention efficacy, causal inference, registration-ready protocolsProspective cohort: prognosis, exposure-outcome tracking, real-world evidenceRetrospective cohort: registry or EHR analyses with explicit confounding controlCase-control: rare outcomes or exploratory risk-factor workCross-sectional: prevalence, survey snapshots, baseline association workDiagnostic accuracy: sensitivity, specificity, ROC, calibration, decision curvesPrediction model: risk scores, survival models, treatment-response models with external validation plans
Reporting Guideline Map
Choose and state the governing framework early:
CONSORT: randomized trialsSPIRIT: trial protocolsSTROBE: observational studiesPRISMA: systematic reviews and meta-analysisSTARD: diagnostic accuracy studiesTRIPOD: prediction modelsCARE: case reportsICH E3: clinical study reports
Protocol Workflow
For protocol or study-design requests:
- Define population, intervention or exposure, comparator, outcome, and timeframe.
- State inclusion and exclusion criteria.
- Define primary endpoint, key secondary endpoints, and censoring rules.
- Choose analysis populations: ITT, mITT, per-protocol, safety.
- Describe missing-data handling and sensitivity analyses.
- State sample-size assumptions clearly: alpha, power, effect size, event rate, dropout.
- Specify monitoring, ethics, registration, and data-governance requirements.
Show full SKILL.md (175 more words)Show less
Statistical Planning Checklist
Always address:
- endpoint type: binary, continuous, count, time-to-event
- stratification variables and subgroup policy
- multiplicity control
- covariate adjustment policy
- temporal leakage and look-ahead bias
- external validation or temporal validation when building prediction models
- calibration, not only discrimination, for predictive work
Evidence Synthesis
For evidence summaries:
- identify study type and evidence level
- note patient population, line of therapy, biomarker context, and comparator
- distinguish efficacy, safety, and external-validity conclusions
- state what remains uncertain
- use cautious language for indirect or observational evidence
Outputs
Good outputs usually include:
- one-page design summary or protocol skeleton
- endpoint table
- statistical analysis outline
- bias and limitation section
- reporting-guideline checklist
Related Skills
For ClinicalTrials.gov, openFDA, or OpenAlex lookups, activate pharma-db-tools.
For cohort tables, biosignals, or DICOM datasets, activate medical-data-tools.
For citation cleanup, evidence matrices, or structured review drafting, activate literature-review-tools.
For hypothesis tests, regression, or effect-size reporting, activate stat-modeling-tools.
For Kaplan-Meier, log-rank, or Cox workflows, activate survival-analysis-tools.
For manuscript critique, hypothesis framing, or reproducibility checklists, activate scientific-workflow-tools.
For molecular, variant, pathway, or structure work, activate bio-tools, bio-db-tools, chem-tools, or docking-tools as appropriate.
© DrugClaw, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/medical/clinical-research-tools of DrugClaw/DrugClaw.
Open the folder on GitHubat commit 960a6e0
Compare with similar skills
Clinical Research Tools 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 Research Tools this skillDrugClaw/DrugClaw | 126 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Clinical Trials Databasegoogle-deepmind/science-skills | 3.2k | 2 repos | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw | 617 | 1 repos | ~1.8k | Automated safety check: Pass | None | |
| Biomedical Analysis Dispatchxjtulyc/MedgeClaw | 617 | 1 repos | ~2k | Automated safety check: Pass | None | |
| Research Paperluwill/research-skills | 862 | — | ~1.9k | Automated safety check: Pass | None | |
| Research Proposalluwill/research-skills | 862 | — | ~4.5k | Automated safety check: Notes | None |
Similar skills
CHARLS Paper Reproduction Guide
xjtulyc/MedgeClaw
Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.
Biomedical Analysis Dispatch
xjtulyc/MedgeClaw
Routes bioinformatics, drug discovery, clinical and multi-omics tasks from a chat interface to Claude Code sessions running K-Dense scientific skills, with a live dashboard per task.
Research Paper
luwill/research-skills
A skill your agent uses when the user asks to write or draft an ORIGINAL RESEARCH ARTICLE — IMRaD paper, conference paper, short/workshop paper, 研究论文/期刊论文/会议论文 — reporting their own completed…
Research Proposal
luwill/research-skills
A skill your agent uses when the user asks to write or draft a PhD / doctoral research proposal, research plan, 研究计划书, or 开题报告 — a forward-looking plan of background, gap, research questions…
Medical Imaging Review
LeonChaoX/qinyan-academic-skills
Write comprehensive literature reviews for medical imaging AI research.
More from DrugClaw/DrugClaw
All 25 skills in this repoBio DB Tools
DrugClaw/DrugClaw
Query public biology databases and APIs including UniProt, RCSB PDB, AlphaFold DB, ClinVar, dbSNP, gnomAD, Ensembl, GEO, InterPro, KEGG, OpenTargets, Reactome, and STRING.
Grn Tools
DrugClaw/DrugClaw
Gene regulatory network workflow guide for transcriptomics and single-cell expression matrices using Arboreto, GRNBoost2, and GENIE3.
Knowledge Graph Tools
DrugClaw/DrugClaw
Drug-discovery knowledge-graph workflow guide for assembling drug-target-disease-pathway relationship graphs from OpenTargets GraphQL, ChEMBL REST, STRING PPI, and Reactome pathway APIs, then…
Literature Review Tools
DrugClaw/DrugClaw
Research-literature workflow guide for evidence-matrix assembly, citation-table normalization, structured review synthesis, and research-gap mapping.
Medical Data Tools
DrugClaw/DrugClaw
Medical data workflow guide for DICOM metadata inspection and basic de-identification, physiological signal analysis with NeuroKit2, and cohort-table profiling for clinical research datasets.
Omics Tools
DrugClaw/DrugClaw
Omics and single-cell workflow guide for AnnData, Scanpy-style dataset profiling, PyDESeq2-oriented count checks, pysam alignment inspection, and pyOpenMS mass-spectrometry summaries.
Related
Categories
Questions about Clinical Research Tools
What does Clinical Research Tools do?
Clinical research workflow guide for protocol design, endpoint selection, evidence grading, reporting-guideline selection, statistical planning, and clinical-trial evidence synthesis. Clinical Research Tools is an agent skill from DrugClaw/DrugClaw. Clinical research workflow guide for protocol design, endpoint selection, evidence grading, reporting-guideline selection, statistical planning, and clinical-trial evidence synthesis.
When should I use Clinical Research Tools?
Clinical Research Tools fits situations like: the user asks to design; review human-subjects research; observational studies; study protocols.
How do I install Clinical Research Tools in Claude Code?
Run `npx skills add DrugClaw/DrugClaw --skill clinical-research-tools -a claude-code`. Or copy the skill folder (skills/medical/clinical-research-tools in DrugClaw/DrugClaw) into .claude/skills/clinical-research-tools in your project. Claude Code loads it when a task matches its description.
How do I install Clinical Research Tools in Codex?
Run `npx skills add DrugClaw/DrugClaw --skill clinical-research-tools -a codex`. Or copy the skill folder (skills/medical/clinical-research-tools in DrugClaw/DrugClaw) into .agents/skills/clinical-research-tools in your project. Codex loads it when a task matches its description.
Can I use Clinical Research Tools 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 DrugClaw/DrugClaw --skill clinical-research-tools -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-research-tools, .gemini/skills/clinical-research-tools, .github/skills/clinical-research-tools and .opencode/skills/clinical-research-tools in your project.
What does Clinical Research Tools need to run?
SKILL.md names no scripts, command-line tools or credentials: Clinical Research Tools is instructions for the agent only.
Does Clinical Research Tools 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 Research Tools 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 Research Tools use?
Clinical Research Tools is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Clinical Research Tools use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Clinical Research Tools?
Skills that share tags, products or a category with Clinical Research Tools: Clinical Trials Database (google-deepmind/science-skills, 3.2k stars), CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars), Biomedical Analysis Dispatch (xjtulyc/MedgeClaw, 617 stars) and Research Paper (luwill/research-skills, 862 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Clinical Research Tools?
DrugClaw (a GitHub organization) maintains it in DrugClaw/DrugClaw, which has 126 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on March 23, 2026.
Source: DrugClaw/DrugClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.