Creator · scdenney
Last updated · Sep 2, 2026
Reviews an existing conjoint study for threats to inference and returns prioritized findings across five areas — design integrity (attributes, profile restrictions, task count and satisficing, randomization, power), estimation (estimand clarity, reference levels, subgroups, clust
Creator · scdenney
Last updated · Sep 2, 2026
Reviews an existing conjoint study for threats to inference and returns prioritized findings across five areas — design integrity (attributes, profile restrictions, task count and satisficing, randomization, power), estimation (estimand clarity, reference levels, subgroups, clust
Creator · scdenney
Last updated · Sep 2, 2026
Reviews an existing conjoint study for threats to inference and returns prioritized findings across five areas — design integrity (attributes, profile restrictions, task count and satisficing, randomization, power), estimation (estimand clarity, reference levels, subgroups, clust
Creator · scdenney
Last updated · Sep 2, 2026
Reviews an existing conjoint study for threats to inference and returns prioritized findings across five areas — design integrity (attributes, profile restrictions, task count and satisficing, randomization, power), estimation (estimand clarity, reference levels, subgroups, clust
Sandbox only
Install targets
Codex install prompt
Install the "conjoint-diagnostics" agent skill from https://github.com/scdenney/open-science-skills/tree/main/codex/conjoint-diagnostics. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Reviews an existing conjoint study for threats to inference and returns prioritized findings across five areas — design integrity (attributes, profile restrictions, task count and satisficing, randomization, power), estimation (estimand clarity, reference levels, subgroups, clustered standard errors, multiple testing), measurement error, external validity and behavioral benchmarking, and interpretation, including the guard-rail against reading an AMCE as a majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation and interpretation choices. Building a design from scratch goes to conjoint-design, reshaping the data to conjoint-cleaning. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"scdenney-conjoint-diagnostics","task":"Install conjoint-diagnostics","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Maintenance
fresh
4d since push
Risk
Risky
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
52
64/100 Quality · 74/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision · Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
RiskyA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
52 GitHub stars
Repo activity
52 stars, 3 forks
Maintenance
4d since push
License
NOASSERTION
Install
npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add scdenney/open-science-skills --skill conjoint-diagnosticsDo not use when
Alternative
174.6K Stars
npx skills add anthropics/skills --skill frontend-design
Alternative
84.6K Stars
npx skills add Leonxlnx/taste-skill --skill design-taste-frontend
Alternative
1.8K Stars
npx skills add Alisa0808/vox-director --skill vox-director
Alternative
174.6K Stars
npx skills add anthropics/skills --skill canvas-design
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20conjoint-diagnostics%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20conjoint-diagnostics%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/scdenney-conjoint-diagnostics/install
Agent should check
Copy prompt
Task: Use conjoint-diagnostics in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20conjoint-diagnostics%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/scdenney-conjoint-diagnostics/install
Install command: npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/scdenney-conjoint-diagnostics/install
LLM text format
/api/skills/scdenney-conjoint-diagnostics/install?format=text
Find alternatives
/api/skills/search?q=conjoint-diagnostics&limit=3
Agent prompt
Use conjoint-diagnostics for this task. Review https://www.openagentskill.com/api/skills/scdenney-conjoint-diagnostics/install, then install with: npx skills add scdenney/open-science-skills --skill conjoint-diagnosticsRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/scdenney-conjoint-diagnostics
LLM text
/api/registry/manifest/scdenney-conjoint-diagnostics?format=text
Install alias
/api/registry/install/scdenney-conjoint-diagnostics
Recommend
/api/registry/recommend?task=Use%20conjoint-diagnostics%20in%20an%20agent%20workflow&limit=3
Agent fit
Coding agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Coding agents
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
CHECK52 GitHub stars
Stars/forks activity
CHECK52 stars, 3 forks; issue activity unavailable in current metadata
Recent maintenance
PASS4d since push
License clarity
PASSNOASSERTION
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Search private knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Workflow fit
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Alternative shortlist
Similar skills that may fit this task.
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
Turn one topic into a narrated Vox-style paper-collage explainer or ad video, from script through captions.
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
--- name: conjoint-diagnostics description: Reviews an existing conjoint study for threats to inference and returns prioritized findings across five areas — design integrity (attributes, profile restrictions, task count and satisficing, randomization, power), estimation (estimand clarity, reference levels, subgroups, clustered standard errors, multiple testing), measurement error, external validity and behavioral benchmarking, and interpretation, including the guard-rail against reading an AMCE as a majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation and interpretation choices. Building a design from scratch goes to conjoint-design, reshaping the data to conjoint-cleaning. ---
# 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)
### 1.5 Sample and Power - Is the sample size justified with a power analysis? (Schuessler & Freitag 2020 cjpowR; Stefanelli & Lukac 2020) - What is the effective sample size (N respondents x T tasks)? - Are Type S (sign) and Type M (magnitude/exaggeration) errors considered? - For subgroup analyses, is there adequate power within each subgroup?
---
## 2. Estimation Diagnostics
### 2.1 Estimand Clarity - Verify the estimand is clearly defined (AMCE, MM, AMIE, or pAMCE) and the choice is justified. - Check whether AMCEs are interpreted with awareness that they depend on the attribute distribution used for averaging (Hainmueller et al. 2014). - Check whether MMs are used where reference-category-free comparisons are needed (Leeper et al. 2020).
### 2.2 Reference Levels - Are reference levels clearly specified and substantively meaningful? - Are AMCEs interpreted relative to the correct reference category? - For subgroup comparisons, is the reference category consistent across groups? (Leeper et al. 2020: conditional AMCEs are sensitive to reference choice)
### 2.3 Subgroup Analysis - Are subgroups defined by pre-treatment characteristics (not post-treatment)? - **Use marginal means and diff-in-MMs for subgroup comparisons**, not conditional AMCEs. (Leeper, Hobolt & Tilley 2020: conditional AMCEs are reference-category dependent and can yield arbitrary subgroup differences) - Are diff-in-MMs presented alongside MMs for interpretability? - Is heterogeneity detection systematic or ad hoc? (Robinson & Duch 2024 cjbart; Goplerud et al. 2025 FactorHet)
### 2.4 Standard Errors and Clustering - Are standard errors clustered at the respondent level? Clustering is conventional with T > 1 tasks per respondent, though Schuessler & Freitag (2020) show the adjustment averages only ~2% across published conjoints and is not strictly necessary for sample causal effects. Flag clustering absent without justification, but do not auto-fail. - Is the clustering variable correctly specified? - Are confidence intervals reported? At what level? (Convention: 95%, some papers use 90% or dual CI bars)
### 2.5 Multiple Testing - How many AMCEs/MMs are estimated in total? - Is there a correction for multiple comparisons? (Liu & Shiraito 2023: >90% chance of at least one spurious significant AMCE with no correction when no true effects exist) - If no correction, is this limitation acknowledged? - Consider: Bonferroni (conservative), Benjamini-Hochberg (FDR), adaptive shrinkage (recommended as default when limited prior knowledge)
---
## 3. Measurement Error Diagnostics (Clayton et al. 2023)
Worry about measurement error whenever the study draws subgroup comparisons, reports small-to-moderate AMCEs/MMs near zero, or forgoes any IRR estimate. Conjoint responses carry **swapping error** (not classical noise): average Intra-Respondent Reliability is ~77% across Clayton et al.'s eight replications, biasing MMs toward 0.5 and AMCEs toward 0. For subgroup diff-in-AMCEs, the correction *increases* the estimated difference ~82% of the time, decreases it ~12%, and flips its sign ~5% -- uncorrected subgroup contrasts are usually understated, not overstated. Audit the study for (a) an IRR estimate or justified borrow (≈0.75 default), (b) bias correction via the `projoint` R package (Clayton et al.), and (c) sensitivity analysis across plausible IRR values if uncorrected.
> **Detailed measurement-error workflow:** see [references/measurement-error.md](references/measurement-error.md).
---
## 4. External Validity Diagnostics
### 4.1 Behavioral Benchmarking - Does the paper position its design against the Hainmueller-Hangartner-Yamamoto 2015 benchmark, or provide other behavioral validation? HHY 2015 compared conjoint and vignette estimates to a Swiss naturalization referendum natural experiment; the paired forced-choice conjoint recovered behavioral effects to within ~2 percentage points. Absent a direct behavioral benchmark, the paper should at minimum reference HHY 2015's evidence that paired forced-choice designs have strong external validity for comparable decision contexts.
### 4.2 Profile Distribution - Does the uniform attribute distribution match real-world frequencies? (de la Cuesta et al. 2022) - If not, does the paper discuss how this affects interpretation? - Are pAMCEs computed for comparison?
### 4.3 Forced Choice vs. Real-World Behavior - Does the forced-choice format accurately reflect the decision context? (Visconti & Yang 2024) - Should an abstention/neither option be offered? (Miller & Ziegler 2024: preferential abstention can produce different-sign AMCEs) - Is there a rating outcome alongside forced choice? (Treger 2025: forced-choice and rating elicit distinct preferences) - **Outcome-type robustness**: If both forced-choice and rating were collected, do AMCEs/MMs agree in sign and ranking across outcome types? Divergence is substantive, not a nuisance.
### 4.4 Attention and Salience - Does the conjoint format artificially inflate attention to attributes that respondents would ignore in real decisions? (Fu & Li 2024) - Could this lead to effect magnitude amplification, sign reversal, or importance reversal? - What real-world decision process is the conjoint trying to simulate? State the target DGP explicitly — without it, "attention inflation" cannot be assessed.
---
## 5. Interpretation Diagnostics
### 5.1 AMCE Interpretation - Does the paper correctly interpret AMCEs as average effects on choice probability, not majority preferences? (Abramson et al. 2022; Ganter 2023 sharpens this: AMCE identifies a choice-probability effect, not a parameter of the underlying preference distribution.) - Does the paper acknowledge that AMCEs depend on the distribution of other attributes? (Bansak et al. 2023 respond that AMCEs map to vote share changes) - Are AMCEs interpreted as causal effects or merely as preference rankings? - If the design relies on the SDB-mitigation argument for conjoints, is the claim hedged in light of Horiuchi, Markovich, and Yamamoto (2022)? Their direct test shows conjoints reduce SDB on some attributes but not others; the mitigation is not automatic.
### 5.2 Lexicographic / Categorical Preferences - Could respondents be applying a categorical veto (always rejecting profiles with a given attribute level)? - If so, standard AMCEs and MMs may be misleading due to co-occurrence rates across task pairs. - Are nested marginal means used to detect attribute ranking? (Dill, Howlett & Müller-Crepon 2024; `cjRank` R package) - Does the paper test whether lower-ranked attributes matter conditional on the veto attribute being held constant?
### 5.3 Magnitude Reporting - Are effect sizes reported in interpretable units (percentage points)? - Are substantive significance thresholds discussed alongside statistical significance? - Is there comparison to benchmark effect sizes in similar studies? - **Cross-attribute magnitude comparisons require caution.** Leeper et al. 2020 (fn 3): in forced-choice designs where both profiles can share a level, MMs are bounded by the co-occurrence probability (for 5 equally likely levels, MMs are bounded to ~(0.04, 0.96)); AMCEs for binary attributes are bounded to (−0.5, 0.5). Comparing raw AMCE magnitudes across attributes with different level counts conflates the effect with its mechanical bound.
### 5.4 Interaction Effects - If interactions are examined, are AMIEs used rather than conditional AMCEs? (Egami & Imai 2019) - Are interaction coefficients from dummy-coded regressions interpreted? If so, flag: these are baseline-dependent artifacts (Egami & Imai 2019). - Is there a test for whether a factor matters at all? (Ham et al. 2024 CRTConjoint: conditional randomization test) - **Configural vs additive cl
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for conjoint-diagnostics, ready for a manual X post.
conjoint-diagnostics: Reviews an existing conjoint study for threats to inference and returns prioritized findings... 52 stars https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=x
Listing + install path for conjoint-diagnostics: https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=x Install: npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to scdenney but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics/audit)
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)scdenney
@scdenney
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Frontend Design
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
174.6K StarsTaste Skill: Anti-Slop Frontend
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
84.6K StarsVox Director
Turn one topic into a narrated Vox-style paper-collage explainer or ad video, from script through captions.
1.8K StarsCanvas Design
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
174.6K StarsSandbox only
Install targets
Codex install prompt
Install the "conjoint-diagnostics" agent skill from https://github.com/scdenney/open-science-skills/tree/main/codex/conjoint-diagnostics. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Reviews an existing conjoint study for threats to inference and returns prioritized findings across five areas — design integrity (attributes, profile restrictions, task count and satisficing, randomization, power), estimation (estimand clarity, reference levels, subgroups, clustered standard errors, multiple testing), measurement error, external validity and behavioral benchmarking, and interpretation, including the guard-rail against reading an AMCE as a majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation and interpretation choices. Building a design from scratch goes to conjoint-design, reshaping the data to conjoint-cleaning. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"scdenney-conjoint-diagnostics","task":"Install conjoint-diagnostics","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Maintenance
fresh
4d since push
Risk
Risky
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
52
64/100 Quality · 74/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision · Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
RiskyA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
52 GitHub stars
Repo activity
52 stars, 3 forks
Maintenance
4d since push
License
NOASSERTION
Install
npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add scdenney/open-science-skills --skill conjoint-diagnosticsDo not use when
Alternative
174.6K Stars
npx skills add anthropics/skills --skill frontend-design
Alternative
84.6K Stars
npx skills add Leonxlnx/taste-skill --skill design-taste-frontend
Alternative
1.8K Stars
npx skills add Alisa0808/vox-director --skill vox-director
Alternative
174.6K Stars
npx skills add anthropics/skills --skill canvas-design
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20conjoint-diagnostics%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20conjoint-diagnostics%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/scdenney-conjoint-diagnostics/install
Agent should check
Copy prompt
Task: Use conjoint-diagnostics in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20conjoint-diagnostics%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/scdenney-conjoint-diagnostics/install
Install command: npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/scdenney-conjoint-diagnostics/install
LLM text format
/api/skills/scdenney-conjoint-diagnostics/install?format=text
Find alternatives
/api/skills/search?q=conjoint-diagnostics&limit=3
Agent prompt
Use conjoint-diagnostics for this task. Review https://www.openagentskill.com/api/skills/scdenney-conjoint-diagnostics/install, then install with: npx skills add scdenney/open-science-skills --skill conjoint-diagnosticsRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/scdenney-conjoint-diagnostics
LLM text
/api/registry/manifest/scdenney-conjoint-diagnostics?format=text
Install alias
/api/registry/install/scdenney-conjoint-diagnostics
Recommend
/api/registry/recommend?task=Use%20conjoint-diagnostics%20in%20an%20agent%20workflow&limit=3
Agent fit
Coding agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Coding agents
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
CHECK52 GitHub stars
Stars/forks activity
CHECK52 stars, 3 forks; issue activity unavailable in current metadata
Recent maintenance
PASS4d since push
License clarity
PASSNOASSERTION
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Search private knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Workflow fit
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Alternative shortlist
Similar skills that may fit this task.
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
Turn one topic into a narrated Vox-style paper-collage explainer or ad video, from script through captions.
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
--- name: conjoint-diagnostics description: Reviews an existing conjoint study for threats to inference and returns prioritized findings across five areas — design integrity (attributes, profile restrictions, task count and satisficing, randomization, power), estimation (estimand clarity, reference levels, subgroups, clustered standard errors, multiple testing), measurement error, external validity and behavioral benchmarking, and interpretation, including the guard-rail against reading an AMCE as a majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation and interpretation choices. Building a design from scratch goes to conjoint-design, reshaping the data to conjoint-cleaning. ---
# 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)
### 1.5 Sample and Power - Is the sample size justified with a power analysis? (Schuessler & Freitag 2020 cjpowR; Stefanelli & Lukac 2020) - What is the effective sample size (N respondents x T tasks)? - Are Type S (sign) and Type M (magnitude/exaggeration) errors considered? - For subgroup analyses, is there adequate power within each subgroup?
---
## 2. Estimation Diagnostics
### 2.1 Estimand Clarity - Verify the estimand is clearly defined (AMCE, MM, AMIE, or pAMCE) and the choice is justified. - Check whether AMCEs are interpreted with awareness that they depend on the attribute distribution used for averaging (Hainmueller et al. 2014). - Check whether MMs are used where reference-category-free comparisons are needed (Leeper et al. 2020).
### 2.2 Reference Levels - Are reference levels clearly specified and substantively meaningful? - Are AMCEs interpreted relative to the correct reference category? - For subgroup comparisons, is the reference category consistent across groups? (Leeper et al. 2020: conditional AMCEs are sensitive to reference choice)
### 2.3 Subgroup Analysis - Are subgroups defined by pre-treatment characteristics (not post-treatment)? - **Use marginal means and diff-in-MMs for subgroup comparisons**, not conditional AMCEs. (Leeper, Hobolt & Tilley 2020: conditional AMCEs are reference-category dependent and can yield arbitrary subgroup differences) - Are diff-in-MMs presented alongside MMs for interpretability? - Is heterogeneity detection systematic or ad hoc? (Robinson & Duch 2024 cjbart; Goplerud et al. 2025 FactorHet)
### 2.4 Standard Errors and Clustering - Are standard errors clustered at the respondent level? Clustering is conventional with T > 1 tasks per respondent, though Schuessler & Freitag (2020) show the adjustment averages only ~2% across published conjoints and is not strictly necessary for sample causal effects. Flag clustering absent without justification, but do not auto-fail. - Is the clustering variable correctly specified? - Are confidence intervals reported? At what level? (Convention: 95%, some papers use 90% or dual CI bars)
### 2.5 Multiple Testing - How many AMCEs/MMs are estimated in total? - Is there a correction for multiple comparisons? (Liu & Shiraito 2023: >90% chance of at least one spurious significant AMCE with no correction when no true effects exist) - If no correction, is this limitation acknowledged? - Consider: Bonferroni (conservative), Benjamini-Hochberg (FDR), adaptive shrinkage (recommended as default when limited prior knowledge)
---
## 3. Measurement Error Diagnostics (Clayton et al. 2023)
Worry about measurement error whenever the study draws subgroup comparisons, reports small-to-moderate AMCEs/MMs near zero, or forgoes any IRR estimate. Conjoint responses carry **swapping error** (not classical noise): average Intra-Respondent Reliability is ~77% across Clayton et al.'s eight replications, biasing MMs toward 0.5 and AMCEs toward 0. For subgroup diff-in-AMCEs, the correction *increases* the estimated difference ~82% of the time, decreases it ~12%, and flips its sign ~5% -- uncorrected subgroup contrasts are usually understated, not overstated. Audit the study for (a) an IRR estimate or justified borrow (≈0.75 default), (b) bias correction via the `projoint` R package (Clayton et al.), and (c) sensitivity analysis across plausible IRR values if uncorrected.
> **Detailed measurement-error workflow:** see [references/measurement-error.md](references/measurement-error.md).
---
## 4. External Validity Diagnostics
### 4.1 Behavioral Benchmarking - Does the paper position its design against the Hainmueller-Hangartner-Yamamoto 2015 benchmark, or provide other behavioral validation? HHY 2015 compared conjoint and vignette estimates to a Swiss naturalization referendum natural experiment; the paired forced-choice conjoint recovered behavioral effects to within ~2 percentage points. Absent a direct behavioral benchmark, the paper should at minimum reference HHY 2015's evidence that paired forced-choice designs have strong external validity for comparable decision contexts.
### 4.2 Profile Distribution - Does the uniform attribute distribution match real-world frequencies? (de la Cuesta et al. 2022) - If not, does the paper discuss how this affects interpretation? - Are pAMCEs computed for comparison?
### 4.3 Forced Choice vs. Real-World Behavior - Does the forced-choice format accurately reflect the decision context? (Visconti & Yang 2024) - Should an abstention/neither option be offered? (Miller & Ziegler 2024: preferential abstention can produce different-sign AMCEs) - Is there a rating outcome alongside forced choice? (Treger 2025: forced-choice and rating elicit distinct preferences) - **Outcome-type robustness**: If both forced-choice and rating were collected, do AMCEs/MMs agree in sign and ranking across outcome types? Divergence is substantive, not a nuisance.
### 4.4 Attention and Salience - Does the conjoint format artificially inflate attention to attributes that respondents would ignore in real decisions? (Fu & Li 2024) - Could this lead to effect magnitude amplification, sign reversal, or importance reversal? - What real-world decision process is the conjoint trying to simulate? State the target DGP explicitly — without it, "attention inflation" cannot be assessed.
---
## 5. Interpretation Diagnostics
### 5.1 AMCE Interpretation - Does the paper correctly interpret AMCEs as average effects on choice probability, not majority preferences? (Abramson et al. 2022; Ganter 2023 sharpens this: AMCE identifies a choice-probability effect, not a parameter of the underlying preference distribution.) - Does the paper acknowledge that AMCEs depend on the distribution of other attributes? (Bansak et al. 2023 respond that AMCEs map to vote share changes) - Are AMCEs interpreted as causal effects or merely as preference rankings? - If the design relies on the SDB-mitigation argument for conjoints, is the claim hedged in light of Horiuchi, Markovich, and Yamamoto (2022)? Their direct test shows conjoints reduce SDB on some attributes but not others; the mitigation is not automatic.
### 5.2 Lexicographic / Categorical Preferences - Could respondents be applying a categorical veto (always rejecting profiles with a given attribute level)? - If so, standard AMCEs and MMs may be misleading due to co-occurrence rates across task pairs. - Are nested marginal means used to detect attribute ranking? (Dill, Howlett & Müller-Crepon 2024; `cjRank` R package) - Does the paper test whether lower-ranked attributes matter conditional on the veto attribute being held constant?
### 5.3 Magnitude Reporting - Are effect sizes reported in interpretable units (percentage points)? - Are substantive significance thresholds discussed alongside statistical significance? - Is there comparison to benchmark effect sizes in similar studies? - **Cross-attribute magnitude comparisons require caution.** Leeper et al. 2020 (fn 3): in forced-choice designs where both profiles can share a level, MMs are bounded by the co-occurrence probability (for 5 equally likely levels, MMs are bounded to ~(0.04, 0.96)); AMCEs for binary attributes are bounded to (−0.5, 0.5). Comparing raw AMCE magnitudes across attributes with different level counts conflates the effect with its mechanical bound.
### 5.4 Interaction Effects - If interactions are examined, are AMIEs used rather than conditional AMCEs? (Egami & Imai 2019) - Are interaction coefficients from dummy-coded regressions interpreted? If so, flag: these are baseline-dependent artifacts (Egami & Imai 2019). - Is there a test for whether a factor matters at all? (Ham et al. 2024 CRTConjoint: conditional randomization test) - **Configural vs additive cl
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for conjoint-diagnostics, ready for a manual X post.
conjoint-diagnostics: Reviews an existing conjoint study for threats to inference and returns prioritized findings... 52 stars https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=x
Listing + install path for conjoint-diagnostics: https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=x Install: npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to scdenney but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics/audit)
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)scdenney
@scdenney
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Frontend Design
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
174.6K StarsTaste Skill: Anti-Slop Frontend
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
84.6K StarsVox Director
Turn one topic into a narrated Vox-style paper-collage explainer or ad video, from script through captions.
1.8K StarsCanvas Design
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
174.6K StarsSandbox only
Install targets
Codex install prompt
Install the "conjoint-diagnostics" agent skill from https://github.com/scdenney/open-science-skills/tree/main/codex/conjoint-diagnostics. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Reviews an existing conjoint study for threats to inference and returns prioritized findings across five areas — design integrity (attributes, profile restrictions, task count and satisficing, randomization, power), estimation (estimand clarity, reference levels, subgroups, clustered standard errors, multiple testing), measurement error, external validity and behavioral benchmarking, and interpretation, including the guard-rail against reading an AMCE as a majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation and interpretation choices. Building a design from scratch goes to conjoint-design, reshaping the data to conjoint-cleaning. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"scdenney-conjoint-diagnostics","task":"Install conjoint-diagnostics","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Maintenance
fresh
4d since push
Risk
Risky
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
52
64/100 Quality · 74/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision · Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
RiskyA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
52 GitHub stars
Repo activity
52 stars, 3 forks
Maintenance
4d since push
License
NOASSERTION
Install
npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add scdenney/open-science-skills --skill conjoint-diagnosticsDo not use when
Alternative
174.6K Stars
npx skills add anthropics/skills --skill frontend-design
Alternative
84.6K Stars
npx skills add Leonxlnx/taste-skill --skill design-taste-frontend
Alternative
1.8K Stars
npx skills add Alisa0808/vox-director --skill vox-director
Alternative
174.6K Stars
npx skills add anthropics/skills --skill canvas-design
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20conjoint-diagnostics%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20conjoint-diagnostics%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/scdenney-conjoint-diagnostics/install
Agent should check
Copy prompt
Task: Use conjoint-diagnostics in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20conjoint-diagnostics%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/scdenney-conjoint-diagnostics/install
Install command: npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/scdenney-conjoint-diagnostics/install
LLM text format
/api/skills/scdenney-conjoint-diagnostics/install?format=text
Find alternatives
/api/skills/search?q=conjoint-diagnostics&limit=3
Agent prompt
Use conjoint-diagnostics for this task. Review https://www.openagentskill.com/api/skills/scdenney-conjoint-diagnostics/install, then install with: npx skills add scdenney/open-science-skills --skill conjoint-diagnosticsRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/scdenney-conjoint-diagnostics
LLM text
/api/registry/manifest/scdenney-conjoint-diagnostics?format=text
Install alias
/api/registry/install/scdenney-conjoint-diagnostics
Recommend
/api/registry/recommend?task=Use%20conjoint-diagnostics%20in%20an%20agent%20workflow&limit=3
Agent fit
Coding agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Coding agents
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
CHECK52 GitHub stars
Stars/forks activity
CHECK52 stars, 3 forks; issue activity unavailable in current metadata
Recent maintenance
PASS4d since push
License clarity
PASSNOASSERTION
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Search private knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Workflow fit
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Alternative shortlist
Similar skills that may fit this task.
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
Turn one topic into a narrated Vox-style paper-collage explainer or ad video, from script through captions.
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
--- name: conjoint-diagnostics description: Reviews an existing conjoint study for threats to inference and returns prioritized findings across five areas — design integrity (attributes, profile restrictions, task count and satisficing, randomization, power), estimation (estimand clarity, reference levels, subgroups, clustered standard errors, multiple testing), measurement error, external validity and behavioral benchmarking, and interpretation, including the guard-rail against reading an AMCE as a majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation and interpretation choices. Building a design from scratch goes to conjoint-design, reshaping the data to conjoint-cleaning. ---
# 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)
### 1.5 Sample and Power - Is the sample size justified with a power analysis? (Schuessler & Freitag 2020 cjpowR; Stefanelli & Lukac 2020) - What is the effective sample size (N respondents x T tasks)? - Are Type S (sign) and Type M (magnitude/exaggeration) errors considered? - For subgroup analyses, is there adequate power within each subgroup?
---
## 2. Estimation Diagnostics
### 2.1 Estimand Clarity - Verify the estimand is clearly defined (AMCE, MM, AMIE, or pAMCE) and the choice is justified. - Check whether AMCEs are interpreted with awareness that they depend on the attribute distribution used for averaging (Hainmueller et al. 2014). - Check whether MMs are used where reference-category-free comparisons are needed (Leeper et al. 2020).
### 2.2 Reference Levels - Are reference levels clearly specified and substantively meaningful? - Are AMCEs interpreted relative to the correct reference category? - For subgroup comparisons, is the reference category consistent across groups? (Leeper et al. 2020: conditional AMCEs are sensitive to reference choice)
### 2.3 Subgroup Analysis - Are subgroups defined by pre-treatment characteristics (not post-treatment)? - **Use marginal means and diff-in-MMs for subgroup comparisons**, not conditional AMCEs. (Leeper, Hobolt & Tilley 2020: conditional AMCEs are reference-category dependent and can yield arbitrary subgroup differences) - Are diff-in-MMs presented alongside MMs for interpretability? - Is heterogeneity detection systematic or ad hoc? (Robinson & Duch 2024 cjbart; Goplerud et al. 2025 FactorHet)
### 2.4 Standard Errors and Clustering - Are standard errors clustered at the respondent level? Clustering is conventional with T > 1 tasks per respondent, though Schuessler & Freitag (2020) show the adjustment averages only ~2% across published conjoints and is not strictly necessary for sample causal effects. Flag clustering absent without justification, but do not auto-fail. - Is the clustering variable correctly specified? - Are confidence intervals reported? At what level? (Convention: 95%, some papers use 90% or dual CI bars)
### 2.5 Multiple Testing - How many AMCEs/MMs are estimated in total? - Is there a correction for multiple comparisons? (Liu & Shiraito 2023: >90% chance of at least one spurious significant AMCE with no correction when no true effects exist) - If no correction, is this limitation acknowledged? - Consider: Bonferroni (conservative), Benjamini-Hochberg (FDR), adaptive shrinkage (recommended as default when limited prior knowledge)
---
## 3. Measurement Error Diagnostics (Clayton et al. 2023)
Worry about measurement error whenever the study draws subgroup comparisons, reports small-to-moderate AMCEs/MMs near zero, or forgoes any IRR estimate. Conjoint responses carry **swapping error** (not classical noise): average Intra-Respondent Reliability is ~77% across Clayton et al.'s eight replications, biasing MMs toward 0.5 and AMCEs toward 0. For subgroup diff-in-AMCEs, the correction *increases* the estimated difference ~82% of the time, decreases it ~12%, and flips its sign ~5% -- uncorrected subgroup contrasts are usually understated, not overstated. Audit the study for (a) an IRR estimate or justified borrow (≈0.75 default), (b) bias correction via the `projoint` R package (Clayton et al.), and (c) sensitivity analysis across plausible IRR values if uncorrected.
> **Detailed measurement-error workflow:** see [references/measurement-error.md](references/measurement-error.md).
---
## 4. External Validity Diagnostics
### 4.1 Behavioral Benchmarking - Does the paper position its design against the Hainmueller-Hangartner-Yamamoto 2015 benchmark, or provide other behavioral validation? HHY 2015 compared conjoint and vignette estimates to a Swiss naturalization referendum natural experiment; the paired forced-choice conjoint recovered behavioral effects to within ~2 percentage points. Absent a direct behavioral benchmark, the paper should at minimum reference HHY 2015's evidence that paired forced-choice designs have strong external validity for comparable decision contexts.
### 4.2 Profile Distribution - Does the uniform attribute distribution match real-world frequencies? (de la Cuesta et al. 2022) - If not, does the paper discuss how this affects interpretation? - Are pAMCEs computed for comparison?
### 4.3 Forced Choice vs. Real-World Behavior - Does the forced-choice format accurately reflect the decision context? (Visconti & Yang 2024) - Should an abstention/neither option be offered? (Miller & Ziegler 2024: preferential abstention can produce different-sign AMCEs) - Is there a rating outcome alongside forced choice? (Treger 2025: forced-choice and rating elicit distinct preferences) - **Outcome-type robustness**: If both forced-choice and rating were collected, do AMCEs/MMs agree in sign and ranking across outcome types? Divergence is substantive, not a nuisance.
### 4.4 Attention and Salience - Does the conjoint format artificially inflate attention to attributes that respondents would ignore in real decisions? (Fu & Li 2024) - Could this lead to effect magnitude amplification, sign reversal, or importance reversal? - What real-world decision process is the conjoint trying to simulate? State the target DGP explicitly — without it, "attention inflation" cannot be assessed.
---
## 5. Interpretation Diagnostics
### 5.1 AMCE Interpretation - Does the paper correctly interpret AMCEs as average effects on choice probability, not majority preferences? (Abramson et al. 2022; Ganter 2023 sharpens this: AMCE identifies a choice-probability effect, not a parameter of the underlying preference distribution.) - Does the paper acknowledge that AMCEs depend on the distribution of other attributes? (Bansak et al. 2023 respond that AMCEs map to vote share changes) - Are AMCEs interpreted as causal effects or merely as preference rankings? - If the design relies on the SDB-mitigation argument for conjoints, is the claim hedged in light of Horiuchi, Markovich, and Yamamoto (2022)? Their direct test shows conjoints reduce SDB on some attributes but not others; the mitigation is not automatic.
### 5.2 Lexicographic / Categorical Preferences - Could respondents be applying a categorical veto (always rejecting profiles with a given attribute level)? - If so, standard AMCEs and MMs may be misleading due to co-occurrence rates across task pairs. - Are nested marginal means used to detect attribute ranking? (Dill, Howlett & Müller-Crepon 2024; `cjRank` R package) - Does the paper test whether lower-ranked attributes matter conditional on the veto attribute being held constant?
### 5.3 Magnitude Reporting - Are effect sizes reported in interpretable units (percentage points)? - Are substantive significance thresholds discussed alongside statistical significance? - Is there comparison to benchmark effect sizes in similar studies? - **Cross-attribute magnitude comparisons require caution.** Leeper et al. 2020 (fn 3): in forced-choice designs where both profiles can share a level, MMs are bounded by the co-occurrence probability (for 5 equally likely levels, MMs are bounded to ~(0.04, 0.96)); AMCEs for binary attributes are bounded to (−0.5, 0.5). Comparing raw AMCE magnitudes across attributes with different level counts conflates the effect with its mechanical bound.
### 5.4 Interaction Effects - If interactions are examined, are AMIEs used rather than conditional AMCEs? (Egami & Imai 2019) - Are interaction coefficients from dummy-coded regressions interpreted? If so, flag: these are baseline-dependent artifacts (Egami & Imai 2019). - Is there a test for whether a factor matters at all? (Ham et al. 2024 CRTConjoint: conditional randomization test) - **Configural vs additive cl
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for conjoint-diagnostics, ready for a manual X post.
conjoint-diagnostics: Reviews an existing conjoint study for threats to inference and returns prioritized findings... 52 stars https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=x
Listing + install path for conjoint-diagnostics: https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=x Install: npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to scdenney but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics/audit)
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)scdenney
@scdenney
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Frontend Design
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
174.6K StarsTaste Skill: Anti-Slop Frontend
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
84.6K StarsVox Director
Turn one topic into a narrated Vox-style paper-collage explainer or ad video, from script through captions.
1.8K StarsCanvas Design
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
174.6K StarsSandbox only
Install targets
Codex install prompt
Install the "conjoint-diagnostics" agent skill from https://github.com/scdenney/open-science-skills/tree/main/codex/conjoint-diagnostics. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Reviews an existing conjoint study for threats to inference and returns prioritized findings across five areas — design integrity (attributes, profile restrictions, task count and satisficing, randomization, power), estimation (estimand clarity, reference levels, subgroups, clustered standard errors, multiple testing), measurement error, external validity and behavioral benchmarking, and interpretation, including the guard-rail against reading an AMCE as a majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation and interpretation choices. Building a design from scratch goes to conjoint-design, reshaping the data to conjoint-cleaning. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"scdenney-conjoint-diagnostics","task":"Install conjoint-diagnostics","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Maintenance
fresh
4d since push
Risk
Risky
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
52
64/100 Quality · 74/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision · Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
RiskyA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
52 GitHub stars
Repo activity
52 stars, 3 forks
Maintenance
4d since push
License
NOASSERTION
Install
npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add scdenney/open-science-skills --skill conjoint-diagnosticsDo not use when
Alternative
174.6K Stars
npx skills add anthropics/skills --skill frontend-design
Alternative
84.6K Stars
npx skills add Leonxlnx/taste-skill --skill design-taste-frontend
Alternative
1.8K Stars
npx skills add Alisa0808/vox-director --skill vox-director
Alternative
174.6K Stars
npx skills add anthropics/skills --skill canvas-design
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20conjoint-diagnostics%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20conjoint-diagnostics%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/scdenney-conjoint-diagnostics/install
Agent should check
Copy prompt
Task: Use conjoint-diagnostics in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20conjoint-diagnostics%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/scdenney-conjoint-diagnostics/install
Install command: npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/scdenney-conjoint-diagnostics/install
LLM text format
/api/skills/scdenney-conjoint-diagnostics/install?format=text
Find alternatives
/api/skills/search?q=conjoint-diagnostics&limit=3
Agent prompt
Use conjoint-diagnostics for this task. Review https://www.openagentskill.com/api/skills/scdenney-conjoint-diagnostics/install, then install with: npx skills add scdenney/open-science-skills --skill conjoint-diagnosticsRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/scdenney-conjoint-diagnostics
LLM text
/api/registry/manifest/scdenney-conjoint-diagnostics?format=text
Install alias
/api/registry/install/scdenney-conjoint-diagnostics
Recommend
/api/registry/recommend?task=Use%20conjoint-diagnostics%20in%20an%20agent%20workflow&limit=3
Agent fit
Coding agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Coding agents
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
CHECK52 GitHub stars
Stars/forks activity
CHECK52 stars, 3 forks; issue activity unavailable in current metadata
Recent maintenance
PASS4d since push
License clarity
PASSNOASSERTION
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Search private knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Workflow fit
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Alternative shortlist
Similar skills that may fit this task.
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
Turn one topic into a narrated Vox-style paper-collage explainer or ad video, from script through captions.
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
--- name: conjoint-diagnostics description: Reviews an existing conjoint study for threats to inference and returns prioritized findings across five areas — design integrity (attributes, profile restrictions, task count and satisficing, randomization, power), estimation (estimand clarity, reference levels, subgroups, clustered standard errors, multiple testing), measurement error, external validity and behavioral benchmarking, and interpretation, including the guard-rail against reading an AMCE as a majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation and interpretation choices. Building a design from scratch goes to conjoint-design, reshaping the data to conjoint-cleaning. ---
# 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)
### 1.5 Sample and Power - Is the sample size justified with a power analysis? (Schuessler & Freitag 2020 cjpowR; Stefanelli & Lukac 2020) - What is the effective sample size (N respondents x T tasks)? - Are Type S (sign) and Type M (magnitude/exaggeration) errors considered? - For subgroup analyses, is there adequate power within each subgroup?
---
## 2. Estimation Diagnostics
### 2.1 Estimand Clarity - Verify the estimand is clearly defined (AMCE, MM, AMIE, or pAMCE) and the choice is justified. - Check whether AMCEs are interpreted with awareness that they depend on the attribute distribution used for averaging (Hainmueller et al. 2014). - Check whether MMs are used where reference-category-free comparisons are needed (Leeper et al. 2020).
### 2.2 Reference Levels - Are reference levels clearly specified and substantively meaningful? - Are AMCEs interpreted relative to the correct reference category? - For subgroup comparisons, is the reference category consistent across groups? (Leeper et al. 2020: conditional AMCEs are sensitive to reference choice)
### 2.3 Subgroup Analysis - Are subgroups defined by pre-treatment characteristics (not post-treatment)? - **Use marginal means and diff-in-MMs for subgroup comparisons**, not conditional AMCEs. (Leeper, Hobolt & Tilley 2020: conditional AMCEs are reference-category dependent and can yield arbitrary subgroup differences) - Are diff-in-MMs presented alongside MMs for interpretability? - Is heterogeneity detection systematic or ad hoc? (Robinson & Duch 2024 cjbart; Goplerud et al. 2025 FactorHet)
### 2.4 Standard Errors and Clustering - Are standard errors clustered at the respondent level? Clustering is conventional with T > 1 tasks per respondent, though Schuessler & Freitag (2020) show the adjustment averages only ~2% across published conjoints and is not strictly necessary for sample causal effects. Flag clustering absent without justification, but do not auto-fail. - Is the clustering variable correctly specified? - Are confidence intervals reported? At what level? (Convention: 95%, some papers use 90% or dual CI bars)
### 2.5 Multiple Testing - How many AMCEs/MMs are estimated in total? - Is there a correction for multiple comparisons? (Liu & Shiraito 2023: >90% chance of at least one spurious significant AMCE with no correction when no true effects exist) - If no correction, is this limitation acknowledged? - Consider: Bonferroni (conservative), Benjamini-Hochberg (FDR), adaptive shrinkage (recommended as default when limited prior knowledge)
---
## 3. Measurement Error Diagnostics (Clayton et al. 2023)
Worry about measurement error whenever the study draws subgroup comparisons, reports small-to-moderate AMCEs/MMs near zero, or forgoes any IRR estimate. Conjoint responses carry **swapping error** (not classical noise): average Intra-Respondent Reliability is ~77% across Clayton et al.'s eight replications, biasing MMs toward 0.5 and AMCEs toward 0. For subgroup diff-in-AMCEs, the correction *increases* the estimated difference ~82% of the time, decreases it ~12%, and flips its sign ~5% -- uncorrected subgroup contrasts are usually understated, not overstated. Audit the study for (a) an IRR estimate or justified borrow (≈0.75 default), (b) bias correction via the `projoint` R package (Clayton et al.), and (c) sensitivity analysis across plausible IRR values if uncorrected.
> **Detailed measurement-error workflow:** see [references/measurement-error.md](references/measurement-error.md).
---
## 4. External Validity Diagnostics
### 4.1 Behavioral Benchmarking - Does the paper position its design against the Hainmueller-Hangartner-Yamamoto 2015 benchmark, or provide other behavioral validation? HHY 2015 compared conjoint and vignette estimates to a Swiss naturalization referendum natural experiment; the paired forced-choice conjoint recovered behavioral effects to within ~2 percentage points. Absent a direct behavioral benchmark, the paper should at minimum reference HHY 2015's evidence that paired forced-choice designs have strong external validity for comparable decision contexts.
### 4.2 Profile Distribution - Does the uniform attribute distribution match real-world frequencies? (de la Cuesta et al. 2022) - If not, does the paper discuss how this affects interpretation? - Are pAMCEs computed for comparison?
### 4.3 Forced Choice vs. Real-World Behavior - Does the forced-choice format accurately reflect the decision context? (Visconti & Yang 2024) - Should an abstention/neither option be offered? (Miller & Ziegler 2024: preferential abstention can produce different-sign AMCEs) - Is there a rating outcome alongside forced choice? (Treger 2025: forced-choice and rating elicit distinct preferences) - **Outcome-type robustness**: If both forced-choice and rating were collected, do AMCEs/MMs agree in sign and ranking across outcome types? Divergence is substantive, not a nuisance.
### 4.4 Attention and Salience - Does the conjoint format artificially inflate attention to attributes that respondents would ignore in real decisions? (Fu & Li 2024) - Could this lead to effect magnitude amplification, sign reversal, or importance reversal? - What real-world decision process is the conjoint trying to simulate? State the target DGP explicitly — without it, "attention inflation" cannot be assessed.
---
## 5. Interpretation Diagnostics
### 5.1 AMCE Interpretation - Does the paper correctly interpret AMCEs as average effects on choice probability, not majority preferences? (Abramson et al. 2022; Ganter 2023 sharpens this: AMCE identifies a choice-probability effect, not a parameter of the underlying preference distribution.) - Does the paper acknowledge that AMCEs depend on the distribution of other attributes? (Bansak et al. 2023 respond that AMCEs map to vote share changes) - Are AMCEs interpreted as causal effects or merely as preference rankings? - If the design relies on the SDB-mitigation argument for conjoints, is the claim hedged in light of Horiuchi, Markovich, and Yamamoto (2022)? Their direct test shows conjoints reduce SDB on some attributes but not others; the mitigation is not automatic.
### 5.2 Lexicographic / Categorical Preferences - Could respondents be applying a categorical veto (always rejecting profiles with a given attribute level)? - If so, standard AMCEs and MMs may be misleading due to co-occurrence rates across task pairs. - Are nested marginal means used to detect attribute ranking? (Dill, Howlett & Müller-Crepon 2024; `cjRank` R package) - Does the paper test whether lower-ranked attributes matter conditional on the veto attribute being held constant?
### 5.3 Magnitude Reporting - Are effect sizes reported in interpretable units (percentage points)? - Are substantive significance thresholds discussed alongside statistical significance? - Is there comparison to benchmark effect sizes in similar studies? - **Cross-attribute magnitude comparisons require caution.** Leeper et al. 2020 (fn 3): in forced-choice designs where both profiles can share a level, MMs are bounded by the co-occurrence probability (for 5 equally likely levels, MMs are bounded to ~(0.04, 0.96)); AMCEs for binary attributes are bounded to (−0.5, 0.5). Comparing raw AMCE magnitudes across attributes with different level counts conflates the effect with its mechanical bound.
### 5.4 Interaction Effects - If interactions are examined, are AMIEs used rather than conditional AMCEs? (Egami & Imai 2019) - Are interaction coefficients from dummy-coded regressions interpreted? If so, flag: these are baseline-dependent artifacts (Egami & Imai 2019). - Is there a test for whether a factor matters at all? (Ham et al. 2024 CRTConjoint: conditional randomization test) - **Configural vs additive cl
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for conjoint-diagnostics, ready for a manual X post.
conjoint-diagnostics: Reviews an existing conjoint study for threats to inference and returns prioritized findings... 52 stars https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=x
Listing + install path for conjoint-diagnostics: https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=x Install: npx skills add scdenney/open-science-skills --skill conjoint-diagnostics
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to scdenney but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics/audit)
[](https://www.openagentskill.com/skills/scdenney-conjoint-diagnostics?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)scdenney
@scdenney
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Frontend Design
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
174.6K StarsTaste Skill: Anti-Slop Frontend
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
84.6K StarsVox Director
Turn one topic into a narrated Vox-style paper-collage explainer or ad video, from script through captions.
1.8K StarsCanvas Design
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
174.6K StarsPermission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Usable metadata, review docs
Risk summary
Install readiness
Permission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Usable metadata, review docs
Risk summary
Install readiness
Permission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Usable metadata, review docs
Risk summary
Install readiness
Permission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Usable metadata, review docs
Risk summary
Install readiness