CtrlK
BlogDocsLog inGet started
Tessl Logo

experimental-design

Best practices for designing reproducible ML experiments. Use when planning ablations, baselines, or controlled experiments.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, actionable, and well-organized for a simple checklist skill. Its main gap is workflow clarity: the practices are listed but not framed as a sequenced process with validation checkpoints.

Suggestions

Reframe the numbered items as an ordered workflow with an explicit validation checkpoint (e.g., 'After running seeds, confirm std is acceptable before reporting results') to lift workflow clarity above 2.

Add a brief verification step for destructive/batch-adjacent actions, such as confirming no test-set leakage before final reporting.

Consider sequencing the practices into setup (baselines, splits, seeds) -> execution (ablations, variable control) -> reporting (mean+/-std, wall-clock, memory) so the sequence is explicit rather than implicit.

DimensionReasoningScore

Conciseness

The body is a lean, directive list ('ALWAYS include meaningful baselines', 'Use MULTIPLE random seeds (minimum 3, ideally 5)', 'change only ONE thing per comparison') with no padding or explanation of concepts Claude already knows, matching the lean-and-efficient anchor; it never drifts toward the verbose level-1 example.

3 / 3

Actionability

Although there is no code, this is an instruction/best-practice skill and the guidance is concrete and actionable with specific thresholds ('minimum 3, ideally 5 seeds', 'at least one classical method baseline', 'Report mean +/- std'), so per the code_vs_instruction scoring note the absence of code is not penalized; it stays above level 2 because the directives are complete rather than missing key details.

3 / 3

Workflow Clarity

The numbered items list clear practices but they are parallel best-practice directives rather than a tightly sequenced process, and there are no validation/feedback checkpoints (e.g., verify baselines reproduce before reporting), matching the 'steps listed but validation gaps; checkpoints missing or implicit' anchor; it is below level 3 which requires explicit validation steps and error-recovery loops.

2 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references, and is organized with one clear heading and a numbered list, satisfying the simple-skills scoring note that progressive disclosure can score 3 with just well-organized sections; it is above level 2 because there is no inline bloat or poorly-signaled referencing.

3 / 3

Total

11

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 cleanly states what the skill covers and gives an explicit 'Use when' trigger with natural, distinctive terms. Its only weakness is the slightly abstract 'best practices for designing' framing on the specificity dimension.

DimensionReasoningScore

Specificity

Quotes 'Best practices for designing reproducible ML experiments' and 'planning ablations, baselines, or controlled experiments' — it names the domain and several concrete activities, but the lead 'best practices for designing' framing is more abstract than a list of concrete capabilities, matching the 'Names domain and some actions, but not comprehensive' anchor rather than the multiple-specific-actions level 3.

2 / 3

Completeness

It answers both 'what' ('Best practices for designing reproducible ML experiments') and 'when' with an explicit 'Use when...' clause, matching the clearly-answers-both-what-AND-when anchor; it is above level 2 because the trigger is explicit rather than implied.

3 / 3

Trigger Term Quality

The 'Use when planning ablations, baselines, or controlled experiments' clause supplies natural terms an ML practitioner would actually say, giving good coverage of common variations; it is not level 2 because the terms are not merely 'some relevant keywords' but a genuine spread of user-facing triggers.

3 / 3

Distinctiveness Conflict Risk

The niche (reproducible ML experimental design) and its triggers (ablations, baselines, controlled experiments) are distinctive and unlikely to fire for unrelated skills, matching the clear-niche-with-distinct-triggers anchor.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
aiming-lab/AutoResearchClaw
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.