hrm-writing-style
GitHub针对Wiley HRM期刊稿件,优化摘要、引言及行文风格。聚焦双受众(学者与从业者)语境,强化理论精确性与实践启示,规范构念标签与因果表述,提升贡献清晰度与可读性,适用于后期润色阶段。
Trigger Scenarios
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-writing-style -g -y
SKILL.md
Frontmatter
{
"name": "hrm-writing-style",
"description": "Use when the prose, abstract, or introduction are the bottleneck for a Human Resource Management (Wiley \"HRM\") manuscript — making the HRM\/OB argument land and surfacing the practitioner takeaway in the journal's dual-audience voice. Late-stage polish; it does not fix the theory or design (hrm-theory-development, hrm-methods)."
}
Writing Style (hrm-writing-style)
When to trigger
- The abstract states what you did but not what the field (and HR leaders) now know
- The introduction takes a page to reach the contribution
- The practitioner takeaway is invisible or relegated to a boilerplate final paragraph
- Construct labels drift across sections (HPWS / high-commitment / HR system used loosely)
- A reviewer says "hard to follow," "the contribution is unclear," or "reads like a tech report"
HRM's dual-audience voice
HRM is read by scholars and by reflective practitioners, and the journal demands both a scholarly advance and a practice payoff. The prose must therefore do two things at once: be theoretically precise (named mechanisms, defined constructs, careful causal language) and accessible (a reader can extract what to do without decoding jargon). Write for an intelligent HR scholar who is not a specialist in your exact niche — and remember the EIC screens for fit and relevance, so the contribution must be legible on page one.
The introduction in five moves (the AMJ/management arc, HRM-tuned)
- Hook the phenomenon — a real HR problem (turnover, the implementation gap, AI and skills, well-being) that matters to organizations and people.
- Name the conversation and the tension — the specific HRM literature and the unresolved question (not "little is known").
- State the contribution — both halves — the scholarly advance and the practice implication, explicitly, in the first two pages.
- Preview the approach — theory, design, level, and what the evidence shows, in a sentence or two.
- Forecast the payoff — what scholars and practitioners take away.
The abstract that survives the screen
Pack four things into ~150–200 words (confirm the current limit on the author page; 检索于 2026-06;以官网为准): the question, the design (sample, level, method), the key finding with a magnitude, and the dual contribution. An abstract that omits the practice payoff signals the wrong journal to the screening editor.
Sentence-level craft for HRM
- Construct discipline. Use one label per construct, defined once, throughout. Drift between "HPWS," "high-commitment," and "HR system" reads as conceptual confusion.
- Causal honesty. Match verbs to the design — "is associated with" for cross-sectional, "increases" only when identification supports it. Referees punish causal language the design cannot back.
- Level clarity. Make the level explicit in prose ("at the unit level," "employees within establishments"), not just in the method.
- Active, economical sentences. Prefer "managers who enact the system" over "the system that is enacted by managers." Cut hedging stacks ("it may possibly suggest").
- Earn the practice paragraph. Replace boilerplate ("managers should pay attention") with a specific, conditional recommendation grounded in your effect.
Checklist
- Abstract states question, design (sample/level/method), finding + magnitude, dual contribution
- The contribution — both halves — is on page one or two, not the discussion
- One label per construct, defined once, consistent throughout
- Causal verbs match the identification the design supports
- Level of analysis is explicit in the prose
- The practice implication is specific and conditional, not boilerplate
- Jargon is defined or replaced; an HR scholar outside the niche can follow it
- APA style and house conventions respected (检索于 2026-06;以官网为准)
Anti-patterns
- Buried contribution: the "so what" arrives only in the discussion
- Method-report tone: what-we-did with no what-it-means
- Construct drift: synonyms used as if interchangeable
- Causal overreach: "X improves Y" from cross-sectional data
- Boilerplate practice paragraph: generic implications that fit any paper
- Hedge stacking: "may possibly tentatively suggest"
- Abstract without a payoff: scholarly result only, no practice signal
Output format
【Journal】Human Resource Management (Wiley "HRM")
【Skill】hrm-writing-style
【Abstract】question + design + finding/magnitude + dual contribution? [Y/N]
【Contribution placement】both halves on p.1–2? [Y/N]
【Construct discipline】one label per construct? [Y/N]
【Causal language】matches identification? [Y/N]
【Practice paragraph】specific & conditional (not boilerplate)? [Y/N]
【Next skill】hrm-submission
Version History
- 1839142 Current 2026-07-05 13:19


