CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

statistical-analysis

Guided statistical analysis with test selection and reporting. Use when you need help choosing appropriate tests for your data, assumption checking, power analysis, and APA-formatted results. Best for academic research reporting, test selection guidance. For implementing specific models programmatically use statsmodels.

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 ./backend/cli/skills/coding/statistical-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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-structured, highly actionable statistical-analysis body with genuine reference and script bundles that match their in-SKILL.md documentation. Its weakness is token efficiency: generic statistics pedagogy, plotting boilerplate, textbook lists, and repeated reference pointers inflate it well beyond what the overview needs, and two code snippets have API-signature bugs.

Suggestions

Cut the 'Key Advantages', 'Best Practices', 'Common Pitfalls', and 'Support and Further Reading' sections — that content is either generic statistics knowledge Claude already has or belongs in references/assumptions_and_diagnostics.md; keep the Getting Started Checklist as the workflow spine.

Move the four full worked code examples (t-test, ANOVA, regression diagnostics with plotting, Bayesian t-test) into a references/analysis_recipes.md and keep only one compact quick-start snippet inline.

Fix the two API mismatches: pingouin's `compute_effsize_from_t` returns a single float (compute the CI separately), and `FTestAnovaPower().solve_power` takes `nobs` (and `k_groups`/proportion kwargs) rather than `ngroups=3`.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with several padded sections that teach Claude things it already knows: ~30 lines of matplotlib residual-plot boilerplate, 'Key Advantages' explaining what Bayesian inference is, 'Best Practices'/'Common Pitfalls' lists of generic statistics-ethics definitions (p-hacking, HARKing), a textbook citation list, and online-resource links. It exceeds the anchor-3 'some unnecessary explanation' profile — there are multiple whole sections that earn no token — but is not severely padded throughout (the test-selection table, effect-size benchmarks, and APA templates are genuinely valuable), so it lands at 2 rather than 1.

2 / 5

Actionability

Mostly executable, copy-paste-ready code for the common cases: pingouin t-test/ANOVA with result extraction, statsmodels power analysis, pymc Bayesian t-test, and fill-in-the-blank APA report templates. It is not a 5 due to minor correctness gaps: `d, ci = compute_effsize_from_t(...)` treats pingouin's function as returning a (d, CI) tuple when it returns a single float, and `FTestAnovaPower().solve_power(..., ngroups=3, ...)` does not match statsmodels' actual signature (which takes nobs and derives groups). Far above the anchor-3 pseudocode profile.

4 / 5

Workflow Clarity

A clear sequence is present — 'Getting Started Checklist' runs question → test selection → power analysis → assumption verification via assumption_checks.py → analysis → effect sizes → reporting → sensitivity analysis — with explicit checkpoints ('ALWAYS check assumptions before interpreting test results') and violation-remediation branches (Welch's t-test, non-parametric alternatives). It falls short of 5 because the 'Workflow Decision Tree' is shallow (every NO branch just says 'Continue') and there are no error-recovery loops for runtime failures, e.g. convergence failures in pymc sampling.

4 / 5

Progressive Disclosure

Structure is good and the references are real and one level deep: all five `references/*.md` files exist as listed in the Resources section, are clearly signaled with per-topic descriptions, and `scripts/assumption_checks.py` exists with exactly the six functions the body documents. It is not a 5 because the overview itself carries long inline content that belongs in the reference files — four full code examples plus a 30-line plotting block push SKILL.md well past overview length, and some sections repeat the same reference pointers three times.

4 / 5

Total

14

/

20

Passed

Description

87%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 description with explicit use-when triggers and an unusual explicit disambiguation pointer to statsmodels. The main deductions are the second-person phrasing (voice penalty on specificity) and missing a few natural trigger synonyms like 'hypothesis test' or 'which test should I use'.

Suggestions

Rewrite the trigger clause in third person to avoid the voice penalty, e.g. 'Use when choosing appropriate statistical tests' instead of 'Use when you need help choosing...'.

Add common user phrasings as trigger terms: 'hypothesis testing', 'p-values', 'which statistical test', 'effect size', 'sample size'.

'Best for academic research reporting, test selection guidance.' is a fragment that repeats content already stated; fold it into the trigger clause for conciseness.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'test selection and reporting', 'assumption checking, power analysis, and APA-formatted results' — giving comprehensive capability coverage that would anchor at 5, but the second-person phrasing 'Use when you need help choosing' triggers the rubric's 1-point voice penalty, dropping it to 4. It is not a 3 because the action list is far more complete than the 1-2-action anchor.

4 / 5

Completeness

It explicitly answers both: what ('Guided statistical analysis with test selection and reporting' plus the enumerated capabilities) and when ('Use when you need help choosing appropriate tests for your data, assumption checking, power analysis...'), with a further scoping clause 'Best for academic research reporting, test selection guidance.' This matches the anchor-5 pattern of concrete trigger phrases attached to both what and when; a 4 would require the 'when' to be less explicit than it is.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'choosing appropriate tests', 'assumption checking', 'power analysis', 'APA-formatted results', 'academic research reporting' are phrases users would plausibly say. It misses common synonyms users often use ('hypothesis test', 'p-value', 'which statistical test', 'significance'), so it falls short of the comprehensive-synonyms anchor at 5 but clearly above the 3 anchor's missing-variations profile.

4 / 5

Distinctiveness Conflict Risk

A clear niche (guided academic statistical test selection and APA reporting) with distinct triggers, and the explicit boundary 'For implementing specific models programmatically use statsmodels' actively routes away the most likely conflicting skill. Minimal conflict risk, matching the anchor-5 profile rather than the minor-overlap anchor at 4.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (638 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

synthetic-sciences/openscience

Path

backend/cli/skills/coding/statistical-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.