Diagnose conjoint design integrity, estimation choices, and validity.
SkillScore74Maintained
Automatic
◆Research pack
Last verified 8/8/2026
What it changes
Passed 17 of 23 test cases with the skill, and 3 of 23 without it.
Without skill13%
With skill74%
Checks it passed that the model alone missed
Cites Liu & Shiraito (2023) regarding the high probability of false positive AMCEs when uncorrected.
Refers to the projoint package for computing task-pair agreement or correcting measurement error bias.
Cites Bansak & Jenke (2025) showing odd or implausible profiles have minimal impact on first-order conjoint inferences.
and 14 more in the full report
14 fixed3 passed either way6 still failing0 broke
Pass-rate lift
+61 pp
Tokens
+121%
Agent turns
0%
Response time
-9%
Model gemini-3.6-flashMeasured 8/8/2026v117 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
Here is our R script and Qualtrics survey data from a multi-task forced-choice conjoint study. Could you run an audit on our code to verify that our standard error clustering and reported empirical quantities line up with the code's implementation, and if our script doesn't already compute intra-respondent task-pair agreement, go ahead and calculate it based on attribute variations across task pairs?
What was checked, without and with the skill
Checked
Without skill
With skill
Cites the Clayton et al. (2023) §3.3 method 2 for computing within-respondent task-pair agreement as a function of attribute differences.
Missed
Passed
Refers to the projoint package for computing task-pair agreement or correcting measurement error bias.
Missed
Passed
case-02 · gemini-3.6-flash · 8/8/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md164 linessingle file
Conjoint Experiment Diagnostics
Instructions
Work through each section below for the conjoint study under review. Assess whether the study addresses each item adequately, partially, or not at all. Flag items that pose threats to inference and prioritize recommendations by severity.
Branch on input:
If a paper or manuscript is provided, proceed through Sections 1–5 sequentially and produce a verdict per section.
If analysis code or data is provided, verify the actual implementation rather than just what the paper claims: (a) confirm clustering specification, (b) confirm the estimand matches the reported quantity, (c) if IRR is unmeasured, compute within-respondent task-pair agreement as a function of attribute-level differences (Clayton et al. 2023 §3.3 method 2 / projoint).
For neighboring concerns, invoke sibling skills: conjoint-design (design choices), conjoint-cleaning (Qualtrics exports → long format), hypothesis-building (linking estimands to "If-Then" predictions), methods-reporting (full JARS/DA-RT compliance and replication archive), cross-national-design (multi-country / multilingual conjoints).
1. Design Diagnostics
1.1 Attribute and Level Selection
Are attributes conceptually distinct and non-overlapping?
Are levels realistic and mutually exclusive within each attribute?
Is the number of attributes justified? (Bansak et al. 2021 PSRM "Beyond the Breaking Point": response quality is generally robust even at 35 filler attributes, with detectable but modest satisficing — use as a ceiling, not an endorsement of 35 attributes as optimal. Distinct from Bansak et al. 2018 on task counts below.)
For cross-national or multilingual designs, verify construct equivalence of attribute labels across languages (see cross-national-design).
Are there "dominant" attributes that might crowd out attention to others?
Do the attribute levels span a meaningful range of the construct of interest?
1.2 Profile Restrictions
Are implausible or contradictory attribute combinations allowed?
If restrictions are imposed, are they documented and justified?
If no restrictions, does the paper acknowledge potential odd profiles? (Bansak & Jenke 2025: odd profiles have minimal impact on first-order inferences, but should be acknowledged)
1.3 Number of Tasks and Satisficing
How many tasks per respondent? (Bansak et al. 2018: up to 30 tasks with limited satisficing)
Are attention checks embedded? Are pass rates reported by task position?
Is there evidence of survey fatigue or satisficing in later tasks? Look for: (a) response-time distributions by task position (not just means), (b) always-same-side / always-left or always-right rates, (c) random-choice / trembling-hand rates relative to Bansak et al. 2021 baselines, (d) attention-check failure rates by task position.
Have profile-order, carryover, and fatigue assumptions been tested empirically? (Ham, Imai & Janson 2024 §3.5: CRTConjoint provides conditional randomization tests for all three of Hainmueller-Hopkins-Yamamoto 2014's identifying assumptions.)
1.4 Randomization
Is attribute-level assignment fully randomized (uniform distribution)?
If non-uniform, is this justified and documented?
Are profile-pair attributes independent or dependent? (Clayton et al. 2023 distinguish independent, dependent, and pair-level attributes)