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

77%

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

72%

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

The content is highly actionable with verified executable examples and good progressive disclosure into real bundle files, but it carries some generic boilerplate and lacks explicit validation checkpoints in the bulk-retrieval workflow.

Suggestions

Trim generic error-handling and 'safe navigation' boilerplate that Claude already knows, keeping only API-specific guidance to improve conciseness.

Add an explicit validation checkpoint in the pagination/bulk-export workflow (e.g., verify totalCount against retrieved count and confirm rate-limit handling before continuing) to raise workflow clarity.

Consolidate the repeated 'Common use cases' bullet lists or move them to the reference file to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete executable examples, but includes generic boilerplate Claude already knows (e.g., the 'Always implement proper error handling' try/except block) and repetitive use-case lists that could be tightened; not padded enough for 1, but not fully lean for 3.	2 / 3
Actionability	Provides numerous complete, copy-paste-ready code examples; every referenced helper (search_studies, get_study_details, search_with_all_results, extract_study_summary) is verified present in the bundled script.	3 / 3
Workflow Clarity	A clear Quick Start and a rate-limit retry feedback loop exist, but the bulk pagination/export path has no explicit validation checkpoint, and the batch-operations guideline caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The body is a well-organized overview that points one level deep to real, clearly-signaled bundle files (references/api_reference.md and scripts/query_clinicaltrials.py), both verified to exist.	3 / 3
	Total	10 / 12 Passed

Description

82%

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 specific and distinctive with strong natural trigger terms, but it lacks an explicit 'Use when...' trigger clause, leaving the 'when to use' dimension only implied and capping completeness at 2.

Suggestions

Add an explicit trigger clause such as 'Use when searching ClinicalTrials.gov, finding recruiting trials by condition/drug/location, or retrieving study details by NCT ID' to satisfy the completeness dimension.

Keep the existing concrete action list but convert the trailing 'for clinical research and patient matching' purpose phrase into an explicit 'when' framing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Search trials by condition, drug, location, status, or phase', 'Retrieve trial details by NCT ID', 'export data' — matching the anchor for listing several specific actions.	3 / 3
Completeness	The 'what' is clear, but the 'when' is only implied by 'for clinical research and patient matching' with no explicit 'Use when...' trigger clause, so completeness is capped at 2 per the guideline.	2 / 3
Trigger Term Quality	Natural user-facing terms are well covered (condition, drug, location, status, phase, NCT ID, clinical research, patient matching); not merely technical jargon.	3 / 3
Distinctiveness Conflict Risk	ClinicalTrials.gov and NCT ID anchor a clear niche unlikely to trigger for unrelated skills, matching the distinct-trigger anchor.	3 / 3
	Total	11 / 12 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: f627ab5

Reviewed: about 8 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.