CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clinical-trial-protocol-skill

Generate clinical trial protocols for medical devices or drugs. This skill should be used when users say "Create a clinical trial protocol", "Generate protocol for [device/drug]", "Help me design a clinical study", "Research similar trials for [intervention]", or when developi...

Quality

72%

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/Protocol Design/clinical-trial-protocol-skill/SKILL.md
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 a well-structured, actionable orchestration: explicit step sequence, on-demand loading of six real reference files, resume capability, and error-retry loops. Its weaknesses are heavy redundancy (the lazy-loading rule and the Implementation Requirements section repeat earlier content almost verbatim) and internal inconsistencies in step numbering and one stale filename reference.

Suggestions

Delete the "Implementation Requirements" section and consolidate the on-demand-loading rule into one statement; it is repeated roughly six times across the document.

Fix the stale filename: the Architecture section lists "05-generate-document.md # NIH Protocol generation" but the actual file and step mapping use "references/05-concatenate-protocol.md".

Unify step numbering: the Full Workflow Logic restarts at "Step 1/2/3" (with a "Step 2.5" menu) inside the global Steps 0-5 sequence, making references like "Continue to Step 3 (Final Summary)" ambiguous.

Add a minimal usage example for scripts/sample_size_calculator.py (or a pointer to the subskill that documents it) so the sole script is actionable from SKILL.md.

DimensionReasoningScore

Conciseness

The on-demand loading rule is stated at least five separate times ("Do NOT pre-read subskill files", "ON-DEMAND LOADING", "Do NOT read subskill files in advance or 'to prepare'", "LAZY LOADING - On-Demand Only"), and the entire "Implementation Requirements" section restates the "Execution Flow" section nearly point-for-point. This is noticeably verbose with several padded, redundant sections, matching the level-2 anchor rather than the level-3 'mostly efficient' anchor.

2 / 5

Actionability

Concrete, executable guidance throughout: the exact welcome message to display, exact menus with option-by-option logic, an explicit step-to-file mapping ("Step 2: references/02-protocol-foundation.md ... sections 1-6"), install commands ("pip install -r requirements.txt"), a concrete waypoint file layout, and a research-summary template. It stops short of 5 because the script is never shown in use ("scripts/sample_size_calculator.py # Statistical power analysis (validated)") and placeholders like "[TBD] items" are left unexplained.

4 / 5

Workflow Clarity

Steps 0-5 are clearly sequenced with completion-status checks, resume-from-waypoint logic, a retry/exit feedback loop on step failure, and an MCP connectivity check in Step 1. It is not a 5 because of numbering incoherence: the Full Workflow Logic restarts its own Step 1/2/3 numbering inside the global 0-5 sequence ("Step 2.5: Protocol Completion Menu", "Continue to Step 3 (Final Summary)"), and the architecture section lists "05-generate-document.md # NIH Protocol generation" while the mapping and the actual filesystem say "references/05-concatenate-protocol.md".

4 / 5

Progressive Disclosure

The bundle structure is genuinely good: six one-level-deep subskill files in references/ (verified to exist on disk), each clearly signaled by step-to-file mapping and loaded on demand, plus a separate scripts/ calculator and assets/ template. It is not a 5 because the ~500-line body inlines full menus, message templates, and a research-summary markdown template that duplicate detail more appropriate to the referenced subskills, keeping SKILL.md from being a lean overview.

4 / 5

Total

14

/

20

Passed

Description

73%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.

The description has a clear what, an explicit when with natural quoted trigger phrases, and a well-defined niche. Its main defects are low action specificity (only one capability is named) and a hard truncation mid-word ("or when developi...") that cuts off the final trigger condition.

Suggestions

Fix the truncated description: it ends mid-word at "or when developi...", cutting off the last trigger condition; complete the sentence within the frontmatter description field.

Name the other concrete capabilities to raise specificity, e.g. FDA regulatory pathway research, similar-trial research via ClinicalTrials.gov, and statistical sample-size calculation.

Add natural trigger synonyms such as "study protocol", "trial design", or "write a clinical study protocol" to broaden keyword coverage.

DimensionReasoningScore

Specificity

"Generate clinical trial protocols for medical devices or drugs" names the domain plus at most two concrete actions (generate protocols; research similar trials, the latter only appearing inside a trigger phrase). It is not the level-4 anchor because capabilities the skill actually has (FDA regulatory pathway research, sample-size calculation, protocol document assembly) are absent from the description.

3 / 5

Completeness

It answers both questions: a clear what ("Generate clinical trial protocols for medical devices or drugs") and an explicit when ("This skill should be used when users say...") with concrete trigger phrases. It is not a 5 because the when-clause terminates mid-word at "or when developi...", leaving one trigger condition incomplete.

4 / 5

Trigger Term Quality

The quoted phrases "Create a clinical trial protocol", "Generate protocol for [device/drug]", "Help me design a clinical study", and "Research similar trials for [intervention]" are natural things a user would say and cover create/generate/design/research synonyms. It falls short of the level-5 anchor because common variations like "study protocol", "trial design", or "write a protocol" are missing and the final trigger clause is cut off mid-word.

4 / 5

Distinctiveness Conflict Risk

Clinical trial protocol generation for medical devices or drugs is a clear niche with distinct, domain-specific trigger phrases ("clinical trial protocol", "design a clinical study", "research similar trials"), so conflict with other skills is minimal.

5 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (519 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Protocol Design/clinical-trial-protocol-skill/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.