CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clinicaltrials-gov-parser

Monitor and summarize competitor clinical trial status changes from ClinicalTrials.gov.

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/clinicaltrials-gov-parser/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 core technical content (parameters, CLI, API methods, references) is accurate and verified against the bundle, but it is buried under roughly 40% generic template boilerplate, and the documented workflow is abstract policy rather than a concrete operational sequence. The result is a mid-scoring skill whose useful material would shine after aggressive trimming.

Suggestions

Delete or collapse the boilerplate sections — Security Checklist, Risk Assessment, Lifecycle Status, Evaluation Criteria/Test Cases — and merge the six overlapping policy sections (Error Handling, Input Validation, Failure Handling, Output Contract, User Checkpoints, Quick Validation) into one short section; this is the single largest conciseness win.

Rewrite the Workflow as the concrete operational sequence (run the Quick Check → search/get via CLI → check_status_changes → report) with the audit commands inline as validation checkpoints, instead of abstract policy steps.

Fix factual mismatches: correct '--output' values to the actual json/table (and json/text for report) formats and either ship a requirements.txt or state the single dependency ('pip install requests').

DimensionReasoningScore

Conciseness

The body is noticeably padded: a boilerplate 'Security Checklist' of 12 unchecked generic boxes, 'Risk Assessment', 'Lifecycle Status' (including a stale 'Next Review Date: 2026-03-06'), 'Evaluation Criteria'/'Test Cases' with placeholders like 'Standard input → Expected output', and at least six overlapping policy sections (Error Handling, Input Validation, Failure Handling, Output Contract, User Checkpoints, Quick Validation) that repeat the same fallback/stop/ask guidance three times over. This matches 'Noticeably verbose; several unnecessary explanations or padded sections'; it is not a 1 because there is no explanation of concepts Claude already knows and the core usage material is dense and useful.

2 / 5

Actionability

Guidance is mostly executable and verified against the bundle: 'python -m py_compile scripts/main.py', 'python scripts/main.py --help', the CLI Usage block (search/get/monitor/report subcommands all exist in scripts/main.py), and the Python API example whose class and methods match the implementation. It is not a 5 because of minor inaccuracies — the Parameters table documents '--output (json, csv)' while the actual CLI accepts json/table (or json/text), and 'pip install -r requirements.txt' is referenced with no requirements.txt in the bundle.

4 / 5

Workflow Clarity

The 'Workflow' section lists a five-step sequence with a fallback loop ('If execution fails or inputs are incomplete, switch to the fallback path') and there is a Quick Check, but the steps are abstract policy statements ('Confirm the user objective...', 'Return a structured result...') rather than the concrete operational sequence (search → get → check_status_changes → report) with validation commands. This matches 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit'; the concrete audit commands exist but are not wired into the workflow steps, keeping it below 4.

3 / 5

Progressive Disclosure

Scored against the actual bundle: the three referenced files (references/api-docs.md, references/status-codes.md, references/examples.md) all exist, are one level deep, and are clearly signaled in a dedicated References section; the packaged script is referenced by path. This matches 'Good structure; most content is appropriately placed; references mostly clear; minor organization gaps'. It is not a 5 because SKILL.md itself is not a lean overview — large policy/boilerplate sections are inlined that belong in reference files (or nowhere), slightly burying the navigation.

4 / 5

Total

13

/

20

Passed

Description

53%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 concise, domain-specific description with a clear 'what', but it entirely lacks a 'when to use' trigger clause and underuses natural search phrasings users would say. It is serviceable but sits squarely at the midpoint of the rubric.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user mentions ClinicalTrials.gov, NCT numbers, trial status/recruitment updates, or competitor pipeline monitoring.'

Include natural synonyms and identifiers users actually type — 'NCT number', 'trial results', 'enrollment status', 'pharma competitive intelligence' — to improve trigger term coverage.

Enumerate one or two more concrete actions (e.g., 'search trials by sponsor or condition, check status changes, generate summary reports') to raise specificity.

DimensionReasoningScore

Specificity

The description names the domain ('competitor clinical trial status changes from ClinicalTrials.gov') and exactly two concrete actions — 'Monitor' and 'summarize' — matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because it does not list several specific actions (e.g., search, track enrollment, generate reports) and not a 2 because the actions are not generic — they are tied to a concrete data source and object.

3 / 5

Completeness

The 'what' is clear (monitor and summarize competitor trial status changes), but there is no 'Use when...' clause or any equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not a 2 because the 'what' is specific rather than vague; it cannot be 4 without an explicit 'when' component.

3 / 5

Trigger Term Quality

Relevant natural keywords are present ('clinical trial', 'trial status', 'ClinicalTrials.gov', 'competitor'), but common variations a user would actually say are missing: NCT numbers, trial results, recruitment/enrollment status, pharma competitive intelligence. This matches 'Some relevant keywords but missing common variations or synonyms'; it falls short of 4's 'good keyword coverage' because several frequently used phrasings are absent.

3 / 5

Distinctiveness Conflict Risk

'ClinicalTrials.gov' and 'competitor clinical trial status changes' define a clear niche with distinct triggers, so overlap risk is limited to closely related medical-research skills (e.g., a PubMed or FDA parser from the same collection) — matching 'Mostly distinct; minor overlap risk with closely related skills'. It is not 5 because 'monitor and summarize' without unique trigger phrasings leaves some ambiguity against sibling biomedical-monitoring skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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-gov-parser/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.