Virtuals Protocol Acp
Virtual-Protocol/openclaw-acp
Hire specialised agents to handle any task — data analysis, trading, content generation, research, on-chain operations, 3D printing, physical goods, gift delivery, and more.
A skill your agent uses 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…
Install Hrm Theory Development
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-theory-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hrm-theory-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Human-Resource-Management-Skills/skills/hrm-theory-development .claude/skills/hrm-theory-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hrm-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Resource-Management-Skills/skills/hrm-theory-development into .claude/skills/hrm-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hrm-theory-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Resource-Management-Skills/skills/hrm-theory-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-theory-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hrm-theory-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Human-Resource-Management-Skills/skills/hrm-theory-development .agents/skills/hrm-theory-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hrm-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Resource-Management-Skills/skills/hrm-theory-development into .agents/skills/hrm-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hrm-theory-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-theory-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hrm-theory-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Human-Resource-Management-Skills/skills/hrm-theory-development .cursor/skills/hrm-theory-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hrm-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Resource-Management-Skills/skills/hrm-theory-development into .cursor/skills/hrm-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hrm-theory-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Human-Resource-Management-Skills/skills/hrm-theory-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-theory-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hrm-theory-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Human-Resource-Management-Skills/skills/hrm-theory-development .gemini/skills/hrm-theory-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hrm-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Resource-Management-Skills/skills/hrm-theory-development into .gemini/skills/hrm-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hrm-theory-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hrm-theory-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-theory-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Human-Resource-Management-Skills/skills/hrm-theory-development .github/skills/hrm-theory-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hrm-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Resource-Management-Skills/skills/hrm-theory-development into .github/skills/hrm-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hrm-theory-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-theory-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hrm-theory-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Human-Resource-Management-Skills/skills/hrm-theory-development .opencode/skills/hrm-theory-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hrm-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Resource-Management-Skills/skills/hrm-theory-development into .opencode/skills/hrm-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hrm-theory-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
hrm-theory-development- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 615 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- HR-system strength
- SKILL.md covers When to trigger, The HRM theory bar, The HRM theory toolkit (use… and Multilevel and "black box"…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Social exchange) and deriving testable predictions a priori
What it does
Hrm Theory Development is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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).
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Recruiting and HR and Data analysis. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- HR-system strength
- Social exchange) and deriving testable predictions a priori
Example prompts
- “/hrm-theory-development”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Hrm Theory Development loads about 1.4k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 615 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 615 words, ~1,421 tokens.
Download SKILL.mdSave it as
.claude/skills/hrm-theory-development/SKILL.md (or your agent's skills folder).- name
- hrm-theory-development
- description
- 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).
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 model with emergent propositions and the same demand for a transparent mechanism. For critical reviews and meta-analyses, the "theory" is the organizing framework that turns scattered findings into a cumulative HRM claim.
The HRM theory toolkit (use the right lens)
| Mechanism family | What it explains | Process verb |
|---|---|---|
| AMO (ability–motivation–opportunity) | how a bundle of HR practices raises performance via three pathways | enables / motivates / affords |
| HR-system strength (Bowen & Ostroff) | how distinctive, consistent, consensual HR signals create a shared climate | signals / aligns |
| Social exchange / POS | why employees reciprocate investment with effort, commitment, citizenship | reciprocates / obligates |
| Signaling | how HR practices communicate intent to employees and applicants | signals / screens |
| Ability/sorting & human capital | how practices change the stock or flow of skills | selects / develops |
| AMO + climate cross-level | how unit HR systems shape individual outcomes through climate | cascades / shapes |
For each hypothesis, write the explicit chain: antecedent (HR practice/system) → mechanism (named theory + process) → outcome (defined construct, stated level) → form/direction → boundary (moderator and why the slope changes). Keep the theory at the level where the mechanism operates and flag cross-level mediation as such.
Show full SKILL.md (264 more words)Show less
Multilevel and "black box" discipline
- HRM's core debate is the HR–performance black box: do not assert a link without theorizing the intervening climate, attitudes, or capabilities, and do not infer the mechanism from a significant indirect effect alone.
- Beware construct drift: "HPWS," "high-commitment," "high-involvement," and "HR system" are not interchangeable — define yours and stay consistent.
- For multi-level theory, distinguish the intended HR system (espoused policy), the implemented system (what managers enact), and the perceived system (what employees experience); a great deal of HRM contribution lives in that gap.
Checklist
- Every hypothesis has an explicit mechanism (named HRM/OB theory + process verb), not just a predicted sign
- The HR practice/system construct is defined and not conflated with adjacent labels
- Level of analysis is stated and consistent across argument and design; cross-level paths flagged
- Mediators (the black box) and moderators are theorized a priori with substantive reasons
- Hypotheses were fixed before analysis (no HARKing)
- A theoretical-model figure maps one-to-one to the hypotheses
- The mechanism is close enough to HR design that a practice implication is visible
- At least one rival explanation (e.g., reverse causality, selection) is named
Anti-patterns
- Label-as-theory: invoking "social exchange" or "AMO" by name without using its actual logic
- Bald predictions: "practice X relates to outcome Y" with no why
- Black-box skipping: an HR→performance arrow with no theorized intervening process
- HARKing: every hypothesis supported and none surprising
- Construct conflation: HPWS / high-commitment / HR strength used as synonyms
- Level confusion: theorizing a unit-level climate effect but arguing it in individual-psychology terms
- Practice-blind theory: an elegant mechanism with no implication any HR function could act on
Output format
【Focal mechanism】AMO / HR-system strength / social exchange / signaling / human capital (process verb: ...)
【HR construct】practice / bundle / system — defined; level stated
【H1 (focal effect)】HR antecedent → mechanism → outcome; direction/form; level
【H2 (black box / mediation)】intervening climate/attitude/capability
【H3+ (boundary)】moderator + reason the slope changes
【Rival explanation addressed】reverse causality / selection / ...
【HARKing check】hypotheses fixed before analysis? yes/no
【Practice hook】what the theory implies for HR practice
【Next skill】hrm-literature-positioning, then hrm-methods© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Human-Resource-Management-Skills/skills/hrm-theory-development of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Hrm Theory Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hrm Theory Development this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Virtuals Protocol AcpVirtual-Protocol/openclaw-acp | 168 | 1 repos | ~6.4k | Automated safety check: Pass | None | |
| Business Overview Analysiszj-unicom-ai/UniEmployee | 360 | — | ~662 | Automated safety check: Pass | MIT | |
| Company Hiring Intelligencetinyfish-io/tinyfish-cookbook | 2.2k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Computes0912758806p/agentic-sop-to-work | 209 | — | ~209 | Automated safety check: Pass | MIT | |
| Manussanjay3290/ai-skills | 432 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Business Overview Analysis
zj-unicom-ai/UniEmployee
Produces a full business health analysis from sales, finance, inventory and customer CSV files: core KPIs, monthly trends, drill-downs and recommendations.
Company Hiring Intelligence
tinyfish-io/tinyfish-cookbook
Reverse-engineer what a company is building by scraping their job postings, careers page, LinkedIn Jobs, and engineering blog using TinyFish web agents.
Compute
s0912758806p/agentic-sop-to-work
A skill your agent uses to compute summary statistics (count/sum/mean/min/max) from a readings artifact, preserving the upstream source trace.
Manus
sanjay3290/ai-skills
Delegate complex, long-running tasks to Manus AI agent for autonomous execution.
Car Methods
franklee16/academic-research-skills
A skill your agent uses when the research design and identification are the bottleneck for a Contemporary Accounting Research (CAR) manuscript — choosing and defending an archival, experimental…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Hrm Theory Development
What does Hrm Theory Development do?
A skill your agent uses 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…. Hrm Theory Development is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Hrm Theory Development?
Hrm Theory Development fits situations like: HR-system strength; social exchange) and deriving testable predictions a priori.
How do I install Hrm Theory Development in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-theory-development -a claude-code`. Or copy the skill folder (Human-Resource-Management-Skills/skills/hrm-theory-development in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/hrm-theory-development in your project. Claude Code loads it when a task matches its description.
How do I install Hrm Theory Development in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-theory-development -a codex`. Or copy the skill folder (Human-Resource-Management-Skills/skills/hrm-theory-development in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/hrm-theory-development in your project. Codex loads it when a task matches its description.
Can I use Hrm Theory Development in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hrm-theory-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hrm-theory-development, .gemini/skills/hrm-theory-development, .github/skills/hrm-theory-development and .opencode/skills/hrm-theory-development in your project.
What does Hrm Theory Development need to run?
SKILL.md names no scripts, command-line tools or credentials: Hrm Theory Development is instructions for the agent only.
Does Hrm Theory Development access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Hrm Theory Development safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Hrm Theory Development use?
Hrm Theory Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Hrm Theory Development use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Hrm Theory Development?
Skills that share tags, products or a category with Hrm Theory Development: Virtuals Protocol Acp (Virtual-Protocol/openclaw-acp, 168 stars), Business Overview Analysis (zj-unicom-ai/UniEmployee, 360 stars), Company Hiring Intelligence (tinyfish-io/tinyfish-cookbook, 2.2k stars) and Compute (s0912758806p/agentic-sop-to-work, 209 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hrm Theory Development?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.