Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Jom Data Analysis

ASecurity

Use when running and reporting the statistical analysis for a Journal of Operations Management (JOM) empirical manuscript — measurement validity for survey constructs, identification and endogeneity for archival operations data, manipulation checks for behavioral-OM experiments, and robustness. Executes and reports the analysis; it does not design the study (jom-methods) or frame the contribution (jom-contribution-framing).

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsrustgo

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jom-data-analysis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jom Data Analysis?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Jom Data Analysis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jom-data-analysis/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jom-data-analysis)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: jom-data-analysis
description: Use when running and reporting the statistical analysis for a Journal of Operations Management (JOM) empirical manuscript — measurement validity for survey constructs, identification and endogeneity for archival operations data, manipulation checks for behavioral-OM experiments, and robustness. Executes and reports the analysis; it does not design the study (jom-methods) or frame the contribution (jom-contribution-framing).
---

# Data Analysis & Validity for Empirical OM (jom-data-analysis)

## When to trigger

- Operations data are collected and it is time to estimate and report
- You are unsure whether your estimator matches your design (survey constructs, archival panel, experiment, multilevel/nested plants)
- Reviewers (and the Empirical Research Methods Department) will probe measurement, common-method bias, or endogeneity
- A decision letter says "the analysis does not support the operational inference"

## Establish measurement before estimation (survey/behavioral)

For survey-based OM constructs, defend the measurement model first:

- **Reliability:** Cronbach's alpha and/or composite reliability for each multi-item operations scale.
- **CFA:** report fit (CFI, TLI, RMSEA, SRMR) and show the hypothesized factor structure beats plausible alternatives (one-factor, combined-factor).
- **Convergent & discriminant validity:** AVE per construct; AVE > inter-construct squared correlations (or HTMT). Report the correlation matrix with reliabilities on the diagonal.
- **Aggregation** (plant/team level): justify with ICC(1), ICC(2), r_wg(j) before aggregating respondents.
- **Qualitative/IBR:** establish trustworthiness — data structure (first-order → themes → dimensions), audit trail, representative evidence so the path from observation to construct is traceable.

## Choose the estimator that matches the design

| Operations data structure / claim                    | Estimator                                                  |
|------------------------------------------------------|-------------------------------------------------------------|
| Latent constructs, mediation, full survey model      | SEM (covariance-based) or PLS-SEM where prediction/formative |
| Nested data (respondents in plants/firms)            | Multilevel / HLM                                            |
| Archival operations panel with unit heterogeneity    | Fixed/random effects, high-dimensional FE; cluster-robust SE|
| Causal claim from secondary data                     | DiD/staggered DiD, IV/2SLS, matching, RD as the design fits |
| Count outcomes (recalls, defects, disruptions)       | Poisson / negative binomial                                 |
| Time-to-event (failure, project completion)          | Cox / parametric survival                                  |
| Manipulated operational decision                     | ANOVA/regression with manipulation & attention checks       |

Cluster standard errors to the sampling/operational structure (plant, firm, supply tie).

## Common-method bias (survey OM)

Report the *designed* separations from `jom-methods` first (temporal/source/respondent separation), then statistical evidence: a Harman single-factor test is necessary but weak — prefer a marker variable, an unmeasured latent method factor, or showing interaction effects survive. Multi-respondent dyadic data is the strongest procedural remedy.

## Endogeneity (archival OM)

Recalls, supplier ties, lean adoption, and disruptions are rarely exogenous. State the threat (selection, reverse causality, omitted operational confounds), the identification strategy, and its assumptions. Report first-stage strength for IV and parallel-trends/anticipation checks for DiD.

## Robustness

- Alternative specifications (controls in/out, alternative operational measures, subsamples by industry/regime).
- Sensitivity to identification assumptions.
- Attrition/missing-data handling (FIML/multiple imputation, not listwise by default).
- Reproducible secondary-data construction consistent with the Wiley Data Availability Statement.

## Anti-patterns

- OLS on nested plant data ignoring non-independence.
- Causal-steps mediation instead of bootstrapped indirect effects.
- Single-factor test as the sole CMB defense.
- Unaddressed endogeneity in archival operations regressions.
- p-values with no effect sizes or operational magnitude.

## Output format

```
【Measurement】alpha/CR, CFA fit, AVE/discriminant (survey) — pass/issues
【Estimator】SEM / HLM / panel-FE / DiD-IV / count / survival / experiment; SE clustering ...
【CMB / identification】designed separation + test; or endogeneity strategy + assumptions ...
【Mediation/Moderation】bootstrap CI / simple slopes reported? ...
【Robustness】...
【Next step】jom-contribution-framing
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →