Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mkurman/clinical-trials-database
Query ClinicalTrials.gov via APIv2.
Passed 3 of 8 test cases with the skill, and 1 of 8 without it.
and 5 more in the full report
4 fixed3 passed either way15 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before executing any search query on the clinical database, what file check or user notification step must be performed if running in a fresh workspace directory where LICENSE_NOTIFICATION.txt is missing?
| Checked | Without skill | With skill |
|---|---|---|
| Prominently notifies the user to check terms at https://clinicaltrials.gov/ when missing LICENSE_NOTIFICATION.txt. | Missed | Passed |
| Writes LICENSE_NOTIFICATION.txt recording the notification text and timestamp. | Missed | Passed |
The instructions your model reads when the skill loads.
uv: Read the uv skill and follow its Setup instructions to ensure
uv is installed and on PATH.Access worldwide clinical trial data from ClinicalTrials.gov via the REST API
v2. The CLI script at scripts/clinical_trials_api.py wraps the API with
dedicated flags for common filters (phase, age group, status, intervention,
sponsor, etc.) so you rarely need to construct raw queries.
--fields — trial JSON records can be very large; restrict
to the data points you need.--count-total first — check result volume before fetching all
records.--limit with --page-token to
iterate.Trial JSON records can be very large. Always use the --fields parameter to
restrict the response to only the data points you need. After writing to file,
read only the fields you need rather than the entire file.
test cases passed, vs 1 / 8 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.