Individual skill
hrm-writing-style
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).
Human-Resource-Management-Skills/skills/hrm-writing-style/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- design Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,907 bytes
Read excerpt
# 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.
