CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clinic-sample-size

Unified tool for calculating sample sizes for Diagnostic, Efficacy, Etiology, and Prognosis clinical studies. Supports various statistical methods (Sensitivity/Specificity, Log-rank, Chi-square, EPV, etc.).

Quality

67%

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/Other/clinic-sample-size/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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's core usage documentation is genuinely actionable, with executable commands for all four study types and sensible smart-inference defaults. However, roughly half the body is generic process boilerplate, and structural defects (a dangling 'See ## Usage above' reference, duplicate contradictory validation shortcuts, a leaked internal path `cd "20260316/scientific-skills/Others/clinic-sample-size"`, and a title appearing mid-document) undermine both conciseness and workflow clarity.

Suggestions

Delete the generic template sections ('Output Contract', 'Deterministic Output Rules', 'Completion Checklist', 'Validation and Safety Rules', 'Failure Handling', 'Required Inputs') and keep only skill-specific content; the ~90 lines of boilerplate are the main token waste.

Consolidate the two validation shortcuts into one that actually works (validate_skill.py), remove the incorrect `python scripts/calculators.py --help` claim and its fabricated 'Expected output format', and fix the 'See `## Usage` above' dangling reference in Example Usage.

Restructure so the title '# Clinic Sample Size Calculator' leads the document, followed by When to Use / Not to Use and the Usage section, and remove the leaked internal build path from the example commands.

DimensionReasoningScore

Conciseness

A large fraction of the ~188-line body is generic template filler that adds no skill-specific information: "Use this skill when the request matches its documented task boundary", "Output discipline: keep results reproducible, identify assumptions explicitly, and avoid undocumented side effects", "Return a structured deliverable that is directly usable without reformatting". Sections like 'Output Contract', 'Deterministic Output Rules', 'Completion Checklist', and 'Validation and Safety Rules' restate process boilerplate Claude already knows. Not 1 because the core Usage section with the four study-type commands is genuinely useful and unpadded; not 3 because the filler is extensive, roughly half the document.

2 / 5

Actionability

The Usage section provides concrete, copy-paste-ready commands covering all four study types, e.g. `python scripts/main.py --study_name "New Biomarker Study" --outcome "Sensitivity > 0.8" diagnostic sens_spec --se 0.8 --sp 0.9 --error 0.05 --prev 0.3 --dropout 0.1`, plus inference-mode examples with commented default values. Not 5 because of gaps: the 'Quick Validation' documents `python scripts/calculators.py --help`, but calculators.py is a module with no CLI, and the efficacy section only shows one of the documented input variants. Not 3 because the primary paths are fully executable and cover the common cases.

4 / 5

Workflow Clarity

Sequences exist ('Example run plan', 'Recommended Workflow') and validation is attempted ('Validation Shortcut', 'Quick Validation'), but the checkpoints are muddled: two different 'run this first' commands are given (validate_skill.py vs calculators.py), the 'Expected output format' under Quick Validation describes report output a --help call would never produce, and 'Example Usage' opens with "See `## Usage` above" pointing at a section that appears later in the document. Sequence present but checkpoints are duplicated/confusing rather than clear — matches anchor 3, not 4.

3 / 5

Progressive Disclosure

The bundle is scripts-only (main.py, calculators.py, validate_skill.py — all real and correctly referenced), and per-study-type details appropriately live in the scripts rather than SKILL.md. However, structure within SKILL.md is disorganized: the actual title '# Clinic Sample Size Calculator' appears midway into the document, 'When to Use' precedes it, and there are two competing validation sections. This fits 'some structure but could be better organized' — not 4, since the interleaved boilerplate and mid-file title make navigation harder than the 'good structure' anchor.

3 / 5

Total

12

/

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.

The description clearly states what the skill does with specific domain terms and named statistical methods, and occupies a distinct niche. Its main weakness is the complete absence of when-to-use trigger guidance, and it misses natural synonyms like 'power analysis' that users would likely say.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user needs a sample size or power calculation for a clinical or medical study (diagnostic accuracy, RCT, cohort, case-control, or prediction model design)'.

Include natural trigger synonyms such as 'power analysis', 'power calculation', and 'how many patients/participants do I need' to broaden keyword coverage.

Optionally mention the deliverable (e.g. 'generates a Markdown report with assumptions and required sample sizes') so users know what output to expect.

DimensionReasoningScore

Specificity

Quotes: "calculating sample sizes for Diagnostic, Efficacy, Etiology, and Prognosis clinical studies" and "Sensitivity/Specificity, Log-rank, Chi-square, EPV" list several concrete, specific capabilities covering four study types and named statistical methods. Not 5 because it omits other actions the skill actually performs (report generation, smart parameter inference, custom output directories); not 3 because it goes well beyond naming the domain with 1-2 actions.

4 / 5

Completeness

The "what" is clear ("Unified tool for calculating sample sizes for Diagnostic, Efficacy, Etiology, and Prognosis clinical studies"), but there is no "when" — no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3 even with a clear what.

3 / 5

Trigger Term Quality

Quotes: "sample sizes", "clinical studies", "Diagnostic, Efficacy, Etiology, and Prognosis", "Sensitivity/Specificity", "Log-rank", "Chi-square", "EPV" — good natural term coverage for the domain. Not 5 because common phrasings users would actually say are missing, e.g. "power analysis", "power calculation", "how many participants/patients"; not 3 because coverage clearly exceeds just a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

Quotes: "sample sizes", "Diagnostic, Efficacy, Etiology, and Prognosis clinical studies", "EPV" — a clear niche with distinct trigger terms; it would not fire for generic document, data, or coding skills. Not 4 because the named study types and methods (EPV, Log-rank) make overlap with other skills minimal rather than just 'minor'.

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

scientific-skills/Other/clinic-sample-size/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.