From jms-skills
Runs and defends quantitative (regression/SEM/robustness) or qualitative (coding/abduction/trustworthiness) analysis for JMS manuscripts, focusing on credibility of results.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jms-skills:jms-data-analysisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Estimates are in but reviewers question endogeneity, robustness, or the indirect-effect claim
JMS judges analysis by whether it credibly supports the theoretical claim, in whichever idiom the study uses. Quantitative work is held to identification and robustness standards; qualitative work is held to trustworthiness and transparency standards. Use the path that matches your design; do not import quant criteria (p-values, effect sizes) to judge a qualitative paper, or qualitative looseness into a quantitative one.
jms-methods (FE, IV/2SLS, DiD, matching) and a robustness battery — alternative measures, alternative samples, controls in/out — each tied to a named threat, not a fishing expedition.【Path】quantitative / qualitative
【Quant】estimator + why; mediation (bootstrap CI); moderation (simple slopes); robustness→threats; CMB/CFA
【Qual】coding chain (1st→2nd→dimensions); abduction made visible; quotes table; negative cases; trustworthiness
【Claim support】does the analysis carry the theoretical claim? gaps …
【Next step】jms-tables-figures
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin jms-skillsGuides transparent reporting of qualitative data-to-theory construction (coding, evidence tables, negative cases) and quantitative robustness checks for ASQ manuscripts.
Runs and validates SEM/CFA, HLM/multilevel, regression, mediation/moderation, and meta-analytic estimation for JOM manuscripts. Use when estimation and results are the bottleneck.
Guides transparent qualitative coding, process analysis, and quantitative robustness checks for Organization Studies manuscripts. Makes the evidence-to-theory link auditable.