CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sample-size-basic

Basic sample size estimator for clinical research planning. Computes per-group and total N for two-sample/paired t-tests, chi-square tests, and proportion comparisons, reporting alpha, power, effect size, and statistical assumptions summary for grant proposals and preliminary ...

Quality

74%

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

Quality

Content

66%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 core workflow is excellent — clearly sequenced with input validation, a confirmation checkpoint, and fallback handling, plus a concrete worked example. However, the body is bloated with governance boilerplate and duplicated verification commands, and it never shows a full invocation of the script with real arguments.

Suggestions

Remove or relocate the governance boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template) that does not help execute sample-size calculations.

Add a complete CLI usage example with arguments, e.g., "python scripts/main.py --test-type t_test --alpha 0.05 --power 0.80 --effect-size 0.5", alongside the existing --help verification.

Drop the duplicated py_compile command (Quick Check vs. Audit-Ready Commands) and remove the date-stamped "Next Review Date", which is time-sensitive information penalized by the guidelines.

DimensionReasoningScore

Conciseness

The body is noticeably padded: boilerplate governance sections (Risk Assessment table, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template) add little executable value, the "Quick Check" and "Audit-Ready Commands" sections duplicate the same py_compile command, and the "Next Review Date: 2026-03-06" is time-sensitive information penalized per the guidelines. It sits between anchor 1 and anchor 3 but is clearly below the midpoint, matching anchor 2's 'several unnecessary explanations or padded sections'.

2 / 5

Actionability

Concrete verification commands ("python -m py_compile scripts/main.py", "python scripts/main.py --help"), documented parameters with defaults (alpha 0.05, power 0.80), and a worked example with expected output ("alpha=0.05, power=0.80, effect_size=0.5 → n=64 per group, total=128") give mostly executable guidance. The minor gap — no end-to-end CLI invocation showing actual arguments — keeps it below anchor 5.

4 / 5

Workflow Clarity

The 7-step workflow has a clear sequence with explicit validation ("Verify alpha in (0,1), power in (0,1), effect_size > 0... If invalid, report exact error and stop"), a user-confirmation checkpoint before computing, and an error-recovery fallback ("If test type is ambiguous, present options... and ask user to clarify"), reinforced by the Error Handling section. This matches anchor 5's explicit validation steps with feedback loops for error recovery.

5 / 5

Progressive Disclosure

Clear section structure with a well-signaled, one-level-deep reference to [references/audit-reference.md] (a real file), and concrete commands referencing the real scripts/main.py. It falls short of anchor 5 because substantial boilerplate content that belongs in separate files (or nowhere) is inlined in SKILL.md — an organization gap rather than a navigation failure.

4 / 5

Total

15

/

20

Passed

Description

71%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, specific description that clearly communicates what the skill computes across t-test, chi-square, and proportion scenarios. Its main weaknesses are the missing explicit "Use when..." trigger guidance and a truncated trailing fragment, which cap completeness and limit trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user says 'sample size', 'power analysis', 'how many subjects', or 'n per group' for study planning."

Complete or remove the truncated trailing text "for grant proposals and preliminary ..." — an ellipsis in a description reads as an unfinished edit.

Include natural synonyms such as "power analysis" and "how many participants" alongside the existing statistical keywords.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage of its scope: "Computes per-group and total N for two-sample/paired t-tests, chi-square tests, and proportion comparisons, reporting alpha, power, effect size, and statistical assumptions summary." No notable gaps in the 'what' — it names all three supported test families and both output quantities, so it exceeds anchor 4 ('several specific actions; minor gaps').

5 / 5

Completeness

The 'what' is clearly stated, but there is no explicit "Use when..." trigger clause; the trailing fragment "for grant proposals and preliminary ..." only weakly implies a 'when' and appears truncated. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3 — it has a clear 'what' with weakly implied 'when', matching anchor 3.

3 / 5

Trigger Term Quality

Good keyword coverage including "sample size", "power", "effect size", "chi-square", and "grant proposals", but common natural phrases users would say are missing (e.g., "power analysis", "how many subjects", "n per group"), so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Basic sample size estimator for clinical research planning" carves out a clear niche with named statistical test families, creating only minor overlap risk with general statistics/data-analysis skills. It does not reach anchor 5 because the weak, truncated trigger guidance means distinct triggers are not fully established.

4 / 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/Protocol Design/sample-size-basic/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.