agentsclimarketplace

Error analysis

Skill StamKavid/last-ds-mile/skills/error-analysis

Slices residuals and errors to find where a model fails, instead of reporting one aggregate score. Use when someone asks where a model gets things wrong, or wants the worst-performing segments named. Use when an overall metric looks acceptable but the result is not yet trusted. Use when debugging why specific cases come out wrong.From its SKILL.md

Install
npx -y skills add StamKavid/last-ds-mile --skill error-analysis

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.7 KB, as published. Nobody here has run it

error-analysis

Overview

An aggregate metric answers "how good on average" — error analysis answers "good for whom, and wrong how." This is the systematic version of what /ds-evaluate does inline, useful any time a deeper failure-mode investigation is needed.

When to Use

  • After a model's aggregate metric is known and acceptable, before trusting it broadly.
  • Debugging a specific complaint ("the model is bad for X") by finding the actual pattern, not guessing.
  • NOT for: picking the metric itself (see metric-selection) — this skill assumes the metric is already chosen and asks where performance diverges from that metric's average.

Core Process

  1. Compute out-of-fold (not in-sample) predictions for every row — error analysis on training-set-fit predictions is optimistic and misleading.
  2. Slice error by every dimension the decision cares about: a segment, a time period, a feature range, a subgroup — not just one arbitrary cut.
  3. Pull the worst N individual mispredictions and look for a shared trait (not just eyeball them one at a time with no hypothesis).
  4. State the finding as a concrete, actionable pattern ("underperforms on X because Y"), not a vague "some errors exist."

Techniques/Patterns

TechniqueWhat it reveals
Slice metric by categorical subgroup (segment, region, neighborhood, product line)Whether one subgroup is silently much worse than the aggregate suggests
Slice metric by a continuous feature's quantile bins (e.g. price quintile, age decile)Whether performance degrades at one end of a range — often the extremes
Residual vs. predicted-value plot (or a groupby summary of the same)Systematic over/under-prediction bias at specific value ranges, not just noise
Worst-N mispredictions table, sorted by absolute errorConcrete cases to trace back to a shared root cause (a data issue, an undermodeled feature, an edge case)
Residual vs. time (for any temporal data)Whether the model is drifting/degrading as time moves away from the training window

Common Rationalizations

RationalizationReality
"The aggregate metric is good, that's enough"This is ds-method's "one aggregate metric is enough to report" rationalization by another name — a good average can hide a subgroup or range where the model is unusable.
"I looked at a few bad predictions, nothing jumped out"A handful of examples eyeballed without a slicing table rarely surfaces a pattern — run the systematic slices first, then look at examples within the worst slice.

See ds-method for the shared Rationalizations that apply to every stage.

Red Flags

Red FlagWhat it usually means
Every slice has been checked except the one the stakeholder actually cares about mostThe analysis technically satisfies "slice performance exists" while missing the decision-relevant cut — go back and add it

See ds-method's Red Flags — "overall metric is good but never checked per-slice" is this skill's direct trigger.

Verification

  • Predictions used for error analysis are out-of-fold, not in-sample.
  • At least one slice matches a dimension the actual decision (from /ds-frame) cares about, not just a convenient one.
  • The worst mispredictions were examined for a shared pattern, not just listed.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.