CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-statistical-modeling

Statistical modeling — linear/logistic/ordinal/Poisson regression, ANOVA, Kruskal-Wallis, chi-square, Mann-Whitney, Cox survival, spline fits (R `ns()`), odds ratios, Cohen's d, F-statistic, p-value computation. Specializes in clinical-trial AE analysis (SDTM DM/AE), severity ordinal regression, and per-feature stat workflows.

Quality

73%

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 ./plugins/tooluniverse/skills/tooluniverse-statistical-modeling/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally actionable skill body with concrete, copy-paste-ready commands and genuine domain gotchas (AEPT filtering trap, R-vs-Python spline divergence, per-gene aggregation), but it is noticeably verbose: the same rules are restated three to four times and generic statistics tutorial content is inlined. Several referenced bundle files do not exist, undermining navigation.

Suggestions

Deduplicate: state the AE/AEPT rule, spline guidance, and expression_anova usage once each and cross-reference, removing the repeated Analysis conventions and Bundled Scripts restatements.

Fix or remove the dead references — anova_and_tests.md, common_patterns_summary.md, TOOLS_REFERENCE.md, QUICK_START.md, and EXAMPLES.md are cited but absent from the bundle.

Move the generic statistics tutorial content (model-selection decision tree, Interpretation Guidance, Evidence Grading, statsmodels-vs-sklearn table) into a reference file; Claude already knows these concepts.

DimensionReasoningScore

Conciseness

The 687-line body duplicates its own guidance repeatedly — the AE/AEPT no-filter rule appears in the PRIMARY SCRIPTS table, the CRITICAL section, and again in Analysis conventions; spline guidance appears four times; two identical expression_anova.py command blocks are pasted verbatim. It also inlines concepts Claude already knows ("OR = 1.0 means no association", "HR > 1 means increased hazard", the model-selection decision tree, the statsmodels-vs-scikit-learn table, Evidence Grading). This matches anchor 2 ('several unnecessary explanations or padded sections') rather than 3, where padding would be incidental rather than structural.

2 / 5

Actionability

Guidance is fully executable and copy-paste ready: complete CLI invocations with all flags (e.g. the r_natural_spline_regression.py and logistic_regression_or.py commands), worked `tu run` examples with expected outputs, wrong-vs-right code snippets, and a stdlib fallback for missing scipy. Specific examples cover the common cases, matching the anchor for a 5.

5 / 5

Workflow Clarity

There is a clear sequenced workflow — RULE ZERO (check pre-computed results first) → Phase 0 data validation → Phase 1 model fitting → Phase 2 diagnostics → Phase 3 interpretation — with explicit checkpoints: Phase 0 column/type checks, sanity heuristics that act as feedback loops ("If your F-statistic is >10 ... you probably aggregated"), and a Completeness Checklist. It falls short of 5 because the sequence is scattered across duplicated sections (PRIMARY SCRIPTS, CRITICAL, Analysis conventions) and precedence between sections must be synthesized by the reader.

4 / 5

Progressive Disclosure

References are one level deep and clearly signaled (dedicated Support section), and all 6 references/*.md files exist — but the body cites anova_and_tests.md (4 times), common_patterns_summary.md, TOOLS_REFERENCE.md, QUICK_START.md, EXAMPLES.md, and test_skill.py, none of which exist in the bundle, so navigation dead-ends. Additionally ~200 lines of reference-grade tutorial content (decision tree, interpretation guidance, evidence grading) are inlined in SKILL.md. This fits anchor 3 ('some structure but could be better organized; content that should be separate is inline') — real structure exists, so not 2, but the broken paths exceed the 'minor organization gaps' of 4.

3 / 5

Total

14

/

20

Passed

Description

71%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 highly specific, technique-dense description with excellent natural trigger keywords and a distinctive clinical-trial/SDTM niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which leaves the invocation conditions only weakly implied and caps completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for regression, ANOVA, odds/hazard ratios, survival analysis, or statistical tests on biomedical or clinical-trial data."

Include the missing high-frequency natural terms users say: "hazard ratio", "survival analysis", "Kaplan-Meier", "t-test", and "mixed-effects model".

Consider a sample question phrasing (e.g. "What is the odds ratio of X after adjusting for confounders?") to make the trigger conditions concrete.

DimensionReasoningScore

Specificity

The description lists many concrete, specific actions — "linear/logistic/ordinal/Poisson regression, ANOVA, Kruskal-Wallis, chi-square, Mann-Whitney, Cox survival, spline fits (R ns()), odds ratios, Cohen's d, F-statistic, p-value computation" — giving comprehensive coverage of the statistical-modeling domain. This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' rather than 4, since no meaningful capability gaps remain for the stated domain.

5 / 5

Completeness

The "what" is explicit and detailed (the full technique list), but there is no "Use when..." clause; "Specializes in clinical-trial AE analysis (SDTM DM/AE), severity ordinal regression, and per-feature stat workflows" is a scope statement that only weakly implies when to invoke the skill. Per the judging guideline, a missing 'Use when...' clause or equivalent explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Strong natural keywords users would actually say ("ANOVA", "chi-square", "odds ratios", "Cox survival", "Mann-Whitney", "p-value"), but common phrasings like "hazard ratio", "t-test", "Kaplan-Meier", "survival analysis", and "mixed-effects model" are absent. This fits anchor 4 ('Good keyword coverage; a few natural terms missing') better than 5, which requires comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche markers ("clinical-trial AE analysis (SDTM DM/AE)", "spline fits (R ns())", "per-feature stat workflows") make it mostly distinct with minor overlap risk against a generic statistics skill. It is not a 5 because the broad opening ("Statistical modeling — linear/logistic ... regression, ANOVA ...") would also match many general data-analysis 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

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

plugins/tooluniverse/skills/tooluniverse-statistical-modeling/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.