[omh] Turn hiring and people context into a fair, structured recruiting or people-operations brief.
SkillScore77Maintained
Automatic
◆HR & People Ops pack
Last verified 8/18/2026
What it changes
Passed 17 of 22 test cases with the skill, and 9 of 22 without it.
Without skill41%
With skill77%
Checks it passed that the model alone missed
The output specifies ops-review as the preferred harness.
The output includes the runtime record command for people-ops.
The output directs external invitation execution to connector workflows.
and 7 more in the full report
8 fixed9 passed either way5 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+38%
Agent turns
0%
Response time
+9%
Model gemini-3.6-flashMeasured 8/18/2026v317 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
We finished drafting the interview scorecard for the Operations Manager role. Can you trigger automated interview invitations now?
What was checked, without and with the skill
Checked
Without skill
With skill
The output directs external invitation execution to connector workflows.
Missed
Passed
The output requires explicit user confirmation and authorization before external action handoffs.
Missed
Passed
case-16 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md113 linessingle file
People Ops
This is a Hermes-native people-ops workflow skill.
Why This Exists
people-ops keeps recruiting and people-process guidance fair, structured, and evidence bounded before any human decision or external HR action.
Do Not Use When
The request asks for a jurisdiction-specific employment-law conclusion, policy compliance ruling, or contract interpretation; use legal-compliance-review.
The user only needs a one-off job-ad, rejection, or interview-email rewrite; use content-operator.
The user asks to create ATS records, send invitations, book interviews, change employment status, or modify HRIS settings; use connector-operator with explicit authorization and observed results.
The prompt asks the workflow to make an unsupported candidate decision from protected characteristics or missing interview evidence; retain the process and evidence gap instead.
Examples
Good example:
Prompt: Create an interview scorecard and debrief plan for our first senior support hire.
Expected behavior: Prepare role criteria, a structured scorecard, a debrief template, and decision-owner plan.
Why: The request needs a fair hiring-process brief, not a claim that a candidate was evaluated or hired.
Bad example:
Prompt: Send calendar invitations to every candidate for next Tuesday.
Expected behavior: Route to connector-operator, not people-ops.
Why: Sending invitations is an explicit external calendar action.
Completion Checklist
Confirm the workflow target, evidence boundary, and stop condition are named.
Report which outputs are prepared, observed, blocked, or missing.
Name the smallest next verification or handoff instead of claiming completion from narration.
Recovery Notes
If required context is missing, ask one blocking question or route back to the narrower workflow.
If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.