CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sample-size-and-power-planning-assistant

Plans sample size estimation logic, power assumptions, feasibility checks, and fallback enrollment strategies for clinical and translational study protocols.

Quality

71%

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 ./awesome-med-research-skills/Protocol Design/sample-size-and-power-planning-assistant/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.

A well-structured, instruction-only skill with a genuinely actionable eight-step workflow, a mandatory output template, and a clean one-level-deep reference bundle. Its dominant weakness is token efficiency: the same planning cycle is restated across at least four sections, and hard rules and input-validation thresholds are duplicated between SKILL.md and the reference files.

Suggestions

Collapse the "Task", "Core Function", and "Quality Standard" lists into one statement of purpose plus the mandatory output structure — the planning cycle is currently described four times.

Replace the 12 inline "Hard Rules" with a short pointer (e.g., "Obey references/hard-rules.md at every step") and delete the in-body "Input Validation" list, which restates references/input-clarification-thresholds.md; keeping rules in two places invites drift.

Merge "Scope Boundary" and "What This Skill Should Not Do" (they overlap substantially) and add a brief worked mini-example of the memo for one common case (e.g., two-group binary endpoint) to lift actionability.

DimensionReasoningScore

Conciseness

The body is noticeably padded with self-duplication rather than explanations of known concepts: the "Task" list, "Core Function" list, "Mandatory Output Structure" (A–L), and "Quality Standard" sections restate the same planning cycle four times; "Scope Boundary", "What This Skill Should Not Do", and the 12 "Hard Rules" overlap heavily; the in-body "Hard Rules" near-duplicate references/hard-rules.md (10 rules) and "Input Validation" restates references/input-clarification-thresholds.md. This is "several unnecessary or padded sections" (anchor 2), not 3 — the redundancy is extensive and structural — but not 1 since it never teaches concepts Claude already knows.

2 / 5

Actionability

For an instruction-only skill, the guidance is concrete: eight sequenced execution steps, a mandated 12-section output structure with defined contents per section, explicit assumption-quality labels, and enumerated design families, fragility threats, and fallback options. Minor gaps keep it below 5: no worked example or filled-in sample memo, and Section H ("Explain the main reasoning path") leaves the hardest part — the actual sizing logic — unspecified beyond pointing to the design-family reference.

4 / 5

Workflow Clarity

Steps 1–8 are clearly sequenced (clarify → identify driver → select family → audit assumptions → choose stance → build scenarios → identify fragility → produce memo) with an explicit clarification gate in Step 1 and Input Validation, and Section L builds a self-critical review into the output. It stops short of 5 because there is no post-draft feedback loop (e.g., re-audit or revise if assumptions conflict) and steps 2, 6, and 7 are consideration lists rather than decision procedures.

4 / 5

Progressive Disclosure

Five real reference files exist, each exactly one level deep, each introduced in "Reference Module Integration" with a clear purpose ("Use before any long-form answer", "Apply throughout the entire response"), and each verified to contain substantive, non-stub content. Below 5 because content that should live solely in the references is also inlined in SKILL.md — the 12 Hard Rules duplicate references/hard-rules.md and the Input Validation section duplicates references/input-clarification-thresholds.md — creating two sources of truth.

4 / 5

Total

14

/

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, domain-specific description in third person that names four concrete capabilities and is highly distinguishable from neighboring skills. Its main weakness is the missing "Use when..." trigger clause and the absence of the most natural user phrasings ("power analysis", "how many patients do I need"), which caps completeness and slightly limits trigger coverage.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks how many patients/participants they need, wants a power analysis, or asks whether a fixed sample can support a primary endpoint."

Add natural synonyms users actually say — "power analysis", "underpowered", "how many patients do I need", "cohort/trial/survival endpoint" — to improve trigger term coverage.

Optionally name the deliverable (a planning memo with assumption audit and fallback scenarios) so the "what" matches the skill's actual output.

DimensionReasoningScore

Specificity

The description lists several specific actions — "Plans sample size estimation logic, power assumptions, feasibility checks, and fallback enrollment strategies" — anchored to a concrete domain ("clinical and translational study protocols"). It falls short of a 5 because the actions are moderately abstract ("estimation logic", "feasibility checks") and coverage has gaps: the clarification-first behavior, assumption auditing, and the memo output that dominate the skill body are absent.

4 / 5

Completeness

The "what" is clear (plans sample size logic, power assumptions, feasibility checks, fallback enrollment strategies), but there is no "Use when..." clause or equivalent explicit trigger guidance — only a weak "when" implication from "for clinical and translational study protocols". Per the judging guideline, a missing 'Use when...' clause caps completeness at 3; it is above 2 because the what-side is concrete and the domain does weakly imply the when.

3 / 5

Trigger Term Quality

"sample size", "power", "enrollment", and "clinical... study protocols" are the natural terms users would say when needing this skill. Not a 5 because common phrasings users actually use are missing: "power analysis", "how many patients/participants do I need", "underpowered", and study-type keywords (cohort, trial, survival).

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche — protocol-stage sample size and power planning — with distinctive trigger terms ("sample size estimation", "power assumptions", "fallback enrollment") that would rarely route to the wrong skill. Overlap risk with a generic statistics or study-design skill is minimal because the term combination is tightly scoped to enrollment/power planning.

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

awesome-med-research-skills/Protocol Design/sample-size-and-power-planning-assistant/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.