From jams-skills
Matches research design to theoretical claims for JAMS manuscripts, covering construct validity, survey/SEM, secondary-data identification, experiments, and meta-analysis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jams-skills:jams-methodsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- The design may not actually support the theoretical claim
JAMS publishes several empirical genres; the validity question is genre-specific. Pick the genre, then clear its bar.
Because so many JAMS papers are survey-based, the measurement model is where reviewers concentrate fire. Make the chain airtight: each construct has a conceptual definition first, then a measure whose items match that definition (content validity), then evidence of reliability (CR/α), convergent validity (AVE ≥ .50, significant loadings), and discriminant validity. For discriminant validity, report HTMT (threshold typically .85/.90) in addition to Fornell–Larcker — reviewers increasingly treat Fornell–Larcker alone as insufficient. If you adapt an existing scale, justify the changes and re-validate; if you create a new scale, follow a recognized scale-development procedure (item generation, purification, validation on a fresh sample). A reflective construct measured with formative items (or vice versa) is a fatal mismatch.
A method is "JAMS-ready" only when it supports both the theoretical claim and the managerial reading. After choosing the design, write one line: the variation / manipulation that identifies the focal effect, and one line: the managerial quantity the estimates will produce. If the design cannot deliver a managerially interpretable magnitude (e.g., a standardized path with no translatable unit), plan now to add a study, an elasticity, or a scenario analysis — discovering this after data collection is expensive. Hand the executed plan to jams-data-analysis, which carries the same managerial-magnitude discipline into reporting.
For experiments and field studies, pre-registration (AsPredicted / OSF) strengthens the inference and pre-empts a HARKing or p-hacking critique; report any deviations from the plan. Across all genres, design the data and analysis pipeline now so it can satisfy the Springer data/code availability policy at acceptance — keep raw data, cleaning scripts, and estimation code organized and documented from the start rather than reconstructing them under deadline. A clean, shareable pipeline is also the cheapest insurance against a reviewer who asks to see a specific robustness check.
【Genre】survey-SEM / secondary-data / experiment / meta-analysis
【Claim】causal / structural / descriptive
【Construct validity】reliability + AVE + discriminant (FL/HTMT): pass/fix
【CMV (survey)】design + test (marker/CFA-marker): pass/fix/NA
【Identification (secondary)】strategy + key assumption: [...] / NA
【Experiment】manipulation + mediation + moderation + power: pass/fix/NA
【Meta】frame + coding reliability + bias checks: pass/fix/NA
【Next skill】jams-data-analysis
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin jams-skillsMatches a JM 'big tent' research design (experiment, field study, survey, secondary data, qualitative) to a substantive marketing question, prioritizing field realism and identification.
Matches research design to causal claims for JMR manuscripts: experimental design, causal identification (IV/DiD/RDD/matching), and structural estimation. Adapts to JMR's rigor and replication expectations.
Helps match research design to theoretical claims for JOM manuscripts — construct validity, common-method bias, endogeneity, multilevel structure, and meta-analysis coding protocols.