CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

data-stats-analysis

Perform statistical tests, hypothesis testing, correlation analysis, and multiple testing corrections using scipy and statsmodels. Works with ANY LLM provider (GPT, Gemini, Claude, etc.).

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

Quality

Content

56%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 code-rich, largely executable skill whose statistical decision checkpoints (variance/normality routing, multiple-testing corrections, batch-effect thresholds) are its real value. However, it spends most of its token budget re-teaching standard scipy usage Claude already knows and repeats provider-compatibility marketing, and it keeps everything inline instead of splitting domain use cases into reference files.

Suggestions

Cut or drastically compress the basic-library tutorials (t-test, correlation, non-parametric, normality snippets) down to one-liners or a cheat-sheet table; keep only what Claude would not already know, such as the domain use cases and decision thresholds.

Move the Common Use Cases (differential expression, cluster enrichment, batch effect detection) into reference files (e.g., references/use-cases.md) and keep SKILL.md as a concise overview with clearly signaled pointers.

Remove the repeated 'Works with ALL LLM providers' claims, the boilerplate ✅/❌ print blocks, and unused imports (proportions_ztest, kstest) to tighten the token budget.

DimensionReasoningScore

Conciseness

The majority of the body (Steps 1-6 and Advanced Features, ~260 lines) re-demonstrates standard scipy/statsmodels calls Claude already knows (ttest_ind, pearsonr, mannwhitneyu, shapiro), plus 'Works with ALL LLM providers' is repeated in the Overview and Technical Notes, ✅/❌ print boilerplate pads every snippet, and the Troubleshooting section addresses trivial issues. This matches anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections') rather than 3, since it is not 'mostly efficient' — well over half the tokens re-teach known library usage.

2 / 5

Actionability

Guidance is mostly executable with concrete, runnable patterns (Levene's test routing to Welch's t-test, multipletests FDR/Bonferroni with p-clipping, Fisher exact enrichment contingency construction, Cohen's d). Anchor 4 rather than 5 because several snippets depend on undefined placeholder inputs (p_values, gene_names, gene_expression_df, data) and imports like proportions_ztest and kstest are never demonstrated.

4 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced with real validation checkpoints: Levene's test routes to Welch's t-test, Shapiro-Wilk routes to non-parametric tests, batch-effect detection has a >10% warning threshold, and Troubleshooting covers NaN cleaning and sample-size minimums. Not 5 because there is no explicit end-to-end error-recovery loop tying the checkpoints into one validated workflow.

4 / 5

Progressive Disclosure

The body has clear section headers, but no bundle files exist at all — the entire ~490-line skill is one monolithic file, and the domain-specific use cases (differential expression, cluster enrichment, batch effect) clearly belong in separate reference files. This matches anchor 3 ('some structure but content that should be separate is inline').

3 / 5

Total

13

/

20

Passed

Description

66%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 solid, specific description that names the domain, tooling, and several concrete capabilities, but it lacks any 'Use when' trigger guidance and omits high-frequency user terms like t-test, ANOVA, and p-value. The provider-compatibility sentence is marketing fluff that consumes the description budget without helping discovery.

Suggestions

Add an explicit trigger clause, e.g. 'Use when comparing group means (t-test, ANOVA), testing correlations, checking p-values/significance, or correcting for multiple comparisons.'

Include the natural synonyms users actually say — t-test, ANOVA, p-value, significance, FDR, non-parametric — in the trigger clause.

Remove the 'Works with ANY LLM provider (GPT, Gemini, Claude, etc.)' sentence; provider compatibility is irrelevant to when the skill should trigger.

DimensionReasoningScore

Specificity

Lists several concrete actions ('statistical tests, hypothesis testing, correlation analysis, and multiple testing corrections using scipy and statsmodels'), matching anchor 4. Not 5 because coverage has gaps (ANOVA, non-parametric tests, effect sizes, confidence intervals are all offered by the skill but absent from the description).

4 / 5

Completeness

The 'what' is clear, but there is no 'Use when...' clause or equivalent trigger guidance; the second sentence ('Works with ANY LLM provider (GPT, Gemini, Claude, etc.)') is compatibility marketing, not usage triggers. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

'statistical tests', 'hypothesis testing', 'correlation analysis', and 'multiple testing corrections' are natural phrases users would say, giving good keyword coverage. Not 5 because common variations users actually utter — 't-test', 'ANOVA', 'p-value', 'is this significant' — are missing.

4 / 5

Distinctiveness Conflict Risk

The scipy/statsmodels statistical-testing niche is mostly distinct with clear differentiators, though it could overlap with general data-analysis or data-viz skills. Not 5 because the provider-compatibility sentence adds generic noise that slightly weakens distinct triggering.

4 / 5

Total

15

/

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/data-stats-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.