SKILLEMALL.ai

BD 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.

synthetic-sciences/OpenScience Hermes author: synthetic-sciences Apache-2.0 6 files body ≈ 4 811 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Statistical models library for Python.

As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureData and analyticstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 327 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "dependencies"

Process rating: all ten parameters 48/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 60Steps. 202 steps, 7 vague phrases
  • 70Execution cost. Instruction body is 4811 tokens
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress
  • low 11 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 327: enough signal without eating the budget
  • +4Structure: 38 headings
  • +3Step-by-step instructions: 202 items
  • +4Has examples (9 code blocks)
  • +4Reference files are cited in the instructions (5 of 5)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.