hrm-theory-development
Use when the theoretical argument and hypotheses are the bottleneck for a Human Resource Management (Wiley "HRM") manuscript — building an HRM/OB mechanism (AMO, HR-system strength, signaling, social exchange) and deriving testable predictions a priori. Builds the theory; it does not run the analysis (hrm-data-analysis).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-theory-development --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Theory Development (hrm-theory-development) ## When to trigger - Hypotheses read as bald predictions ("HPWS is positively related to performance") with no mechanism - You have results and are tempted to write hypotheses around them (HARKing risk) - The argument leans on one borrowed citation rather than a developed HRM logic - A mediator (the "black box" between HR practices and outcomes) is in the data but not theorized - A reviewer says "the theory is thin," "why would this practice produce this outcome?", or "the mechanism is a label, not an argument" ## The HRM theory bar HRM publishes work that **explains how HR practices and systems shape attitudes, behavior, and performance — and under what conditions.** The contribution must be theoretical, empirical, and/or methodological, but even an empirically driven paper needs an articulated mechanism written *before* the results are known. Crucially, the theory should sit close enough to HR design that a **practice implication** falls out of it; pure psychological process with no HR-system anchor drifts toward PPsych/JAP. For **qualitative / theory-building** work, HRM does not expect a priori hypotheses; it expects a grounded mode
- When to trigger
- The HRM theory bar
- The HRM theory toolkit (use the right lens)
- Multilevel and "black box" discipline
- Checklist
- Anti-patterns
- Output format
What does the hrm-theory-development skill do?
Use when the theoretical argument and hypotheses are the bottleneck for a Human Resource Management (Wiley "HRM") manuscript — building an HRM/OB mechanism (AMO, HR-system strength, signaling, social exchange) and deriving testable predictions a priori. Builds the theory; it does not run the analysis (hrm-data-analysis).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-theory-development --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.