CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

statsmodels

Statsmodels is Python's premier library for statistical modeling, providing tools for estimation, inference, and diagnostics across a wide range of statistical methods.

Quality

61%

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/AI-Agents-Safe-Coding-Skills-claude/skills/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

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.

The body is well-structured with executable examples and genuinely useful workflows and pitfalls, but it is padded with redundant sections and, critically, all five of its reference-file pointers lead to files that do not exist in the bundle. Trimming the duplicate reference summaries and either shipping or removing the reference files would raise quality substantially.

Suggestions

Ship the five referenced files (references/linear_models.md, glm.md, discrete_choice.md, time_series.md, stats_diagnostics.md) or remove the pointers and the grep/search-pattern guidance that targets them.

Delete the 'Reference Documentation' section that re-summarizes each reference file already pointed to inline, and trim 'Core Statistical Modeling Capabilities' model/feature enumerations that restate standard statsmodels knowledge.

Make quick-start examples self-contained by defining or clearly labeling placeholder inputs (X_data, y, y_binary, df), and cut the 'Getting Help' section of public documentation links.

DimensionReasoningScore

Conciseness

The ~600-line body is noticeably verbose: the 'Reference Documentation' section re-summarizes five reference files already pointed to inline, the 'Core Statistical Modeling Capabilities' sections enumerate model families and features Claude already knows, and 'Getting Help' links to public docs. These are whole padded/redundant sections, not isolated spots, so it sits below the 'mostly efficient' anchor.

2 / 5

Actionability

Concrete, mostly executable code throughout (add_constant, OLS/Logit/ARIMA fits, het_breuschpagan, get_forecast().summary_frame(), formula API, a full CV loop). Minor gaps: placeholder variables like X_data, y, and df are never defined, so examples are not fully copy-paste ready.

4 / 5

Workflow Clarity

Four numbered workflows with explicit checkpoints and conditional feedback branches ('If overdispersed, fit Negative Binomial', 'Difference if non-stationary', 'Refit with robust SEs if needed', holdout/CV validation). Not anchor 5 because some checkpoints are named without an executable command (e.g. 'Check for influential observations').

4 / 5

Progressive Disclosure

Pointers are clearly signaled and one level deep, but the actual bundle contains no references/ directory at all — all five referenced files (linear_models.md, glm.md, discrete_choice.md, time_series.md, stats_diagnostics.md) are dangling, and the detailed content remains inlined in SKILL.md. Structure exists on paper but nothing is actually split out.

3 / 5

Total

13

/

20

Passed

Description

53%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 in third person and clearly identifies the library, but it stays at the level of generic capability categories without concrete actions or any 'use when' trigger clause. Adding natural trigger phrases like regression, logistic regression, time series, and ARIMA would materially improve it.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when fitting regressions (OLS, logistic, Poisson), analyzing time series (ARIMA, SARIMAX, VAR), running statistical tests, or interpreting model diagnostics.'

Replace abstract capability wording ('estimation, inference, and diagnostics') with concrete model families and tasks users would name (regression, GLM, time series forecasting, hypothesis testing).

Drop marketing fluff like 'Python's premier library' to free description budget for specific triggers.

DimensionReasoningScore

Specificity

Names the domain ('statistical modeling') and lists actions ('estimation, inference, and diagnostics'), but these are abstract capability categories rather than concrete actions like fitting regressions or forecasting time series, and 'premier library' is fluff.

3 / 5

Completeness

The 'what' is clear ('providing tools for estimation, inference, and diagnostics') but there is no 'when to use' clause or equivalent trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords ('Statsmodels', 'statistical modeling', 'inference', 'diagnostics') but misses the natural phrases users would actually say such as 'regression', 'OLS', 'logistic regression', 'time series', or 'statistical tests'.

3 / 5

Distinctiveness Conflict Risk

Naming 'Statsmodels' explicitly gives a clear niche with distinct triggers; minor overlap risk remains with generic scipy/sklearn-style statistical-analysis skills because no concrete model families are named.

4 / 5

Total

13

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (615 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

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

12

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/statsmodels/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.