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

77%

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 ./plugins/tooluniverse/skills/tooluniverse-clinical-trial-design/SKILL.md

The canonical home for this skill is tooluniverse-clinical-trial-design in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

60%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 delivers genuinely actionable guidance — a reasoning-first workflow, per-path tool mappings, an executable Quick Start, and go/no-go score thresholds — but it is held back by duplicated/verbose sections, a tool-name inconsistency in the Quick Start, and a broken progressive-disclosure structure where all six referenced detail files are missing from the bundle. Fixing the missing bundle files and trimming the duplicated template/tree sections would lift it substantially.

Suggestions

Ship the six referenced files (REPORT_TEMPLATE.md, STUDY_DESIGN_PROCEDURES.md, WORKFLOW_DETAILS.md, BEST_PRACTICES.md, EXAMPLES.md, QUICK_START.md) in the bundle, or remove the citations and inline only what is needed — every current reference currently resolves to nothing.

Trim duplication to tighten token budget: cut the 14-section listing and the ASCII path tree (both duplicate REPORT_TEMPLATE.md and the per-path tool reference), and drop or relocate the Version Information section since time-sensitive dates/versions penalize conciseness.

Fix the Quick Start tool-name inconsistency (`search_clinical_trials` in the tool reference vs `tu.tools.ClinicalTrials_search_studies` in the code) and add a validation step for the no-data case (what to do when a tool returns no precedent trials before writing report sections).

DimensionReasoningScore

Conciseness

The body is mostly dense and useful (reasoning questions, evidence-grading table, per-path tool lists), but several sections are padded or duplicated: the 14-section listing duplicates REPORT_TEMPLATE.md content, the ASCII path tree duplicates the per-path tool reference, 'When to Use This Skill' repeats the description's triggers, and a Version Information section carries time-sensitive dates/versions ("February 2026", "ToolUniverse 0.5+") outside any deprecated section. Not a 4: more than minor trimming is needed; not a 2: most content is substantive rather than filler.

3 / 5

Actionability

Concrete tool names are mapped to each of the 6 research paths, the Quick Start is executable Python with expected-result caveats, and the report-first procedure gives explicit steps. Not a 5: there is a tool-name inconsistency — the tool reference lists `search_clinical_trials` but the Quick Start code calls `tu.tools.ClinicalTrials_search_studies` — and the report sections lack fillable specifics beyond names. Not a 3: guidance is genuinely executable, not pseudocode.

4 / 5

Workflow Clarity

A clear sequence is laid out: answer 4 reasoning questions first, then execute 6 parallel research paths, create the report first and update progressively, with feasibility-score thresholds (>=75 proceed, 50-74 moderate, <50 de-risk) acting as explicit go/no-go checkpoints. Not a 5: there is no validation/error-recovery loop for the common failure case where a tool returns no or conflicting data before report sections are written; not a 3: the sequence and checkpoints are explicit, not implicit.

4 / 5

Progressive Disclosure

The body cites six reference files (REPORT_TEMPLATE.md, STUDY_DESIGN_PROCEDURES.md, WORKFLOW_DETAILS.md, BEST_PRACTICES.md, EXAMPLES.md, QUICK_START.md) in a Reference Files table and inline, but none exist in the bundle — there is no references/ directory at all, so all navigation to the detail material is broken. Meanwhile content that clearly belongs in those files (the 14-section template listing, the ~35-line Programmatic Access API example) is inlined in SKILL.md, matching the anchor for inlined content plus unresolvable references. Not a 3: the references are clearly signaled but point to nonexistent files, making the structure worse than 'could be better organized'; not a 1: the body itself has clear section headers and is navigable.

2 / 5

Total

13

/

20

Passed

Description

83%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 in third-person voice that clearly states what the skill does (6-dimension feasibility analysis with named outputs) and when to use it (concrete Use-for triggers). Weaknesses are minor: a few natural trigger variations are missing from the description itself, and 'power/sample-size estimation' and 'FDA submission strategy' create slight overlap risk with adjacent statistics and regulatory skills.

Suggestions

Add a few natural trigger variations to the description itself (e.g., 'sample size calculation', 'Phase 1/2 trial design', 'enrollment feasibility'), which currently appear only in the body's When-to-Use section.

Sharpen the boundary against adjacent skills, e.g., noting this skill assesses feasibility while a companion skill writes the protocol, to reduce overlap with statistics and regulatory-submission skills.

DimensionReasoningScore

Specificity

The description enumerates concrete actions — "Analyzes 6 dimensions (endpoint, population, comparator, effect size, duration, regulatory pathway)", "Produces enrollment projections, endpoint recommendations, and approval-pathway analysis" — which matches the anchor for several specific actions with minor gaps (safety-monitoring outputs and report generation are not mentioned). Not a 5: coverage is not fully comprehensive; not a 3: far more than 1-2 concrete actions are named.

4 / 5

Completeness

It explicitly answers both questions: 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 — a direct match for the top anchor.

5 / 5

Trigger Term Quality

Natural trigger terms like "trial-protocol design", "power/sample-size estimation", "comparator selection", and "FDA submission strategy" are phrases users would actually say. Not a 5: common variations such as "sample size calculation", "enrollment", or "Phase 1/2 design" appear only in the body, not the description; not a 3: keyword coverage is good, not just 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The clinical-trial-design feasibility niche is clear and distinct from general drug/disease research skills. Not a 5: "power/sample-size estimation" and "FDA submission strategy" create minor overlap risk with statistics and regulatory-submission skills (and a sibling tooluniverse-clinical-trial-protocol skill is referenced in the body); not a 3: overlap risk is confined to closely related skills, not broad.

4 / 5

Total

17

/

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

plugins/tooluniverse/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.