CtrlK
BlogDocsLog inGet started
Tessl Logo

statsmodels

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

40

Quality

43%

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
SKILL.md
Quality
Evals
Security

Quality

Content

50%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides good executable code examples in its Quick Start section and references a well-organized set of reference files, but it is significantly too verbose. Large portions of the content describe statistical concepts and model types that Claude already knows, and the extensive capability listings read more like documentation than actionable skill instructions. The workflows lack concrete validation checkpoints and feedback loops.

Suggestions

Cut the 'Core Statistical Modeling Capabilities' section drastically—move the detailed model listings and feature descriptions into the reference files and keep only a brief table mapping outcome types to recommended models.

Add explicit validation checkpoints with concrete criteria to the Common Workflows (e.g., 'If Breusch-Pagan p < 0.05, switch to robust SEs or WLS' rather than just 'Test for heteroskedasticity').

Remove the 'When to Use This Skill' bullet list and the explanatory text about what each model family does—Claude knows these concepts. Focus on project-specific decision rules and gotchas.

Trim the 15-item pitfalls list to the 5-6 most non-obvious ones that Claude is actually likely to get wrong, rather than listing basic statistical knowledge.

DimensionReasoningScore

Conciseness

The skill is severely verbose at ~500+ lines. It extensively lists model types, features, and capabilities that Claude already knows (e.g., what OLS is, what Poisson regression does, what AIC/BIC are). The 'When to Use This Skill' section, the exhaustive capability listings under each model category, and the 15-item pitfalls list are largely redundant for Claude. Much of this reads like a textbook table of contents rather than actionable guidance.

2 / 5

Actionability

The Quick Start section provides executable, copy-paste ready code examples for OLS, Logistic Regression, ARIMA, and GLM. The Formula API and Model Comparison sections also have concrete code. However, the 'Core Statistical Modeling Capabilities' section is mostly descriptive lists rather than executable guidance, and the Common Workflows section lists steps without code.

4 / 5

Workflow Clarity

The four common workflows (Linear Regression, Binary Classification, Count Data, Time Series) list clear sequences of steps, but they lack explicit validation checkpoints and feedback loops. Steps like 'Check residual diagnostics' and 'Test for heteroskedasticity' are mentioned but without concrete validation criteria or error recovery paths. The GLM quick start example does show a conditional check for overdispersion, which is good, but the workflows themselves are abstract numbered lists.

3 / 5

Progressive Disclosure

The skill references five detailed reference files (linear_models.md, glm.md, discrete_choice.md, time_series.md, stats_diagnostics.md) with clear descriptions of what each contains. However, no bundle files were provided, so these references cannot be verified. More importantly, the SKILL.md itself inlines enormous amounts of content (capability lists, model descriptions, best practices) that should be in those reference files, making the main file bloated while supposedly having detailed references.

3 / 5

Total

12

/

20

Passed

Description

36%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 reads more like a marketing tagline for the statsmodels library than a functional skill description. It lacks concrete actions (e.g., specific statistical methods), has no 'Use when...' clause, and uses overly broad terminology that doesn't help Claude distinguish this skill from other statistics-related skills.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g., 'Use when the user asks about regression analysis, time series forecasting, hypothesis testing, ANOVA, or statistical diagnostics in Python.'

Replace the abstract terms 'estimation, inference, and diagnostics' with specific capabilities like 'run OLS/logistic regression, perform time series analysis (ARIMA, VAR), conduct hypothesis tests, generate summary statistics tables.'

Include natural user terms and synonyms such as 'regression', 'p-values', 'confidence intervals', 'time series', 'ARIMA', 'linear models' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (statistical modeling in Python with statsmodels) but actions are minimal and generic — 'estimation, inference, and diagnostics' are broad categories, not concrete actions like 'run OLS regression' or 'perform time series analysis'.

2 / 5

Completeness

Has a vague 'what' (tools for estimation, inference, diagnostics) but completely lacks a 'when' clause. There is no explicit trigger guidance for when Claude should select this skill.

2 / 5

Trigger Term Quality

Includes 'statsmodels', 'statistical modeling', 'estimation', 'inference', and 'diagnostics' which are relevant but misses natural user phrases like 'regression', 'time series', 'hypothesis testing', 'ANOVA', 'OLS', or 'p-value'.

3 / 5

Distinctiveness Conflict Risk

Mentioning 'statsmodels' specifically helps distinguish it from generic data science or other Python library skills, but 'statistical modeling' and 'estimation, inference, diagnostics' are broad enough to overlap with skills for scipy.stats, scikit-learn, or general statistics tasks.

3 / 5

Total

10

/

20

Passed

Validation

72%

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

Validation8 / 11 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

Total

8

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.