CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

experiment-design

Design scientific experiments including sample size calculation, randomization, control groups, blinding, and study protocols. Covers RCTs, quasi-experiments, factorial designs, A/B tests, survey design, and observational studies. Use when user asks to design an experiment, ca...

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

Quality

Content

57%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 useful reference-style body with executable power-analysis code, a practical design-selection table, and a protocol template. It is weakened by a glossary of textbook concepts Claude already knows, a machine-specific venv path baked into the code block, the absence of an explicit sequenced workflow with validation checkpoints, and no use of bundle files for the template and script.

Suggestions

Delete or drastically trim the "Key Design Principles" section — definitions of control types, randomization schemes, blinding levels, and the bias-mitigation table are knowledge Claude already has; keep only non-obvious guidance.

Move the power-analysis code into a portable scripts/power_analysis.py bundle file and remove the hardcoded "source /Users/zhangmingda/clawd/.venv/bin/activate" line so the code runs on any machine.

Add an explicit numbered workflow (clarify research question → select design from the table → compute and sanity-check sample size → fill protocol template) and move the study protocol template to assets/ so it can be copied verbatim.

DimensionReasoningScore

Conciseness

The body is mostly compact (tables, code, template), but the "Key Design Principles" section spends ~30 lines defining textbook concepts Claude already knows (positive/negative controls, block/stratified randomization, single/double/triple blinding, the bias-mitigation table). Matches the "mostly efficient but includes some unnecessary explanation" anchor; not 2 because there is no padded prose, and not 4 because the concept glossary is genuinely removable.

3 / 5

Actionability

The power-analysis functions (sample_size_ttest, sample_size_chi2, sample_size_correlation) are complete, runnable Python with concrete example calls, and the design-selection table and protocol template are directly usable. Matches "mostly executable guidance with minor gaps"; not 5 because the code block opens with a machine-specific activation line ("source /Users/zhangmingda/clawd/.venv/bin/activate") that fails on any other machine, and only three statistical scenarios are covered.

4 / 5

Workflow Clarity

The section ordering implies a sequence (select design → compute sample size → draft protocol) but no explicit ordered workflow is stated, and validation is limited to generic Error Handling/Input Validation boilerplate rather than process checkpoints (e.g., verifying computed N achieves target power). Matches the "sequence present but implicit, checkpoints missing" anchor; not 4 because the steps are never made explicit, not 2 because the sections do rough-order the process.

3 / 5

Progressive Disclosure

A single ~155-line file with no bundle files: section headers are clear, but content that should be separate is inlined — the ~30-line fill-in study protocol template belongs in an assets/ file and the power-analysis heredoc belongs in a scripts/ file. Matches the "content that should be separate is inline" anchor; not 4 because at this length the unsplit template and script exceed minor organization gaps.

3 / 5

Total

13

/

20

Passed

Description

80%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 third-person description with comprehensive capability and design-type coverage and an explicit trigger clause. Its main defect is that the text is truncated mid-phrase ("ca..."), which cuts off the trigger guidance and omits natural synonyms like "power analysis" or "study design".

Suggestions

Restore the full 'Use when...' clause — the description is truncated mid-phrase ("...design an experiment, ca..."), cutting off the intended trigger conditions.

Add natural trigger synonyms users would say, such as "power analysis", "study design", "clinical trial", or "randomized controlled trial", to improve trigger coverage and distinctiveness.

DimensionReasoningScore

Specificity

"Design scientific experiments including sample size calculation, randomization, control groups, blinding, and study protocols" lists multiple concrete actions (sample size calculation, randomization, blinding, protocol design) plus comprehensive design-type coverage ("RCTs, quasi-experiments, factorial designs, A/B tests, survey design, and observational studies"), matching the comprehensive-coverage anchor. It is not 4 because the action list shows no coverage gaps.

5 / 5

Completeness

Both parts are present: a clear 'what' ("Design scientific experiments including sample size calculation, randomization...") and an explicit 'when' ("Use when user asks to design an experiment"), matching the anchor where 'when' could be more explicit. It is not 5 because the 'when' clause is cut off mid-sentence, losing the remaining concrete trigger phrases; not 3 because the 'Use when' clause is explicitly present rather than merely implied.

4 / 5

Trigger Term Quality

Natural terms like "design an experiment", "A/B tests", "sample size", and "RCT" are present, matching the good-coverage anchor. It is not 5 because the trigger clause is truncated mid-phrase ("Use when user asks to design an experiment, ca...") and common synonyms such as "power analysis", "study design", or "clinical trial" are missing.

4 / 5

Distinctiveness Conflict Risk

Distinctive terms ("randomization, control groups, blinding", "quasi-experiments", "factorial designs") establish a clear experiment-design niche with only minor overlap risk against general statistics or A/B-testing skills. It is not 5 because "sample size calculation" and "A/B tests" could plausibly match a statistics or conversion-testing skill; not 3 because the core triggers are firmly experimental-design-specific.

4 / 5

Total

17

/

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/experiment-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.