AD list-experiment
Designs and diagnoses list experiments, or the item count technique. Covers whether indirect measurement is warranted, control-list construction against ceiling and floor effects, double-list and direct-question-pairing designs, difference-in-means and maximum-likelihood estimators through ictreg, no-design-effect and no-liar assumptions with ict.test and ict.hausman.test, common-failure corrections, and power planning for the substantial precision penalty. Use when the user measures a sensitive attitude or behavior and asks about list experiments, item count, unmatched count, veiled questioning, or an implausible prevalence estimate. Sensitivity-bias decisions go to survey-design.
Designs and diagnoses list experiments, or the item count technique.
As a process D 48/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
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
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4469 tokens
- 100Steps. 54 steps
- 100Consistency. Name and required fields are in place
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
- +1No license
- +2Single-language instructions
- +3Description length 690: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.