CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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 tight, fully operational SKILL.md: it documents the script interface completely with copy-paste examples, output shapes, and failure handling, while adding zero filler. The simple-skill exceptions in the rubric apply cleanly, so workflow clarity and progressive disclosure earn top marks despite no multi-step workflow or external reference files.

DimensionReasoningScore

Conciseness

The body is purely operational ("Use `scripts/clinicaltrials_client.py` for all ClinicalTrials.gov v2 calls", "Study searches are better with `max_items=10` and `max_pages=1`") with zero background explanation of what ClinicalTrials.gov is; every line teaches non-obvious rules or I/O shape, matching the lean/efficient anchor.

5 / 5

Actionability

An executable bash invocation plus three copy-paste-ready JSON payloads (studies with filters, metadata, field_values) covering the common cases, a full action list, all optional fields, and explicit failure semantics ("Failure returns `ok=false` with `error.code` and `error.message`"); not 4 because nothing concrete is missing for the documented actions.

5 / 5

Workflow Clarity

The single action (pipe one JSON object to the script) is unambiguous, and the rubric's simple-skill exception applies; error feedback is defined via the failure channel, and re-run/truncation rules guard long conversations. Not a destructive or batch operation, so no validation cap applies.

5 / 5

Progressive Disclosure

Under 50 lines with well-organized sections (Operating rules, Execution behavior, Input, Output, Execution, References); the body correctly states no additional references are required, and the one referenced bundle file, `scripts/clinicaltrials_client.py`, exists, so the simple-skill exception for a 5 holds.

5 / 5

Total

20

/

20

Passed

Description

76%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 names the API version and five concrete capability areas with an explicit 'Use when' clause. Its main weakness is trigger coverage: the when-clause mentions only 'concise summaries' and lacks the natural phrasing variations users would use for the other capabilities.

Suggestions

Broaden the trigger clause to cover all capabilities, e.g. 'Use when the user asks about clinical trials, trial statuses, eligibility criteria, or ClinicalTrials.gov data' rather than only 'concise ClinicalTrials.gov summaries'.

Add natural synonyms users actually say — 'clinical trials', 'trial search', 'trial status', 'recruiting studies' — to improve trigger term coverage.

Mirror the field-statistics and enum-introspection capabilities in the when-clause so those use cases also trigger the skill.

DimensionReasoningScore

Specificity

"Submit compact ClinicalTrials.gov API v2 requests for study search, metadata, enums, search areas, and field statistics" names five concrete, distinct actions in third-person voice, matching the comprehensive-coverage anchor; not 4 because no capability area is conspicuously missing.

5 / 5

Completeness

Both what ("Submit compact ClinicalTrials.gov API v2 requests for study search, metadata, enums, search areas, and field statistics") and when ("Use when a user wants concise ClinicalTrials.gov summaries") are present, but the when-clause covers only summaries and omits the metadata/enums/field-statistics use cases, fitting the anchor where 'when' could be more explicit or specific rather than 5.

4 / 5

Trigger Term Quality

"ClinicalTrials.gov", "study search", and "summaries" are relevant, but natural variations users would actually say ("clinical trials", "trial status", "trial lookup", "medical research studies") are absent, matching the some-keywords-but-missing-synonyms anchor rather than 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

"ClinicalTrials.gov API v2" is a clearly defined niche with distinct triggers, so the risk of firing for an unrelated skill is minimal; not 4 because no closely related overlapping skill domain is identifiable.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.