CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-clinical-trial-design

Strategic clinical trial design feasibility assessment. Analyzes 6 dimensions (endpoint, population, comparator, effect size, duration, regulatory pathway) using precedent trials and FDA guidance. Produces enrollment projections, endpoint recommendations, and approval-pathway analysis. Use for trial-protocol design, power/sample-size estimation, comparator selection, and FDA submission strategy. Driven by precedent-based reasoning rather than first-principles math.

Quality

76%

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 ./plugin/skills/tooluniverse-clinical-trial-design/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 body is well-organized domain guidance with concrete tool mappings and a sensible reasoning-first workflow, but the progressive-disclosure layer is broken — all six referenced files are missing — and the workflow lacks validation checkpoints. Code examples are near-executable but contain tool-name inconsistencies between sections.

Suggestions

Bundle the six referenced files (REPORT_TEMPLATE.md, STUDY_DESIGN_PROCEDURES.md, WORKFLOW_DETAILS.md, BEST_PRACTICES.md, EXAMPLES.md, QUICK_START.md) into the skill's references directory; currently every 'See X for detailed steps' path in the body is a dead end, leaving the 14-section report template and per-path procedures unreachable.

Add validation checkpoints and fallback loops to the workflow: what to do when a tool returns no hits (e.g., alternate disease names, looser filters), and cross-checking enrollment projections and effect-size assumptions against the precedent trials found in PATH 4 before writing them into the report.

Tighten the body: merge the 'LOOK UP DON'T GUESS' block into the preceding 'look them up from precedent trials' paragraph, move the version/date block into a reference file, and fix the Quick Start's tool-name inconsistencies (ClinicalTrials_search_studies vs search_clinical_trials) so the example matches the tool reference tables.

DimensionReasoningScore

Conciseness

The body is mostly dense domain-specific guidance, but it duplicates itself ('Look them up from precedent trials and FDA guidance — do not derive them from first principles' is restated as the 'LOOK UP DON'T GUESS' block), carries a dated version block ('Version 1.0.0', 'Last Updated: February 2026'), and inlines a generic ClinicalTrials.gov pagination script whose details it simultaneously defers to the data-wrangling skill. This fits anchor 3 ('mostly efficient but could be tightened') rather than 4, where only minor trimming would be needed.

3 / 5

Actionability

Concrete tool names are mapped to each of the 6 research paths and the Quick Start is near-executable Python, but the example calls tu.tools.ClinicalTrials_search_studies and OpenTargets_get_associated_phenotypes_by_disease_efoId while the tool reference tables list search_clinical_trials and different OpenTargets methods, so the naming is inconsistent and not reliably copy-paste ready; the example also trails off at 'Compile into feasibility report...'. Mostly executable with minor gaps fits anchor 4; anchor 5 would require consistent, complete, common-case-covering code.

4 / 5

Workflow Clarity

The macro sequence is present and sensible (answer 4 reasoning questions, run 6 parallel paths, build the report first and update progressively), but there are no validation checkpoints or feedback loops anywhere — no 'if a tool returns no hits, try X', no cross-check of enrollment projections against precedent trial enrollment — and the per-path step sequences are deferred to a file that is not in the bundle. Anchor 3 ('sequence present but checkpoints missing or implicit') fits; anchor 4 requires most checkpoints to be present.

3 / 5

Progressive Disclosure

The inline structure would be excellent — clearly signaled, one-level-deep references plus a reference table for REPORT_TEMPLATE.md, STUDY_DESIGN_PROCEDURES.md, WORKFLOW_DETAILS.md, BEST_PRACTICES.md, EXAMPLES.md, and QUICK_START.md — but the bundle contains no files at all: every 'See X for detailed steps / full templates / complete workflow' is a dead end, leaving the skill an overview whose detail layer is entirely missing. Scored against the actual (empty) bundle structure, navigation fails outright, fitting anchor 2; anchor 3 requires the structure to be only imperfectly organized, not broken.

2 / 5

Total

12

/

20

Passed

Description

88%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 strong description: concrete, third-person, comprehensive action coverage with an explicit 'Use for...' trigger clause. The only weaknesses are a few missing natural trigger variations (sample size calculation, Phase 1/2 design, biomarker trial) and mild trigger overlap with the sibling protocol-writing skill.

DimensionReasoningScore

Specificity

The description enumerates concrete actions in third-person voice: 'Analyzes 6 dimensions (endpoint, population, comparator, effect size, duration, regulatory pathway)', 'Produces enrollment projections, endpoint recommendations, and approval-pathway analysis'. Coverage is comprehensive within the trial-design domain with no noticeable gaps, matching the anchor for multiple specific concrete actions; anchor 4 would require minor coverage gaps that are not evident.

5 / 5

Completeness

It explicitly answers both: what ('Analyzes 6 dimensions... Produces enrollment projections, endpoint recommendations, and approval-pathway analysis') and when ('Use for trial-protocol design, power/sample-size estimation, comparator selection, and FDA submission strategy') with concrete trigger phrases, exactly matching the anchor-5 example pattern. Not 4, because the 'when' clause is explicit and specific rather than improvable.

5 / 5

Trigger Term Quality

Natural phrases like 'trial-protocol design', 'power/sample-size estimation', 'comparator selection', and 'FDA submission strategy' are present, but common variations users would say — 'sample size calculation', 'Phase 1/2 design', 'biomarker trial' — appear only in the body, not the description. Good coverage with a few natural terms missing fits between anchors 3 and 4, noticeably above the midpoint.

4 / 5

Distinctiveness Conflict Risk

The feasibility-assessment niche is clear and 'Driven by precedent-based reasoning' distinguishes its approach, but 'Use for trial-protocol design' overlaps with the sibling tooluniverse-clinical-trial-protocol skill, which is the one that actually writes protocols. Mostly distinct with minor overlap risk against a closely related skill fits anchor 4; anchor 5 would require essentially no trigger collision.

4 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-clinical-trial-design/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.