CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

statsmodels

Fits and diagnoses Python statistical models including OLS, GLM, discrete and mixed models, ARIMA and SARIMAX. Supports coefficient inference, marginal effects, model comparison and time series forecasting with explicit design and uncertainty checks. Used for econometrics and statistical modeling; for guided test selection with APA reporting, see statistical-analysis.

Quality

80%

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

Quality

Content

71%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, expert-calibrated body: terse best practices with version-specific API guidance, four well-sequenced workflows with validation and remediation loops, and excellent one-level-deep reference architecture with all linked files present. The main weakness is redundancy — the reference files are listed and described twice — plus the absence of any inline runnable code example.

Suggestions

Collapse the 'Reference Documentation' section (which re-describes linear_models.md, glm.md, discrete_choice.md, time_series.md, stats_diagnostics.md already linked above) into a single navigation point; keep one annotated link per file.

Add one minimal inline executable snippet (e.g., OLS fit with missing="raise" plus results.summary()) so the body's concrete parameter guidance is demonstrated without opening quick_start_guide.md.

Move the 'Getting Help' link list and citation instructions into a reference file to reclaim body tokens; they are rarely needed at decision time.

DimensionReasoningScore

Conciseness

Best Practices and Pitfalls are lean, expert-level one-liners, but the body pays back redundancy: the 'Reference Documentation' section re-lists and describes the same reference files already linked under 'Quick Start, Capabilities, and Model Selection', and the 'Getting Help' and 'Citing' sections add tokens of marginal operational value. Not 4 because the duplicated reference listing is more than a minor trim; not 2 because most sections assume competence and avoid concept explanations.

3 / 5

Actionability

Guidance is concrete at the parameter level — 'use missing="raise" during construction', 'has_constant="add" for a new array', 'use result_object=True and named fields for ADF/KPSS', 'prefer rng=' — plus an exact install command and executable rg patterns. Not 5 because the body contains no inline executable Python example; runnable code is deferred entirely to the quick-start reference, leaving a gap for a user who has not opened it.

4 / 5

Workflow Clarity

Four workflows are clearly sequenced with named validation checkpoints and conditional remediation loops ('Check for overdispersion / If overdispersed, fit Negative Binomial', 'Refit with robust SEs if needed', 'Check for convergence issues'). Not 5 because checkpoints name the check but defer the mechanics (which statistic, what criterion) to references, a minor validation gap.

4 / 5

Progressive Disclosure

The body is a genuine overview: all 9 referenced files exist in references/ (109–904 lines each), links are one level deep, each is signaled with a one-line scope description, and bulk detail is appropriately split out of the ~240-line SKILL.md. The duplicate listing under 'Reference Documentation' is a conciseness issue rather than a navigation defect, so it does not drop this below the clear-overview anchor.

5 / 5

Total

16

/

20

Passed

Description

80%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: concrete, comprehensive capability statements in third person with domain-specific trigger terms and explicit disambiguation from a sibling skill. The main gap is that the 'when' clause names a domain rather than listing concrete user trigger phrases, and a few natural synonyms (e.g., plain 'regression') are missing.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Fits and diagnoses Python statistical models including OLS, GLM, discrete and mixed models, ARIMA and SARIMAX", "coefficient inference, marginal effects, model comparison and time series forecasting" — covering the domain comprehensively with no vague filler. Not 4 because coverage spans fitting, diagnostics, inference, comparison and forecasting rather than having minor gaps.

5 / 5

Completeness

Both what ("Fits and diagnoses... models... Supports coefficient inference, marginal effects, model comparison and time series forecasting") and when ("Used for econometrics and statistical modeling") are explicitly present. Not 5 because the 'when' clause states a domain of use rather than concrete trigger phrases a user would say; not 3 because an explicit 'Used for' clause exists and even disambiguates the sibling statistical-analysis skill.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "OLS", "GLM", "ARIMA", "SARIMAX", "econometrics", "statistical modeling", "time series forecasting" are terms users actually say. Not 5 because plain-language synonyms like "regression", "logistic regression" and "p-values" are absent, leaving a few natural trigger phrasings uncovered; not 3 because coverage well exceeds 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Library-specific model names (SARIMAX, ARIMA, OLS, GLM) form a clear niche and the trailing pointer ('for guided test selection with APA reporting, see statistical-analysis') disambiguates the nearest neighbor. Not 5 because broad phrases like "Python statistical models" could still overlap with generic statistics or ML-skills descriptions.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

K-Dense-AI/scientific-agent-skills

Path

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.