CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clinical-trial-finder

Find clinical trials for a gene, variant, or condition from ClinicalTrials.gov + EUCTR, with FHIR R4 output

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/clinical-trial-finder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 organized with a strong safety/agent-boundary framing and concrete parameter documentation, but it reads as a design-rationale document rather than an operating manual: no command invocation, script path, or sequenced workflow tells the agent how to actually dispatch and use the skill. Rationale padding and dated claims also cost token efficiency.

Suggestions

Add a usage section with at least one copy-paste-ready invocation example (e.g. the CLI command for a condition query and for --gene / --rsid modes).

Replace the implicit workflow with an explicit ordered sequence (validate input → run query → present results with disclaimer and TERMINATED/WITHDRAWN flags), with a validation checkpoint on inputs.

Trim citation/regulatory rationale to one line per decision and move time-sensitive claims (2026 adoption status, API key requirements) into a clearly dated notes section.

DimensionReasoningScore

Conciseness

Every bullet is operational rather than tutorial-style, but many carry rationale padding the dispatching agent does not need — e.g. "the authoritative US registry mandated by FDAAA 801 (2007) and mirrored by WHO ICTRP. Reference: Zarin et al., NEJM 2011; 364:852-860". Time-sensitive claims ("R5 is in early adoption as of 2026", "DisGeNET requires a commercial API key as of 2026") further penalize per the guidelines since they are not in a deprecated/old-patterns section. This is 'mostly efficient but could be tightened', above anchor 2's several padded sections but below anchor 4.

3 / 5

Actionability

Parameters are documented concretely (--max-results, --status, --gene, --rsid, --country, --euctr, --fhir, --ot-min-score, --ot-max-diseases), but there is no invocation example, script path, or CLI command anywhere in the body — the agent is never shown how to actually call the skill. This is more than anchor 1's pure description but only 'high-level hints missing the specific steps to execute', matching anchor 2.

2 / 5

Workflow Clarity

The body implies a dispatch workflow through Input Validation, Safety Rules, and Agent Boundary sections, but no sequenced steps (validate input → invoke script → present results with disclaimer) and no agent-side validation checkpoints exist; retry/backoff and FHIR inline validation are described as script-internal behavior, not workflow checkpoints. This matches anchor 3: sequence present but implicit, checkpoints missing.

3 / 5

Progressive Disclosure

The skill is a single self-contained file with clear section headers (Domain Decisions, Safety Rules, Agent Boundary, Input Validation) and scannable bullets; no bundle files exist, so navigation is trivial. It falls short of anchor 5 only because the ~80-line rationale-heavy Domain Decisions section could have been slimmed or split into a design-notes reference; structure is otherwise well placed, matching anchor 4.

4 / 5

Total

12

/

20

Passed

Description

70%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, concrete description that names the action, input types, sources, and output format, with good natural trigger terms and a distinct niche. Its main weakness is the complete absence of an explicit 'Use when...' trigger clause, which caps completeness and leaves invocation conditions only weakly implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to find, search, or list clinical trials, research studies, or registered studies for a gene, variant, or condition.'

Include a few common synonyms users would say (e.g. 'research studies', 'trial registry', 'rsID') to strengthen trigger-term coverage.

Optionally mention the HTML report and CSV outputs so the 'what' fully reflects the skill's deliverables.

DimensionReasoningScore

Specificity

"Find clinical trials" names the action, "for a gene, variant, or condition" specifies the inputs, and "from ClinicalTrials.gov + EUCTR, with FHIR R4 output" names sources and output format. This sits above anchor 3 (only 1-2 concrete actions, not comprehensive) but below anchor 5, which would also cover the HTML report and CSV outputs documented in the body; only one action verb is present, so this is 'several specifics with minor gaps' rather than comprehensive.

4 / 5

Completeness

The 'what' is clear and concrete (find trials for a gene/variant/condition across two registries with FHIR R4 output), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the input list only weakly implies 'when'. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

"clinical trials", "gene", "variant", "condition", and "ClinicalTrials.gov" are terms users would naturally say when needing this skill. It falls short of anchor 5 because common variations like "research study", "medical research", "registry", or "rsID" are absent, but coverage is well beyond anchor 3's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The clinical-trial search niche with named registries (ClinicalTrials.gov + EUCTR) and a specific output format (FHIR R4) is unambiguous and unlikely to fire for any other skill. Neighboring anchor 4 ('minor overlap risk with closely related skills') does not fit — there are no closely related competing triggers.

5 / 5

Total

16

/

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/clinical-trial-finder/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.