CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clinic-research-design

Generates a structured prompt framework for clinical study protocols. Supports Diagnostic, Efficacy, Etiology, and Prognosis studies. Calculates sample size and provides logic guides for LLMs.

Quality

64%

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/clinic-research-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 skill has a genuinely actionable core — a concrete CLI invocation with documented PICO arguments and a well-specified output format — wrapped in a large amount of generic template boilerplate. Cutting the duplicated validation sections, the verbatim description repeat, and the platitudinous workflow/safety sections would roughly halve the body while losing nothing.

Suggestions

Delete or merge the redundant generic sections (When to Use, Key Features, Dependencies, Implementation Details, Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Deterministic Output Rules, Completion Checklist) — keep only the concrete ones: the CLI usage, Arguments, Output Format, and a single validation step.

Consolidate "Validation Shortcut" and "Quick Validation" into one section with the single command "python scripts/main.py --help" and its expected output.

Remove the verbatim repetition of the frontmatter description inside "Key Features" and drop the odd dated example path ("cd "20260316/scientific-skills/...") in favor of a portable invocation example.

DimensionReasoningScore

Conciseness

Roughly half the body is generic boilerplate that adds nothing Claude cannot infer: "Use this skill when the request matches its documented task boundary" is tautological, the frontmatter description is repeated verbatim in Key Features, and the same "python scripts/main.py --help" validation appears in both "Validation Shortcut" and "Quick Validation". This matches anchor 2 (noticeably verbose, several padded sections), not anchor 3, because the padding is pervasive rather than occasional.

2 / 5

Actionability

The core path is executable and copy-paste ready: "python scripts/main.py --type efficacy --P "Type 2 Diabetes" --I "Metformin" --C "Placebo" --O "HbA1c" --study_design "RCT"" with documented arguments and a described output format (headers, "[LLM Instruction]" blockquotes, hard data). It is anchor 4 rather than 5 because no output path/flag is documented and the surrounding sections ("Recommended Workflow", "Output Contract") stay abstract.

4 / 5

Workflow Clarity

"Usage for Agents" gives a clear sequence (call the skill with the command → read the output file → execute its instructions), and validation checkpoints exist (Quick Validation expected output, Completion Checklist, Failure Handling recovery steps). It falls short of anchor 5 because validation is scattered across redundant sections rather than integrated as an explicit validate→fix→retry loop within the sequence.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so this scores the body structure alone: it has clear section headers and mentions script paths ("scripts/main.py", "scripts/calculators/sample_size.py"), but it is a 20+ section single file with substantial inline boilerplate and duplicated content that should be consolidated. This matches anchor 3 (some structure but could be better organized), not anchor 4 (the duplication and template filler are real organization gaps).

3 / 5

Total

13

/

20

Passed

Description

58%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 is in third person, names a concrete domain and several specific capabilities, and carves out a recognizable niche. Its main weaknesses are the complete absence of a "Use when..." trigger clause (which caps completeness) and thin synonym coverage of natural user phrasings like "clinical trial" or "protocol design".

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to design or draft a clinical study/trial protocol, plan a diagnostic/efficacy/etiology/prognosis study, or calculate sample size for medical research."

Include natural synonyms users would actually say — "clinical trial protocol", "study design", "RCT", "medical research" — alongside the current study-type enumeration.

Replace the vague "provides logic guides for LLMs" with a concrete capability statement such as "selects the appropriate reporting guideline template (STARD, SPIRIT, etc.) per study type".

DimensionReasoningScore

Specificity

Quotes "Generates a structured prompt framework for clinical study protocols" and "Calculates sample size" — several concrete actions naming the domain, with the minor gap that "provides logic guides for LLMs" is vague. It exceeds anchor 3 (more than 1-2 actions) but not anchor 5 ("logic guides" is not a comprehensive, concrete action list).

4 / 5

Completeness

The "what" is clear (generates a structured prompt framework, calculates sample size), but there is no "Use when..." clause or equivalent trigger guidance anywhere. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3; it cannot reach 4 because the "when" is fully absent, not merely implicit.

3 / 5

Trigger Term Quality

Natural keywords like "clinical study protocols", "sample size", and the four study types (Diagnostic, Efficacy, Etiology, Prognosis) are present, but common user phrasings such as "clinical trial", "protocol design", "study design", or "RCT" are missing. This matches anchor 3 (relevant keywords but missing common variations/synonyms) rather than anchor 4's good-but-gapped coverage.

3 / 5

Distinctiveness Conflict Risk

A clear niche (clinical study protocol generation with PICO-style inputs and sample-size calculation) makes it mostly distinct with only minor overlap risk against generic statistics or sample-size calculator skills. Not anchor 5 because those adjacent statistics skills could still collide on "sample size" triggers.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 8 missing, 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Protocol Design/clinic-research-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.