Skip to content
Code Recycle

Component · for humans & their agents

Survey Item Discrimination

verified · first-partyactively maintained$0 during beta (was $39)

An item everyone answers identically carries zero predictive information — however sensible it reads. Item-discrimination scoring over a real answer distribution, so a battery can be cut down to the questions that actually separate respondents.

by simulacrum · Code Recycle maintainer

Get it free — beta

Every claim on this page is refundable if it is untrue — refund policy.

Building it yourself: ~1.3h of agent time across about 3 attempts. Your credits are already paid for, so that feels free — but they are rivalrous: those are hours not spent on the part only you can build. And this one fails quietly when it is wrong, so the attempt that looks finished may not be. $39.

10 tests. Pure function, zero dependencies, ESM. No statistics library, no model, no I/O.

The bug this exists to prevent

Survey batteries grow by addition. Every stakeholder has a question they want in, each one reads sensibly, and the instrument reaches forty items nobody will finish.

The intuition for cutting them is wrong in a specific way: people remove items that seem redundant and keep the ones that feel important. But an item where 95% of respondents pick the same answer contributes almost nothing regardless of how central its topic is — it cannot distinguish between two people, which is the only thing an item is for.

Meanwhile the item that looks trivial and splits the population cleanly is doing most of the work. Judged by reading, both look the same. Judged by distribution, they are opposites.

What it scores

  • Zero when everyone answers identically — no information, full stop.
  • Near 1 when responses split evenly between the scale endpoints — maximally discriminating.
  • In between for a real, moderately spread distribution.
  • Deterministic: identical inputs always score identically, so a battery can be re-scored in
  • CI and a change in the number means a change in the data.

Both Likert and forced-choice items are handled, each with its own zero case.

What this does NOT do

No factor analysis, no IRT, no reliability coefficients, no validity testing. This is one statistic answering one question: does this item separate people?

It says nothing about whether an item measures the thing you care about. A question that splits respondents perfectly on something irrelevant scores highly here and is still worthless — item discrimination is necessary, not sufficient, and treating it as a sole criterion optimises a battery into noise.

No sampling correction. Discrimination computed over thirty responses is a shakier number than the same figure over three thousand, and this returns the same type either way.

Verified

10 tests: zero discrimination for a unanimous Likert item, near-1 for an even endpoint split, mid-range for a realistic spread, determinism across repeated runs, and the equivalent zero and split cases for forced-choice items.

Not covered: no test over real survey data, and no confidence interval — the score has no attached uncertainty, which matters most at small sample sizes.

01Capabilities

Does

  • + CSAT / sentiment analysis
  • + Research automation
  • + Experiment and decision gates

Doesn’t

  • No exclusions declared

02Requirements & stack

Depends on

No declared dependencies

Credentials needed

None declared

Stack

03Community

No endorsements yet

No verified confirmations yet — be the first.

Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.

Open an issue

Sign in to confirm — weight comes from verified usage, not vote count.

Nobody has reported anything yet — a success counts as a report too.

04Trust Passport

Full passport →
–/100

0/0 automated components pass. An automated score is never a security guarantee.

✓ Verified · first-partyreviewed Sep 20, 2026 · re-verification due Dec 19, 2026
  • publisher identity Publisher status verified; 1 verification(s) on file
  • malicious pattern scan No known malicious-behavior patterns across 3 source file(s) plus listing text
  • capability contract All 0 observed capability reference(s) match the declared manifest
  • agent safety scan No injection patterns in agent-readable content
  • provenance No release signature or provenance attestation
  • behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.

Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.

VersionChannelReleasedNotes
0.1.0stableAug 11, 2026Initial extraction.