clinicaltrials-database

Query ClinicalTrials.gov via API v2. Search trials by condition, drug, location, status, or phase. Retrieve trial details by NCT ID, export data, for clinical research and patient matching.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/clinicaltrials-database/SKILL.md

Quality

Content

75%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 highly actionable with executable code and solid reference structure, but it is longer than necessary and could be tightened by reducing repeated import boilerplate and trimming overview duplication.

Suggestions

Consolidate the repeated `from scripts.query_clinicaltrials import ...` boilerplate by stating the import once and showing only the call in subsequent examples.

Trim the Overview and 'When to Use' sections to avoid restating the frontmatter description and to reduce the eight overlapping use-case bullets.

Move the bulk of the ten inline capability examples' detail into references/api_reference.md, keeping SKILL.md a leaner overview with a few representative examples.

Dimension	Reasoning	Score
Conciseness	Mostly task-focused and free of basic-concept padding, but the ~500-line body repeats the same import boilerplate across ten capability sections and could be consolidated; the Overview/When-to-Use sections restate the description.	3 / 5
Actionability	Provides copy-paste-ready, executable Python for every common case (search by condition/intervention/location/sponsor, retrieve by NCT ID, pagination, CSV export), backed by a real helper script with matching function signatures.	5 / 5
Workflow Clarity	Sequences are clear and the Best Practices section supplies explicit feedback loops (429 rate-limit -> sleep -> retry, raise_for_status, missing-data .get() guards); the pagination batch path has a stop condition and max_pages safety, though completeness verification of bulk results is only implicit.	4 / 5
Progressive Disclosure	Good structure with well-signaled, one-level-deep references to real files (scripts/query_clinicaltrials.py, references/api_reference.md) and a clear 'load when...' cue; minor gap is that the body itself is fairly long with ten inline capability sections rather than a leaner overview.	4 / 5
	Total	16 / 20 Passed

Description

75%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 concrete and well-targeted to a distinct niche, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness. Specificity is strong with minor generic spots.

Suggestions

Add an explicit 'Use when...' trigger clause naming natural user phrases (e.g., 'Use when searching ClinicalTrials.gov, finding recruiting trials by condition or location, or looking up a trial by NCT ID').

Make the export capability concrete by naming the output format (e.g., 'export trial data to CSV').

Drop the trailing 'for clinical research and patient matching' use-case fragment or fold it into the explicit 'when' clause to avoid vague padding.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (search by condition, drug, location, status, phase; retrieve by NCT ID; export data), but 'export data' is generic with no format specified and the trailing 'for clinical research and patient matching' is use-case fluff rather than a capability.	4 / 5
Completeness	The 'what' is clear and concrete, but there is no explicit 'Use when...' trigger clause; 'for clinical research and patient matching' only weakly implies the when, so completeness is capped at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Strong natural keywords users would say (ClinicalTrials.gov, clinical trials, condition, drug, location, NCT ID, patient matching), though a few common synonyms or phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	ClinicalTrials.gov / NCT ID is a clear, narrow niche with distinct triggers and minimal risk of conflicting with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (505 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/clinicaltrials-database/SKILL.md
Commit: d5ae560

Reviewed: 1 day 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.