clinicaltrials-db

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 results, or verify study details by NCT ID.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/clinicaltrials-db/SKILL.md

Quality

Content

71%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.

The body is well-structured with executable code and good progressive disclosure, but it carries redundant restatements of the description and script internals that reduce token efficiency. Trimming the overlapping sections would lift conciseness without losing clarity.

Suggestions

Remove or shrink the "Key Features" section, which duplicates the frontmatter description and the "When to Use" bullets.

Drop the "Implementation Details" parameter list since those parameters are already documented in the bundled script and references/api_reference.md.

Add a brief note on handling None returns and pagination (pageToken) so the example workflow covers error/edge cases explicitly.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the "Key Features" section largely restates the description and "Implementation Details" re-explains API parameters already present in the bundled script, so the body could be tightened.	3 / 5
Actionability	Provides a concrete, copy-paste-ready Python example importing the real functions with arguments covering both search and detail retrieval, with only a minor gap around the returned data shape.	4 / 5
Workflow Clarity	The example sequences the two main actions (search then get-by-NCT) clearly with comments, but it does not address handling None returns or pagination, leaving minor validation gaps.	4 / 5
Progressive Disclosure	The body is a clear overview with well-signaled, one-level-deep references to references/api_reference.md and scripts/query_clinicaltrials.py (both verified to exist), keeping bulk API detail in the reference file.	5 / 5
	Total	16 / 20 Passed

Description

87%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.

The description is strong: it answers both what and when with concrete, natural-language triggers tied to a specific, distinctive API. Minor gains are possible by broadening trigger synonyms and sharpening the "analyze" action.

Dimension	Reasoning	Score
Specificity	Names the API backend and several concrete actions — "search for clinical trials", "retrieve detailed study protocols", and "analyze recruitment status" — but "analyze" is slightly thin, leaving minor coverage gaps rather than fully comprehensive breadth.	4 / 5
Completeness	Clearly states what ("Query the ClinicalTrials.gov API v2 to search... retrieve... and analyze...") and when ("use when you need to find trials by condition/drug, export results, or verify study details by NCT ID") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrases like "find trials by condition/drug", "export results", and "verify study details by NCT ID" with good coverage, though it lacks synonyms/variants beyond the primary terms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (ClinicalTrials.gov API v2) with distinct triggers around trial search and NCT ID lookup, posing minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: aipoch/medical-research-skills
Path: scientific-skills/Evidence Insight/clinicaltrials-db/SKILL.md
Commit: 63c61d3

Reviewed: 3 hours 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.