Clinical Trials Database
google-deepmind/science-skills
Query ClinicalTrials.gov via APIv2. An agent skill from google-deepmind/science-skills.
Draft a clinical trial protocol synopsis with the elements regulators and IRBs expect.
Install Clinical Trial Protocol
$ npx skills add mohitagw15856/pm-claude-skills --skill clinical-trial-protocol -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills clinical-trial-protocol --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/clinical-trial-protocol .claude/skills/clinical-trial-protocol && 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-trial-protocol" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/clinical-trial-protocol into .claude/skills/clinical-trial-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-trial-protocol", 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/mohitagw15856/pm-claude-skills/tree/main/skills/clinical-trial-protocolType 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 mohitagw15856/pm-claude-skills --skill clinical-trial-protocol -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills clinical-trial-protocol --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/clinical-trial-protocol .agents/skills/clinical-trial-protocol && 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-trial-protocol" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/clinical-trial-protocol into .agents/skills/clinical-trial-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-trial-protocol", 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 mohitagw15856/pm-claude-skills --skill clinical-trial-protocol -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills clinical-trial-protocol --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/clinical-trial-protocol .cursor/skills/clinical-trial-protocol && 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-trial-protocol" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/clinical-trial-protocol into .cursor/skills/clinical-trial-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-trial-protocol", 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/mohitagw15856/pm-claude-skills.git --path skills/clinical-trial-protocol--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 mohitagw15856/pm-claude-skills --skill clinical-trial-protocol -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills clinical-trial-protocol --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/clinical-trial-protocol .gemini/skills/clinical-trial-protocol && 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-trial-protocol" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/clinical-trial-protocol into .gemini/skills/clinical-trial-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-trial-protocol", 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 mohitagw15856/pm-claude-skills clinical-trial-protocolInstalls 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 mohitagw15856/pm-claude-skills --skill clinical-trial-protocol -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/clinical-trial-protocol .github/skills/clinical-trial-protocol && 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-trial-protocol" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/clinical-trial-protocol into .github/skills/clinical-trial-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-trial-protocol", 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 mohitagw15856/pm-claude-skills --skill clinical-trial-protocol -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills clinical-trial-protocol --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/clinical-trial-protocol .opencode/skills/clinical-trial-protocol && 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-trial-protocol" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/clinical-trial-protocol into .opencode/skills/clinical-trial-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clinical-trial-protocol", 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-trial-protocol- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 562 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Draft a clinical trial protocol synopsis with the elements regulators and IRBs expect.
- Asked to write a clinical trial protocol
- SKILL.md covers Working from a brief, Required Inputs, Output Format and Quality Checks, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A study protocol synopsis
What it does
Clinical Trial Protocol is an agent skill from mohitagw15856/pm-claude-skills. Draft a clinical trial protocol synopsis with the elements regulators and IRBs expect. Use when asked to write a clinical trial protocol, a study protocol synopsis, a trial design, or to structure endpoints/eligibility/statistics for an interventional study. Produces a structured protocol synopsis — objectives, design, population with eligibility, interventions, endpoints, statistics, and safety/ethics — for expert review. (For non-clinical/UX research, use research-protocol.)
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: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to write a clinical trial protocol
- A study protocol synopsis
- Structure endpoints/eligibility/statistics for an interventional study
Example prompts
- “/clinical-trial-protocol”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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 Trial Protocol loads about 1.2k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 562 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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 562 words, ~1,213 tokens.
Download SKILL.mdSave it as
.claude/skills/clinical-trial-protocol/SKILL.md (or your agent's skills folder).- name
- clinical-trial-protocol
- description
- Draft a clinical trial protocol synopsis with the elements regulators and IRBs expect. Use when asked to write a clinical trial protocol, a study protocol synopsis, a trial design, or to structure endpoints/eligibility/statistics for an interventional study. Produces a structured protocol synopsis — objectives, design, population with eligibility, interventions, endpoints, statistics, and safety/ethics — for expert review. (For non-clinical/UX research, use research-protocol.)
Clinical Trial Protocol Skill
A clinical trial protocol stands or falls on a few linked decisions: a clear objective, a design that can answer
it, endpoints that measure it, eligibility that defines who's studied, and a statistical plan that can detect the
effect. This skill drafts a protocol synopsis that makes those decisions explicit and internally consistent, in
the structure IRBs/ethics committees and regulators expect. (For a general academic or UX study, use
research-protocol.)
Safety & compliance note: this is a drafting aid for expert review, not regulatory, medical, or statistical sign-off. Real trials require qualified investigators, a statistician, and IRB/ethics and regulatory approval (e.g. GCP, ICH, local law). Do not invent efficacy/safety data; mark assumptions for the study team to set.
Working from a brief
Given "a phase II trial of drug X for condition Y", produce the full synopsis anyway — infer a defensible design, endpoints, and eligibility appropriate to the phase and condition, and clearly label every inferred choice as a draft assumption for the study team and statistician to confirm. Never fabricate prior data or effect sizes; state them as placeholders to be set.
Required Inputs
Ask for these only if they aren't already provided (else infer and label as draft):
- Intervention & condition — what's being studied, in whom, and the phase.
- Objective / question — the primary question the trial must answer.
- Comparator — placebo, standard of care, or active control; and blinding.
- Outcome of interest — how benefit (and harm) will be measured.
- Constraints — known population, setting, and any regulatory context.
Output Format
Clinical Trial Protocol Synopsis: [title]
- 1. Background & rationale — the problem, prior evidence (mark placeholders), and why this trial.
- 2. Objectives — primary and secondary, each as a precise, testable statement.
- 3. Design — phase, type (RCT, etc.), allocation/randomisation, blinding, arms, and duration.
- 4. Population — setting, and explicit inclusion and exclusion criteria.
- 5. Interventions — the intervention and comparator: dose/regimen, administration, and concomitant rules.
- 6. Endpoints — primary endpoint (one, tied to the primary objective), secondary endpoints, and how/when each is measured.
- 7. Statistical considerations — analysis populations, the primary analysis, and a sample-size basis (with assumptions flagged for the statistician).
- 8. Safety — adverse-event definitions, monitoring/reporting, stopping rules, and any DSMB.
- 9. Ethics & conduct — informed consent, IRB/ethics approval, data integrity, and GCP adherence.
Close with assumptions to confirm and a reminder that a qualified investigator and statistician must own the final protocol.
Show full SKILL.md (174 more words)Show less
Quality Checks
- The primary objective, primary endpoint, and primary analysis are aligned and consistent
- There is exactly one primary endpoint, clearly measurable and time-anchored
- Inclusion/exclusion criteria are explicit and operationally checkable
- Sample-size basis is stated with its assumptions flagged for the statistician
- Safety monitoring, reporting, and stopping rules are present
- Ethics/consent/IRB and GCP elements are included; no efficacy/safety data is invented
Anti-Patterns
- Do not invent prior efficacy/safety data or effect sizes — mark them as placeholders to be set
- Do not list multiple "primary" endpoints — pick one and demote the rest to secondary
- Do not let objective, endpoint, and analysis drift apart — they must answer the same question
- Do not present this as regulatory/statistical sign-off — it's a draft for expert review
- Do not omit safety monitoring and stopping rules — a protocol without them isn't approvable
Based On
Clinical research practice — objective-endpoint-analysis alignment, explicit eligibility, sample-size justification, and ICH-GCP safety/ethics structure.
Example Trigger Phrases
- "Write a clinical trial protocol."
- "Draft a study protocol synopsis."
- "Design the trial."
- "Structure endpoints, eligibility and statistics for an interventional study."
© mohitagw15856, MIT. 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/clinical-trial-protocol of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Clinical Trial Protocol 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 Trial Protocol this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| 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 mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Clinical Trial Protocol
What does Clinical Trial Protocol do?
Draft a clinical trial protocol synopsis with the elements regulators and IRBs expect. Clinical Trial Protocol is an agent skill from mohitagw15856/pm-claude-skills. Draft a clinical trial protocol synopsis with the elements regulators and IRBs expect.
When should I use Clinical Trial Protocol?
Clinical Trial Protocol fits situations like: asked to write a clinical trial protocol; A study protocol synopsis; structure endpoints/eligibility/statistics for an interventional study.
How do I install Clinical Trial Protocol in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill clinical-trial-protocol -a claude-code`. Or copy the skill folder (skills/clinical-trial-protocol in mohitagw15856/pm-claude-skills) into .claude/skills/clinical-trial-protocol in your project. Claude Code loads it when a task matches its description.
How do I install Clinical Trial Protocol in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill clinical-trial-protocol -a codex`. Or copy the skill folder (skills/clinical-trial-protocol in mohitagw15856/pm-claude-skills) into .agents/skills/clinical-trial-protocol in your project. Codex loads it when a task matches its description.
Can I use Clinical Trial Protocol 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 mohitagw15856/pm-claude-skills --skill clinical-trial-protocol -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-trial-protocol, .gemini/skills/clinical-trial-protocol, .github/skills/clinical-trial-protocol and .opencode/skills/clinical-trial-protocol in your project.
What does Clinical Trial Protocol need to run?
SKILL.md names no scripts, command-line tools or credentials: Clinical Trial Protocol is instructions for the agent only.
Does Clinical Trial Protocol 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 Trial Protocol 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 Trial Protocol use?
Clinical Trial Protocol is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Clinical Trial Protocol use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Trial Protocol?
Skills that share tags, products or a category with Clinical Trial Protocol: 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 Trial Protocol?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.