CtrlK
BlogDocsLog inGet started
Tessl Logo

clinical-trials-database

Query ClinicalTrials.gov via APIv2. Use when you want to search for trials by condition, drug, location, status, or phase; retrieve trial details by NCT ID; check eligibility/inclusion criteria; count trials across conditions or time periods; identify a sponsor's trial portfolio; find recruiting trials for patient matching.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-3

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

A well-structured, highly actionable API skill body with strong progressive disclosure (real, clearly-signaled reference files) and copy-paste-ready examples. The main gaps are redundant '--fields' warnings that hurt conciseness and the absence of an explicit validation/feedback loop for batch fetches, which caps workflow clarity.

Suggestions

Consolidate the repeated '--fields' guidance: state the rule once in Core Rules and reference it from the Context Efficiency Warning instead of restating it, to reduce redundancy.

Add an explicit validation checkpoint for batch workflows, e.g. after '--count-total', instruct to inspect totalCount and adjust '--limit'/filters before fetching, and note how to handle an empty or error response.

Consider moving the full per-flag enum value lists (status, phase, age-group, study-type) into references/clinical_trials_api.md and keeping only the most common values inline, since they already exist in the reference.

DimensionReasoningScore

Conciseness

Mostly efficient — flag references, enum values, and worked examples all earn their tokens — but the '--fields always' guidance is repeated across Core Rules, the Context Efficiency Warning, the Response Layout Summary, and the flag reference, and the Context Efficiency Warning largely duplicates the Core Rules; could be tightened. Not a 3 due to this redundancy; not a 1 because nothing explains concepts Claude already knows.

2 / 3

Actionability

Fully executable, copy-paste-ready commands with multiple worked examples (cystic fibrosis, atezolizumab, NCI, pancreatic, NYC), a complete flag reference with concrete enum values, and explicit output paths — matching the score-3 anchor.

3 / 3

Workflow Clarity

Core Rules give a clear recommended sequence ('--count-total first', then fetch with '--fields', paginate with '--page-token') and pagination is well documented, and the prerequisite license-check has a conditional checkpoint; however there is no explicit validation/error-recovery feedback loop for the batch-fetch workflow, which the rubric flags for batch operations, so it caps at 2 rather than 3.

2 / 3

Progressive Disclosure

SKILL.md is an overview with common commands inline and pushes detail to two real, correctly-named, one-level-deep reference files (references/studies_schema.md and references/clinical_trials_api.md, both present in the bundle), clearly signaled via TIP callouts, inline 'See references/...' notes, and a References section — matching the score-3 anchor.

3 / 3

Total

10

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 strong description: comprehensive concrete capabilities, explicit 'Use when' triggers, and a distinctive niche. The only weakness is the second-person 'you want to' phrasing in the trigger clause, which violates the third-person-voice guideline and caps specificity.

Suggestions

Rewrite the trigger clause in third person to avoid the second-person penalty, e.g. 'Use when searching for trials by condition, drug, location, status, or phase; retrieving trial details by NCT ID; ...' (drop 'you want to').

Consider adding 'ClinicalTrials.gov' / 'clinical trials' as explicit trigger nouns near the start so the literal keyword users type appears early.

DimensionReasoningScore

Specificity

Lists many concrete actions ('search for trials by condition, drug, location, status, or phase; retrieve trial details by NCT ID; check eligibility/inclusion criteria; count trials...; identify a sponsor's trial portfolio; find recruiting trials for patient matching'), which is otherwise a 3, but the trigger clause 'Use when you want to...' uses second-person voice ('you'), which the rubric penalizes by reducing specificity by 1.

2 / 3

Completeness

Explicitly answers both what ('Query ClinicalTrials.gov via APIv2') and when ('Use when you want to search for trials by...; retrieve trial details...; check eligibility...'), with an explicit trigger clause — the score-3 pattern.

3 / 3

Trigger Term Quality

Strong coverage of natural terms users would say — 'trials', 'condition', 'drug', 'location', 'status', 'phase', 'NCT ID', 'eligibility/inclusion criteria', 'sponsor', 'recruiting trials', 'patient matching' — matching the breadth of the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

ClinicalTrials.gov / NCT IDs / trial portfolios / eligibility criteria form a clear, distinctive niche with triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
google-deepmind/science-skills
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.