CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

randomization-gen

Generates randomization sequences for RCTs including simple, blocked, and stratified allocation. Produces sealed randomization lists ready for allocation concealment.

Quality

68%

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/randomization-gen/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 workflow section is a strength — explicit input validation, a confirmation checkpoint, and a fallback loop — but the body is padded with generic template boilerplate that wastes context, and its actionability is undermined by a Parameters table that doesn't match the packaged script's real CLI. Removing the boilerplate and documenting the actual invocation would substantially improve the skill.

Suggestions

Remove or relocate the generic boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template) and deduplicate Quick Check vs. Audit-Ready Commands to cut token cost.

Document the actual script invocation with its real flags, e.g., python scripts/main.py --subjects 120 --groups "Control,TreatmentA,TreatmentB" --block-size 6 --output trial_randomization.csv, and fix the Parameters table (groups are comma-separated strings, default output is randomization.csv).

Replace the vague Example section with a real input/output pair (an actual sealed-list excerpt) and either add seed support to the script or drop the seed claim from the Workflow.

DimensionReasoningScore

Conciseness

The body carries several padded, generic sections — "Risk Assessment", "Security Checklist", "Evaluation Criteria" ("Standard input → Expected output"), "Lifecycle Status" ("Planned Improvements: Performance optimization"), "Output Requirements", and "Response Template" — none of which teach anything Claude doesn't already know, and "Quick Check" duplicates the identical py_compile command from "Audit-Ready Commands". This matches anchor 2 (noticeably verbose, several unnecessary padded sections); it is not a 1 because it never explains basic concepts Claude already knows.

2 / 5

Actionability

There are concrete audit commands (python -m py_compile scripts/main.py; python scripts/main.py --help) and a Parameters table, but the core generation invocation is never shown, the Example is pseudocode-level ("Input: n=120, 3 groups, block=6 / Output: Sealed randomization list"), and the Parameters table misdescribes the actual script CLI (body lists n_groups as an int and a randomization.txt default; the script takes --groups "Control,Treatment" comma-separated and defaults to randomization.csv, with no seed flag despite the workflow mentioning one). This is anchor 3: some concrete guidance but incomplete and inaccurate in key details, not the mostly-executable anchor 4.

3 / 5

Workflow Clarity

The six-step Workflow has an explicit validation step with exact constraints ("block_size is a multiple of n_groups... report exact constraint violated and stop"), a pre-generation checkpoint for user confirmation, and a fallback that suggests nearest valid block sizes and proceeds only after confirmation — a genuine feedback loop. It falls short of anchor 5 because the post-fallback re-validation cycle is implicit and steps 4–5 never state the executable command, but it is clearly above anchor 4's "minor validation gaps"... rather, it sits at anchor 4: most checkpoints present with minor gaps.

4 / 5

Progressive Disclosure

Scored against the actual bundle: references/audit-reference.md exists and is clearly signaled one level deep with a description of its contents, and scripts/main.py is reachable via the audit commands. Structure is good, but ~60 lines of generic boilerplate (security checklist, evaluation criteria, response template) are inlined in SKILL.md where they don't earn their place — matching anchor 4's "most content appropriately placed; minor organization gaps" rather than anchor 5's appropriately split content.

4 / 5

Total

13

/

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 specific, third-person description with strong domain vocabulary and low conflict risk, but it omits any explicit 'when to use' trigger clause, which caps its completeness. Adding a Use-when sentence with natural trigger phrases would raise it to the level of the reference good examples.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks for randomization, random allocation, block randomization, stratified randomization, or an RCT allocation sequence."

Include common synonyms and variations such as "randomisation" (British spelling, frequent in medical research) and "treatment allocation" to broaden natural trigger coverage.

Optionally mention the concrete deliverable format (e.g., CSV randomization list) to close the minor specificity gap.

DimensionReasoningScore

Specificity

The description names the domain and several concrete actions — "Generates randomization sequences for RCTs including simple, blocked, and stratified allocation" and "Produces sealed randomization lists ready for allocation concealment" — with minor gaps (e.g., no mention of output format or delivery). It lists several specific actions like the anchor-4 example but lacks the comprehensiveness of anchor 5, which would cover the full capability surface.

4 / 5

Completeness

The "what" is clear and concrete (generates RCT randomization sequences and sealed lists), but there is no "Use when..." clause or equivalent explicit trigger guidance; "for RCTs" only weakly implies when to use it. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3, and anchor 3 (clear what, when missing or weakly implied) is the closest fit.

3 / 5

Trigger Term Quality

Natural domain terms are present: "randomization sequences", "RCTs", "blocked", "stratified allocation", "allocation concealment" — phrases a trial designer would actually say. A few natural synonyms are missing (e.g., "randomisation", "treatment allocation", "allocation sequence"), so it falls short of anchor 5's comprehensive synonym coverage but is clearly above anchor 3.

4 / 5

Distinctiveness Conflict Risk

"RCT randomization sequences", "sealed randomization lists", and "allocation concealment" define a clear niche with distinct triggers that no adjacent skill (statistics, sample-size, general data generation) would naturally claim, matching anchor 5's minimal conflict risk. It is well above anchor 4, which requires minor overlap risk with closely related skills.

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/Protocol Design/randomization-gen/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.