Clinical Trials Database
google-deepmind/science-skills
Query ClinicalTrials.gov via APIv2. An agent skill from google-deepmind/science-skills.
A multi-source clinical-trials intelligence system — aggregates, normalizes, and analyzes trials across ClinicalTrials.gov, EU CTIS, and biomedical sources, with an offline SQLite engine no…
$ npx skills add mvanhorn/printing-press-library --skill pp-clinical-trials -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clinical-trials --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/mvanhorn/printing-press-library.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-skills/pp-clinical-trials .claude/skills/pp-clinical-trials && 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 "pp-clinical-trials" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clinical-trials into .claude/skills/pp-clinical-trials/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clinical-trials", 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/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clinical-trialsType 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 mvanhorn/printing-press-library --skill pp-clinical-trials -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clinical-trials --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-skills/pp-clinical-trials .agents/skills/pp-clinical-trials && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pp-clinical-trials" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clinical-trials into .agents/skills/pp-clinical-trials/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clinical-trials", 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 mvanhorn/printing-press-library --skill pp-clinical-trials -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clinical-trials --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-skills/pp-clinical-trials .cursor/skills/pp-clinical-trials && 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 "pp-clinical-trials" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clinical-trials into .cursor/skills/pp-clinical-trials/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clinical-trials", 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/mvanhorn/printing-press-library.git --path cli-skills/pp-clinical-trials--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 mvanhorn/printing-press-library --skill pp-clinical-trials -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clinical-trials --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-skills/pp-clinical-trials .gemini/skills/pp-clinical-trials && 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 "pp-clinical-trials" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clinical-trials into .gemini/skills/pp-clinical-trials/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clinical-trials", 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 mvanhorn/printing-press-library pp-clinical-trialsInstalls 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 mvanhorn/printing-press-library --skill pp-clinical-trials -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-skills/pp-clinical-trials .github/skills/pp-clinical-trials && 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 "pp-clinical-trials" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clinical-trials into .github/skills/pp-clinical-trials/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clinical-trials", 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 mvanhorn/printing-press-library --skill pp-clinical-trials -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mvanhorn/printing-press-library pp-clinical-trials --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-skills/pp-clinical-trials .opencode/skills/pp-clinical-trials && 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 "pp-clinical-trials" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-clinical-trials into .opencode/skills/pp-clinical-trials/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-clinical-trials", 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.
pp-clinical-trialsA multi-source clinical-trials intelligence system — aggregates, normalizes, and analyzes trials across ClinicalTrials.gov, EU CTIS, and biomedical sources, with an offline SQLite engine no…
Pp Clinical Trials is an agent skill from mvanhorn/printing-press-library. A multi-source clinical-trials intelligence system — aggregates, normalizes, and analyzes trials across ClinicalTrials.gov, EU CTIS, and biomedical sources, with an offline SQLite engine no single-registry tool has. Trigger phrases: what clinical trials are running for, recruiting trials for, phase 3 trials for, compare these two drugs trials, emerging therapies in, is this trial risky, watch trials for, clinical trials intelligence, use clinical-trials, run clinical-trials.
Its SKILL.md is about 4.6k 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 and Recruiting and HR. It works with SQLite. The repository describes itself as: Official library of CLIs generated by the CLI Printing Press. Endorsed, tested, and community-contributed. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit d9a1696. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
goclaudenpxFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
semver.orgFrom 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.
Pp Clinical Trials loads about 4.6k tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 1,922 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 noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, BashAutomated 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 mvanhorn/printing-press-library at commit d9a1696, republished under its Apache-2.0 licence (© mvanhorn). 1,922 words, ~4,613 tokens.
.claude/skills/pp-clinical-trials/SKILL.md (or your agent's skills folder).<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/health/clinical-trials/SKILL.md,
regenerated post-merge by tools/generate-skills/. Hand-edits here are
silently overwritten on the next regen. Edit the library/ source instead.
See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
This skill drives the clinical-trials-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
$HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:npx -y @mvanhorn/printing-press-library install clinical-trials --cli-onlyclinical-trials-pp-cli --version$PATH for the agent/runtime that will invoke this skill.If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:
go install github.com/mvanhorn/printing-press-library/library/health/clinical-trials/cmd/clinical-trials-pp-cli@latestIf --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
Every other ClinicalTrials.gov tool is a single-source pass-through. This one merges registries into one normalized trial model, dedups across NCT/EUCTR/WHO IDs, and computes intelligence: emerging therapies, recruitment velocity, drug comparisons, abandonment risk, geographic hotspots, and sponsor dominance. It degrades gracefully down a fallback chain and never crashes, caching everything locally for offline, agent-native analysis.
Reach for this CLI when the task is understanding the clinical-trials landscape — what is running, what is emerging, how two drugs compare, whether a trial is risky, or where recruitment is concentrated — across more than one registry. It is the right tool for evidence synthesis, competitive trial analysis, and weekly landscape reports.
Do not use this CLI for:
These capabilities aren't available in any other tool for this API.
emerging — See the fastest-growing trial categories for a disease area, with percent change.
Pick this when the user asks where research is heading, not about one specific trial.
clinical-trials-pp-cli emerging cancer --jsonvelocity — Measure how fast a disease area's trials and enrollment are growing over time.
Use to quantify momentum in a field; buckets a sampled set of trials by start year and reports a recent-vs-prior growth rate (no prior snapshot needed).
clinical-trials-pp-cli velocity "alzheimer" --jsoncompare — Compare two drugs head-to-head across trial counts, phases, sponsors, and recruiting status.
Use to weigh two interventions by real trial activity, not marketing.
clinical-trials-pp-cli compare "Keytruda" "Opdivo" --jsonrisk — Get an explainable risk read on a single trial from termination, enrollment, site count, sponsor track record, and phase factor (earlier phases = higher risk).
Use to triage whether a trial is likely to complete and report.
clinical-trials-pp-cli risk NCT07011732 --jsonforecast — Forward-looking completion outlook for a trial, derived from the same deterministic signals as risk.
Use to get a plain-language outlook band and the primary concerns behind it. Caveat: heuristic only — a read of registry signals, not a clinical prediction.
clinical-trials-pp-cli forecast NCT07011732 --jsonsponsors — Rank who runs the most trials in an area, classified as industry, academic, or government.
Use to see who controls research in a field.
clinical-trials-pp-cli sponsors "diabetes" --jsondigest — Compact "what's notable" snapshot for a condition or search term: total matched, recruiting count, newest trials, and recently-stopped ones.
Use for a fast read on a topic's current state; a read-only point-in-time snapshot (use watch for a persistent change feed). --limit bounds the newest and recently-stopped lists.
clinical-trials-pp-cli digest "type 2 diabetes" --limit 5 --jsonsimilar — Find trials similar to a given NCT ID by shared condition, phase, and intervention profile.
Use to surface comparable trials from registry signals only (no ML matching); --limit caps how many matches are returned.
clinical-trials-pp-cli similar NCT04280705 --limit 5 --jsontimeline — Show a trial's key dates in chronological order: start, primary completion, completion, and last-update posted.
Use to see a single trial's schedule at a glance; dates with no posted value are omitted.
clinical-trials-pp-cli timeline NCT04280705 --jsonenrollment-check — Heuristic plausibility check on a trial's posted enrollment target relative to its phase.
Reuses the risk command's enrollment signal. Caveat: this is a heuristic from observable registry signals only — not a clinical judgment or a prediction of whether the trial will enroll.
clinical-trials-pp-cli enrollment-check NCT04280705 --jsonexport-fhir — Export a trial's registry metadata as a minimal FHIR R4 ResearchStudy resource (JSON) or a flat CSV row.
Use to hand a trial's core metadata to a FHIR-aware system or a spreadsheet. --format fhir (default) emits the ResearchStudy JSON; --format csv emits one flat row. Caveat: this is a lightweight metadata export, not a full FHIR-conformant clinical dataset, and is not validated against a FHIR profile.
clinical-trials-pp-cli export-fhir NCT04280705
clinical-trials-pp-cli export-fhir NCT04280705 --format csvwatch — Track a term and report new, changed, and terminated trials since the last run.
Use to monitor a topic over time instead of re-reading full result sets.
clinical-trials-pp-cli watch "vitamin d" --jsonsearch — Search a single normalized trial model aggregated and deduplicated across ClinicalTrials.gov, EU CTIS, and OpenAlex.
Use as the default entry point; it queries the merged multi-source mirror, so it sees more than any single registry.
clinical-trials-pp-cli search "glioblastoma" --jsonevidence — Link a trial to its publications and citation context via PubMed and OpenAlex.
Use to check whether a trial actually published results.
clinical-trials-pp-cli evidence NCT07011732 --jsonsafety — Surface FDA adverse-event signals for a trial's intervention drug.
Use to add a real-world safety lens to a trial's drug.
clinical-trials-pp-cli safety "pembrolizumab" --jsonreport — Compose search, emerging, hotspots, and sponsors into one markdown or CSV briefing for a topic.
Use for a weekly landscape summary a clinician can read at a glance.
clinical-trials-pp-cli report "long covid" --format mdhealth — Show live status, latency, and failure rate for every data source in the fallback chain.
Use to know which sources are degraded before trusting a result.
clinical-trials-pp-cli health --jsonclinicaltrials-gov-version — Manage clinicaltrials gov version
clinical-trials-pp-cli clinicaltrials-gov-version — API and data versions. API version follows Semantic Versioning 2.0.0 Schema.stats — Data statistics
clinical-trials-pp-cli stats field-values — Value statistics of the study leaf fields.clinical-trials-pp-cli stats list-field-sizes — Sizes of list/array fields. To search studies by a list field size, use AREA[FieldName:size] search operator.clinical-trials-pp-cli stats size — Statistics of study JSON sizes.studies — Related to clinical trial studies
clinical-trials-pp-cli studies enums — Returns enumeration types and their values.clinical-trials-pp-cli studies fetch-study — Returns data of a single study.clinical-trials-pp-cli studies list — Returns data of studies matching query and filter parameters. The studies are returned page by page.clinical-trials-pp-cli studies metadata — Returns study data model fields.clinical-trials-pp-cli studies search-areas — Search Docs and their Search Areas.When you know what you want to do but not which command does it, ask the CLI directly:
clinical-trials-pp-cli which "<capability in your own words>"which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.
clinical-trials-pp-cli search "glioblastoma" --json --limit 20Searches the merged multi-source mirror and returns a bounded result set an agent can parse.
clinical-trials-pp-cli emerging cancer --jsonRanks the fastest-growing oncology trial categories with percent change.
clinical-trials-pp-cli compare "pembrolizumab" "nivolumab" --jsonCompares two drugs by trial counts, phases, and sponsors with RxNorm synonym resolution.
clinical-trials-pp-cli risk NCT07011732 --jsonReturns an explainable risk score with each contributing factor.
clinical-trials-pp-cli report "long covid" --format mdComposes search, emerging, hotspots, and sponsors into one markdown briefing.
No credentials required for the core. ClinicalTrials.gov, EU CTIS, OpenAlex, RxNorm, and MeSH need no key. OpenFDA and PubMed accept an optional key purely for higher rate limits.
Run clinical-trials-pp-cli doctor to verify setup.
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
Pipeable — JSON on stdout, errors on stderr
Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
clinical-trials-pp-cli studies list --agent --select id,name,statusPreviewable — --dry-run shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag
Read-only — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests
Commands that read from the local store or the API wrap output in a provenance envelope:
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.
Agents should treat the CLI's path resolver as part of the runtime contract:
Use --home <dir> for one invocation, or set CLINICAL_TRIALS_HOME=<dir> to relocate all four path kinds under one root.
Use per-kind env vars only when a specific kind must diverge: CLINICAL_TRIALS_CONFIG_DIR, CLINICAL_TRIALS_DATA_DIR, CLINICAL_TRIALS_STATE_DIR, CLINICAL_TRIALS_CACHE_DIR.
Resolution order is per-kind env var, --home, CLINICAL_TRIALS_HOME, XDG (XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME), then platform defaults.
config contains settings like config.toml and profiles. data contains credentials.toml, data.db, cookies, and auth sidecars. state contains persisted queries, jobs, and teach.log. cache contains regenerable HTTP/cache files.
Stored secrets live in credentials.toml under the data dir. Existing legacy config.toml secrets are read for compatibility and leave config.toml on the first auth write.
Run clinical-trials-pp-cli doctor --fail-on warn to surface path and credential-location warnings. agent-context exposes a schema v4 paths block for agents that need the resolved dirs.
For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags:
{
"mcpServers": {
"clinical-trials": {
"command": "clinical-trials-pp-mcp",
"env": {
"CLINICAL_TRIALS_HOME": "/srv/clinical-trials"
}
}
}
}Fleet precedence: an inherited per-kind env var overrides an explicit --home for that kind. Use CLINICAL_TRIALS_HOME or per-kind vars as durable fleet levers, and use --home only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing CLINICAL_TRIALS_HOME, or doctor will not find credentials left under the former root.
When you (or the agent) notice something off about this CLI, record it:
clinical-trials-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
clinical-trials-pp-cli feedback --stdin < notes.txt
clinical-trials-pp-cli feedback list --json --limit 10Entries are stored locally as feedback.jsonl under the resolved data dir. They are never POSTed unless CLINICAL_TRIALS_FEEDBACK_ENDPOINT is set AND either --send is passed or CLINICAL_TRIALS_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout | Default; write to stdout only |
file:<path> | Atomically write output to <path> (tmp + rename) |
webhook:<url> | POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
clinical-trials-pp-cli profile save briefing --json
clinical-trials-pp-cli --profile briefing studies list
clinical-trials-pp-cli profile list --json
clinical-trials-pp-cli profile show briefing
clinical-trials-pp-cli profile delete briefing --yesExplicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Parse $ARGUMENTS:
help, or --help → show clinical-trials-pp-cli --help outputinstall → ends with mcp → MCP installation; otherwise → see Prerequisites above--agent)go install github.com/mvanhorn/printing-press-library/library/health/clinical-trials/cmd/clinical-trials-pp-mcp@latestclaude mcp add clinical-trials-pp-mcp -- clinical-trials-pp-mcpclaude mcp listwhich clinical-trials-pp-cli
If not found, offer to install (see Prerequisites at the top of this skill).--agent flag:clinical-trials-pp-cli <command> [subcommand] [args] --agentclinical-trials-pp-cli <command> --help.© mvanhorn, 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
Just SKILL.md in cli-skills/pp-clinical-trials of mvanhorn/printing-press-library.
Open the folder on GitHubat commit d9a1696
Pp Clinical Trials 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 |
|---|---|---|---|---|---|---|
| Pp Clinical Trials this skillmvanhorn/printing-press-library | 2.1k | — | ~4.6k | Automated safety check: Notes | Apache-2.0 | |
| Clinical Trials Databasegoogle-deepmind/science-skills | 3.2k | 2 repos | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| Inclusion Criteria Genaipoch/medical-research-skills | 1.9k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Patient Recruitment Ad Genaipoch/medical-research-skills | 1.9k | — | ~2.7k | Automated safety check: Pass | MIT | |
| Clinicaltrials DBaipoch/medical-research-skills | 1.9k | — | ~762 | Automated safety check: Pass | MIT | |
| Treatment PlansK-Dense-AI/claude-scientific-writer | 2.4k | 1 repos | ~2.7k | Automated safety check: Pass | MIT |
google-deepmind/science-skills
Query ClinicalTrials.gov via APIv2. An agent skill from google-deepmind/science-skills.
aipoch/medical-research-skills
Generate and optimize clinical trial subject inclusion/exclusion criteria to balance scientific rigor with recruitment feasibility.
aipoch/medical-research-skills
Generate ethical, compliant, and patient-friendly recruitment advertisements for clinical trials.
aipoch/medical-research-skills
Query the ClinicalTrials.gov API v2 to search for clinical trials, retrieve detailed study protocols, and analyze recruitment status; use when you need to find trials by condition/drug, export…
K-Dense-AI/claude-scientific-writer
Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals.
maziyarpanahi/openmed
Searches ClinicalTrials.gov for studies by condition, intervention, and recruitment status using the modern v2 REST API with cursor (pageToken) pagination.
mvanhorn/printing-press-library
Desktop automation through the real Rust agent-desktop CLI, published in Printing Press through a small bridge.
mvanhorn/printing-press-library
Search, browse, and download Google Fonts from the terminal via the gfonts CLI.
mvanhorn/printing-press-library
The free, offline Trigger phrases: search 1688 for, find a factory on 1688 for, wholesale price on 1688 for, who is the cheapest supplier on 1688 for, compare 1688 suppliers for, use 1688, run 1688.
mvanhorn/printing-press-library
Inspect known Activity Japan plan IDs or URLs, compare dated prices and sessions, check language-sitemap coverage, and hand off to canonical booking pages.
mvanhorn/printing-press-library
Every Admin By Request portal action, plus a local SQLite mirror of audit, events, inventory and requests for ad-hoc...
mvanhorn/printing-press-library
macOS screen capture, window recording, GIF conversion, and agent evidence bundles from the terminal.
Works with
Categories
A multi-source clinical-trials intelligence system — aggregates, normalizes, and analyzes trials across ClinicalTrials.gov, EU CTIS, and biomedical sources, with an offline SQLite engine no…. Pp Clinical Trials is an agent skill from mvanhorn/printing-press-library.gov, EU CTIS, and biomedical sources, with an offline SQLite engine no single-registry tool has.
Pp Clinical Trials fits situations like: phrases: what clinical trials are running for; recruiting trials for; phase 3 trials for; compare these two drugs trials.
Run `npx skills add mvanhorn/printing-press-library --skill pp-clinical-trials -a claude-code`. Or copy the skill folder (cli-skills/pp-clinical-trials in mvanhorn/printing-press-library) into .claude/skills/pp-clinical-trials in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mvanhorn/printing-press-library --skill pp-clinical-trials -a codex`. Or copy the skill folder (cli-skills/pp-clinical-trials in mvanhorn/printing-press-library) into .agents/skills/pp-clinical-trials 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 mvanhorn/printing-press-library --skill pp-clinical-trials -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pp-clinical-trials, .gemini/skills/pp-clinical-trials, .github/skills/pp-clinical-trials and .opencode/skills/pp-clinical-trials in your project.
Going by SKILL.md and its folder, Pp Clinical Trials needs the command-line tools its instructions call (go, claude and npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Bash.
SKILL.md names 1 domain. As links in the text: semver.org. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Pp Clinical Trials is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pp Clinical Trials: Clinical Trials Database (google-deepmind/science-skills, 3.2k stars), Inclusion Criteria Gen (aipoch/medical-research-skills, 1.9k stars), Patient Recruitment Ad Gen (aipoch/medical-research-skills, 1.9k stars) and Clinicaltrials DB (aipoch/medical-research-skills, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mvanhorn (a GitHub user) maintains it in mvanhorn/printing-press-library, which has 2,056 GitHub stars. The repository holds 506 skills in this directory. The repository was last updated on October 9, 2026.
Source: mvanhorn/printing-press-library on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.