CtrlK
BlogDocsLog inGet started
Tessl Logo

statsmodels

Statistical models library for Python. Use when you need specific model classes (OLS, GLM, mixed models, ARIMA) with detailed diagnostics, residuals, and inference. Best for econometrics, time series, rigorous inference with coefficient tables. For guided statistical test selection with APA reporting use statistical-analysis.

61

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 ./backend/cli/skills/coding/statsmodels/SKILL.md

The canonical home for this skill is statsmodels in administrakt0r/AI-Agents-Safe-Coding-Skills

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 library skill with strong executable quick-start examples, explicit diagnostic-driven workflows, and a clean one-level-deep reference bundle. Its main weakness is token efficiency: it re-encodes the statsmodels API surface and best-practice lists that Claude already knows and that the reference files already carry, roughly doubling the body's necessary size.

Suggestions

Cut the 'Core Statistical Modeling Capabilities' model/family/link/test enumerations down to a one-line 'When to use' plus the existing reference pointer per section — Claude already knows statsmodels' class catalog, and the reference files restate it in full.

Merge the 'Reference Documentation' section into the per-capability pointer lines and move the 'Common Pitfalls' and 'Best Practices' lists into the relevant reference file, keeping only the 4-5 highest-frequency pitfalls (add_constant, overdispersion, model-to-outcome matching, non-stationary ARIMA) inline.

Drop the prose Overview/'When to Use' bullet list (which restates the frontmatter description) in favor of the Quick Start code, targeting roughly one-third of the current body length.

DimensionReasoningScore

Conciseness

The ~600-line body inlines large enumerations Claude already knows about this well-known library — distribution families, link functions, model-class lists ('OLS, WLS, GLS, GLSAR...'), test-name catalogs (Ljung-Box, Durbin-Watson, Breusch-Godfrey...), and a padded Overview ('Python's premier library') — much of it duplicated again in the 'Reference Documentation' section and in the five reference files. This matches anchor 2 (noticeably verbose, several unnecessary/padded sections) rather than anchor 1 (no extended hand-holding tutorial prose, and the code blocks are dense) and rather than anchor 3 (the padding is pervasive, not just 'some' over-explanation).

2 / 5

Actionability

Concrete, runnable code for the common cases: OLS with add_constant, summary, prediction intervals, and Breusch-Pagan; Logit with odds ratios, margeff, and AUC; ARIMA with ADF testing, ACF/PACF, and forecast frames; GLM with an overdispersion check that branches to Negative Binomial. Fits anchor 4 (mostly executable, minor gaps) rather than anchor 5 because snippets use undefined placeholders (X_data, y_binary, y_series) and named capabilities like mixed models and VAR get no example at all.

4 / 5

Workflow Clarity

Four numbered workflows with explicit checkpoints and conditional feedback ('Check for overdispersion' → 'If overdispersed, fit Negative Binomial'; 'Test for stationarity' → 'Difference if non-stationary'; 'Refit with robust SEs if needed'). This matches anchor 4 — clear sequence with most checkpoints — rather than anchor 3 (checkpoints are explicit, not merely implied) and falls short of anchor 5 because error-recovery loops for convergence failures and final validation steps are named but not elaborated.

4 / 5

Progressive Disclosure

Five real, one-level-deep reference files, each clearly signposted inline ('See references/linear_models.md for...'), summarized in a Reference Documentation section, and backed by grep navigation patterns. Structure matches anchor 4 rather than anchor 5 because the capability enumerations and the Reference Documentation summaries largely duplicate content already carried by the reference files, inflating SKILL.md unnecessarily.

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 description: it states what the skill covers, gives explicit and concrete 'use when' triggers, and cleanly differentiates itself from a sibling skill. The only weakness is slightly incomplete natural-keyword coverage (no 'regression', 'logistic', or 'forecasting') and noun-style rather than action-verb phrasing.

DimensionReasoningScore

Specificity

Names concrete capabilities — 'specific model classes (OLS, GLM, mixed models, ARIMA) with detailed diagnostics, residuals, and inference' and 'coefficient tables' — covering the library's main areas with minor gaps (no mention of formula API, model comparison, or named tests). It matches anchor 4 (several specific items, minor gaps) rather than anchor 5 because it is noun-heavy rather than action-verb driven, and rather than anchor 3 because it lists far more than 1-2 concrete actions.

4 / 5

Completeness

Explicitly answers both: what ('Statistical models library for Python... detailed diagnostics, residuals, and inference... coefficient tables') and when ('Use when you need specific model classes (OLS, GLM, mixed models, ARIMA)... Best for econometrics, time series, rigorous inference'). Matches anchor 5 exactly; it even adds routing guidance to the statistical-analysis skill, so it cannot be anchor 4 where 'when' is only weakly specified.

5 / 5

Trigger Term Quality

Includes natural terms users would say: 'OLS, GLM, mixed models, ARIMA', 'econometrics', 'time series', 'residuals'. A few common variations are missing — 'regression', 'logistic', 'forecasting', and 'statistical tests' never appear — so it fits anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers (specific model-class acronyms like OLS/ARIMA and the library name itself) and an explicit boundary clause ('For guided statistical test selection with APA reporting use statistical-analysis') that minimizes overlap risk — matching anchor 5 rather than anchor 4's 'minor overlap risk'.

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 (624 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
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.