clinicaltrials-skill

Submit compact ClinicalTrials.gov API v2 requests for study search, metadata, enums, search areas, and field statistics. Use when a user wants concise ClinicalTrials.gov summaries

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, executable, well-organized skill body that gives Claude everything needed to call the client correctly with no filler. The referenced script exists in the bundle as claimed.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with no padding or explanations of concepts Claude already knows; every line (operating rules, input/output spec, one executable example) earns its place, matching the score-5 anchor.	5 / 5
Actionability	Provides a copy-paste-ready bash invocation plus three concrete JSON input examples and an explicit action/params schema, fully covering the common cases per the score-5 anchor.	5 / 5
Workflow Clarity	As a single-purpose read-only API client, the action is unambiguous and the simple-skill exception applies; failure handling ('ok=false with error.code and error.message') and save_raw path reporting are explicit, with no destructive/batch validation gap.	5 / 5
Progressive Disclosure	Under 50 lines with the only bundle file (scripts/clinicaltrials_client.py) clearly referenced and a References section confirming no further files are needed; well-organized sections satisfy the score-5 simple-skill anchor.	5 / 5
	Total	20 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, third-person description that clearly states capabilities and an explicit trigger clause. Trigger-term coverage is strong but could add a few natural synonyms.

Suggestions

Add natural synonyms such as 'clinical trials', 'trial search', or 'clinical studies' to broaden trigger-term coverage.

Consider naming the data domain in the trigger (e.g., 'Use when a user wants concise clinical trial search results or study summaries') to sharpen the when-clause.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'study search, metadata, enums, search areas, and field statistics' — giving comprehensive coverage of the API's capabilities, matching the score-5 anchor.	5 / 5
Completeness	Explicitly states both what it does ('Submit compact ClinicalTrials.gov API v2 requests for...') and when to use it ('Use when a user wants concise ClinicalTrials.gov summaries'), satisfying the score-5 anchor.	5 / 5
Trigger Term Quality	Natural terms like 'ClinicalTrials.gov', 'study search', and 'concise ... summaries' are present, but common synonyms such as 'clinical trials', 'trial search', or 'clinical studies' are missing, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The ClinicalTrials.gov API v2 niche is specific with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/life-science-research/skills/clinicaltrials-skill/SKILL.md
Commit: 1e28582

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.