CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

experimental-data-analysis

Statistical analysis and reporting for experimental datasets; use when you need to interpret experimental results, test significance (t-tests/ANOVA), or generate reproducible reports.

Quality

77%

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/Data Analysis/experimental-data-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-organized skill body with executable commands, clear run-directory conventions, and genuine one-level-deep reference files. Its main weakness is redundancy — Key Features and the Analysis Pipeline cover the same ground twice — plus abstract pipeline steps that would benefit from concrete script options and output examples.

Suggestions

Merge 'Key Features' with the 'Analysis Pipeline' (or reduce Key Features to one-line bullets) — the data preparation, descriptive statistics, and t-test/ANOVA capabilities are currently described twice, costing tokens without new information.

Add concrete detail for the analysis scripts: the command-line arguments analyze_experiment.py accepts (dataset path, grouping/outcome columns, overriding the run directory) and an example of the produced outputs/tables.

Link the references at their point of use (e.g. under Inferential Statistics: 'See references/stats-method-selection.md for the decision table') instead of only listing paths in Key Features, and add an explicit verify-step for the generated report.

DimensionReasoningScore

Conciseness

The body is mostly efficient (commands, directory conventions) but 'Key Features' (lines 17-28) restates the 'Analysis Pipeline' (lines 66-88) nearly point-for-point (data prep, descriptive stats, t-tests/ANOVA all described twice), and generic guidance like 'Handle missing values (e.g., drop, impute, or flag) according to the experimental design' is padding. Not a 2 because there is no conceptual over-explanation and the Example Usage and run-directory sections are tight.

3 / 5

Actionability

Concrete copy-paste commands are present ('python scripts/init_run.py', 'python scripts/analyze_experiment.py') along with explicit run-directory conventions ('outputs/runs/<timestamp>/config.json', 'Writing outside the run directory is prohibited'). Not a 5 because the analysis pipeline itself is abstract — no arguments/options for the scripts, no example of what outputs/tables look like.

4 / 5

Workflow Clarity

A clear sequence is given: init run, run analysis on the latest run directory, then the four-step pipeline with assumption checks (normality, homogeneity of variance) as explicit checkpoints, plus a write-isolation guardrail. Not a 5 because there is no explicit validate-outputs/verify-report step or error-recovery loop after assumption violations ('switch to an appropriate non-parametric alternative' names the fallback but not how to decide or re-check).

4 / 5

Progressive Disclosure

Good structure with a reasonably sized overview body; both referenced files ('references/stats-method-selection.md', 'references/reporting-template.md') exist, are one level deep, and contain the promised method-selection and report-template material. Not a 5 because the references are listed as bare paths in a bullet rather than context-linked navigation ('See X for Y') at the point of use, and pipeline detail that could live in a reference is inlined.

4 / 5

Total

15

/

20

Passed

Description

78%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 description that clearly states what the skill does and when to use it, with concrete method-level triggers (t-tests/ANOVA). The main deductions are the second-person 'use when you need to' phrasing (voice penalty) and keyword coverage that omits common synonyms like p-values or compare-groups phrasing.

Suggestions

Rewrite in third-person voice, e.g. 'use when the user needs to interpret experimental results...' or 'Use when analyzing experimental results, testing significance, or generating reproducible reports', to avoid the second-person penalty.

Add common trigger synonyms such as 'p-values', 'compare groups/conditions', or 'effect sizes' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('Statistical analysis and reporting for experimental datasets') with 2-3 concrete actions ('interpret experimental results', 'test significance (t-tests/ANOVA)', 'generate reproducible reports'), which is a base 4, but the second-person phrasing 'use when you need to' triggers the rubric's -1 voice penalty. It is above a 3's 'not comprehensive' anchor but the explicit penalty brings it back to 3.

3 / 5

Completeness

Explicitly answers both: the 'what' ('Statistical analysis and reporting for experimental datasets') and the 'when' with concrete trigger phrases ('use when you need to interpret experimental results, test significance (t-tests/ANOVA), or generate reproducible reports'). This matches the 5 anchor exactly; a 4 would require the 'when' clause to be less explicit or specific.

5 / 5

Trigger Term Quality

Natural trigger phrases users would say are present ('statistical analysis', 'experimental results', 'significance', 't-tests/ANOVA', 'reproducible reports'), matching 'good keyword coverage; a few natural terms missing'. It falls short of 5 because common variations like 'p-values', 'compare groups', or 'clinical trial' are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche (experimental dataset statistics with named tests t-tests/ANOVA) gives mostly distinct triggers with minimal conflict risk, matching the 4 anchor. It is not a 5 because 'statistical analysis and reporting' still overlaps somewhat with generic data-analysis or reporting skills.

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/Data Analysis/experimental-data-analysis/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.