CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

statistical-analysis

Statistical analysis toolkit. Hypothesis tests (t-test, ANOVA, chi-square), regression, correlation, Bayesian stats, power analysis, assumption checks, APA reporting, for academic research.

60

Quality

76%

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 ./bundled/skills/statistical-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.

The content is highly actionable with comprehensive executable examples and a sound, well-referenced structure, but it is markedly over-long and restates background knowledge Claude already has. Trimming the boilerplate lists and pushing more detail into the existing reference files would meaningfully improve token efficiency without losing actionability.

Suggestions

Cut or condense the 'Best Practices' and 'Common Pitfalls' lists, which restate general statistical knowledge Claude already has, and the Bayesian 'Key Advantages' section.

Move the full APA report templates and the four-panel matplotlib diagnostic block into references/reporting_standards.md and references/assumptions_and_diagnostics.md, leaving only a compact inline example.

Tighten the code examples to the minimal executable core and remove inline setup boilerplate (e.g., repeated matplotlib axis labeling) that Claude can fill in.

DimensionReasoningScore

Conciseness

The ~620-line body is noticeably verbose: the 'Best Practices' (10 items), 'Common Pitfalls' (10 items), and 'Key Advantages' of Bayesian sections largely restate statistical knowledge Claude already has, and full matplotlib figure-setup code pads several examples.

2 / 5

Actionability

Provides fully executable, copy-paste-ready code for the common cases — pingouin t-test/ANOVA, statsmodels regression with VIF diagnostics, pymc Bayesian t-test, and statsmodels power analysis — covering the core workflows with concrete, runnable snippets.

5 / 5

Workflow Clarity

A decision tree plus a sequenced 'Getting Started Checklist' give a clear path through the work; checkpoints are mostly implicit (assumption checks are recommended but not enforced as validate-remediate-recheck loops), leaving minor validation gaps.

4 / 5

Progressive Disclosure

References are real, one level deep, and clearly signaled ('See references/...md') with a dedicated Resources section; structure is good, though a fair amount of content (full report templates, effect-size table, large code blocks) stays inlined rather than pushed to the reference files.

4 / 5

Total

15

/

20

Passed

Description

75%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.

The description is specific and clearly niche-scoped with strong capability enumeration, but its trigger guidance is weak and lacks the explicit 'Use when...' phrasing that the rubric expects. Raising the 'when' clarity and adding natural synonyms would move it toward the top anchors.

Suggestions

Add an explicit trigger clause such as 'Use when running hypothesis tests, regression, or power analysis for academic research' rather than relying on the trailing 'for academic research' tag.

Include natural synonyms and file/context cues users say (e.g., 'p-values', 'effect sizes', 'statistical significance', 'survey data') to broaden trigger coverage.

Keep the concrete action list but consider trimming 'Bayesian stats' to 'Bayesian analysis' or adding 'Bayes Factors' to match user vocabulary more naturally.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'Hypothesis tests (t-test, ANOVA, chi-square), regression, correlation, Bayesian stats, power analysis, assumption checks, APA reporting' — with comprehensive coverage of the domain.

5 / 5

Completeness

Has a clear 'what' (the enumerated capabilities) but the 'when' is only weakly implied via the broad tag 'for academic research' rather than an explicit 'Use when...' clause, so completeness is capped per the rubric guidance.

3 / 5

Trigger Term Quality

Good keyword coverage including natural terms researchers say ('t-test', 'ANOVA', 'regression', 'power analysis') and a 'for academic research' trigger, but lacks synonyms and the trigger phrasing is thin rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Statistical analysis toolkit' names a clear niche with distinct, specific test-based triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository

foryourhealth111-pixel/Vibe-Skills

Path

bundled/skills/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.