Agent skill · Data & Analytics

hrm-methods

Use when the research design is the bottleneck for a Human Resource Management (Wiley "HRM") manuscript — matching multilevel structure, multi-source/multi-wave timing, construct validity, and common-method-bias defenses to the theoretical claim. Designs the study; it does not run the estimation (hrm-data-analysis).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-methods --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: Human-Resource-Management-Skills/skills/hrm-methods/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Research Design & Methods (hrm-methods) ## When to trigger - Predictor and outcome are single-source, single-wave, self-reported (common-method-bias risk) - The theory is cross-level (unit HR system → individual outcome) but data are one level - HR-system or practice constructs lack validated measures or a defended aggregation - The causal claim ("HPWS raises performance") rests on cross-sectional correlation - A reviewer says "the design cannot test this hypothesis," "CMB," or "HPWS adoption is endogenous" ## HRM accepts any rigorous design — the bar is fit, not method HRM welcomes qualitative, quantitative, meta-analytic, and critical-review work, exploratory or confirmatory, inductive/deductive/abductive. The judgment is **fit and rigor**, plus the journal's demand that the design support a **practice-relevant** conclusion. Match the design to the claim: | Theoretical claim | Design that earns it | |-------------------|----------------------| | HR practice/system → individual attitudes & behavior | Multi-source, multi-wave survey; predictor and outcome from different sources/times | | Unit HR system → individual outcomes (cross-level) | Nested data (employees in units); HLM-ap

What's inside
Steps it walks through
  1. When to trigger
  2. HRM accepts any rigorous design — the bar is fit, not method
  3. Designing against the threats HRM referees punish
  4. Level-of-analysis discipline
  5. Execution bridge (StatsPAI / Stata MCP)
  6. Checklist
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the hrm-methods skill do?

Use when the research design is the bottleneck for a Human Resource Management (Wiley "HRM") manuscript — matching multilevel structure, multi-source/multi-wave timing, construct validity, and common-method-bias defenses to the theoretical claim. Designs the study; it does not run the estimation (hrm-data-analysis).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-methods --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going