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.
Workflow Lane
- Current lane: Research and company ops (
product-docs, source-finder, web-research, research, best-practice-research, autoresearch-goal, model-optimization, inference-serving, +19 more) - research, signals, ops, and briefings.
- If intent belongs to another lane, hand back to
oh-my-hermes or name the adjacent workflow.
- Shared product, routing, compatibility, and evidence rules:
omh-routing/references/skill-common-rail.md.
Use When
Use when a team needs a role brief, hiring plan, interview rubric, candidate-debrief structure, onboarding outline, or people-process decision support.
Strong routing signals: `recruiting plan`, `hiring scorecard`, `interview scorecard`, `candidate debrief`, `채용 계획`, `면접 평가표`, `후보자 비교`
Catalog Metadata
Category: operations
Phase: people-operations
Hermes role: operator
Quality tier: evidence-gated
Reasoning demand: light
Quality bar:
- Distinguish role outcomes from proxy criteria and missing evidence.
- Keep inclusion, privacy, policy, and decision-owner gaps visible.
Handoff policy:
Keep domain framing, clarification, source/evidence synthesis, draft outputs, and next-work routing in Hermes. A prepared brief, review, reply, or plan is not an external action, approval, filing, send, publish, data mutation, implementation, review, CI, or merge claim. Prepare a connector, file, coding, or human-review handoff only when the user explicitly accepts that next step; report it only from observed evidence. Hermes can prepare fair process guidance and interview artifacts; it cannot claim a candidate was contacted, evaluated, hired, rejected, or recorded in an HR system.
Required inputs:
- role or people-process outcome
- available evidence
- decision owner
- policy constraints
Expert clarification questions:
role or people-process outcome
- English: What role or people-process outcome should this work achieve?
- Korean: 이 작업에서 어떤 역할 또는 인사 프로세스 결과를 달성해야 하나요?
Expected outputs:
- role/outcome and must-have versus trainable-criteria brief
- structured interview scorecard and evidence-based debrief template
- hiring-process, interviewer, and decision-owner plan
- inclusion, privacy, policy, and missing-evidence flags with a next route
Artifact expectations:
- prepared people-operations brief when a wrapper captures it
Safety rules:
- Keep protected characteristics and missing interview evidence out of unsupported candidate recommendations.
- Do not claim HRIS, ATS, outreach, interview, or employment-status actions occurred.
Runtime Evidence
Preferred harness for this skill: ops-review.
omh runtime record --skill people-ops --harness ops-review --status started
Record observed delegation results; otherwise return not_available or not_observed.
Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
Preserve workflow intent and stop conditions; verify before claiming completion.
Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.
1---
2name: "omh-people-ops"
3description: "[omh] Turn hiring and people context into a fair, structured recruiting or people-operations brief. Use when the user says: recruiting plan, hiring scorecard, interview scorecard, candidate debrief, 채용 계획, 면접 평가표, 후보자 비교."
4metadata:
5 hermes:
6 tags: [workflow, oh-my-hermes, operations]
7 category: operations
8 phase: people-operations
9 role: operator
10 quality_tier: evidence-gated
11---
12
13# People Ops
14
15This is a Hermes-native `people-ops` workflow skill.
16
17## Why This Exists
18
19`people-ops` keeps recruiting and people-process guidance fair, structured, and evidence bounded before any human decision or external HR action.
20
21## Do Not Use When
22
23- The request asks for a jurisdiction-specific employment-law conclusion, policy compliance ruling, or contract interpretation; use `legal-compliance-review`.
24- The user only needs a one-off job-ad, rejection, or interview-email rewrite; use `content-operator`.
25- 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.
26- 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.
27
28## Examples
29
30Good example:
31
32- Prompt: Create an interview scorecard and debrief plan for our first senior support hire.
33- Expected behavior: Prepare role criteria, a structured scorecard, a debrief template, and decision-owner plan.
34- Why: The request needs a fair hiring-process brief, not a claim that a candidate was evaluated or hired.
35
36Bad example:
37
38- Prompt: Send calendar invitations to every candidate for next Tuesday.
39- Expected behavior: Route to `connector-operator`, not `people-ops`.
40- Why: Sending invitations is an explicit external calendar action.
41
42## Completion Checklist
43
44- Confirm the workflow target, evidence boundary, and stop condition are named.
45- Report which outputs are prepared, observed, blocked, or missing.
46- Name the smallest next verification or handoff instead of claiming completion from narration.
47
48## Recovery Notes
49
50- If required context is missing, ask one blocking question or route back to the narrower workflow.
51- If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
52
53## Workflow Lane
54
55- Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `best-practice-research`, `autoresearch-goal`, `model-optimization`, `inference-serving`, `+19 more`) - research, signals, ops, and briefings.
56- If intent belongs to another lane, hand back to `oh-my-hermes` or name the adjacent workflow.
57- Shared product, routing, compatibility, and evidence rules: `omh-routing/references/skill-common-rail.md`.
58
59## Use When
60
61Use when a team needs a role brief, hiring plan, interview rubric, candidate-debrief structure, onboarding outline, or people-process decision support.
62
63 Strong routing signals: `recruiting plan`, `hiring scorecard`, `interview scorecard`, `candidate debrief`, `채용 계획`, `면접 평가표`, `후보자 비교`
64
65## Catalog Metadata
66
67Category: `operations`
68Phase: `people-operations`
69Hermes role: `operator`
70Quality tier: `evidence-gated`
71Reasoning demand: `light`
72
73Quality bar:
74
75- Distinguish role outcomes from proxy criteria and missing evidence.
76- Keep inclusion, privacy, policy, and decision-owner gaps visible.
77
78Handoff policy:
79
80Keep domain framing, clarification, source/evidence synthesis, draft outputs, and next-work routing in Hermes. A prepared brief, review, reply, or plan is not an external action, approval, filing, send, publish, data mutation, implementation, review, CI, or merge claim. Prepare a connector, file, coding, or human-review handoff only when the user explicitly accepts that next step; report it only from observed evidence. Hermes can prepare fair process guidance and interview artifacts; it cannot claim a candidate was contacted, evaluated, hired, rejected, or recorded in an HR system.
81
82Required inputs:
83
84- role or people-process outcome
85- available evidence
86- decision owner
87- policy constraints
88
89Expert clarification questions:
90- `role or people-process outcome`
91 - English: What role or people-process outcome should this work achieve?
92 - Korean: 이 작업에서 어떤 역할 또는 인사 프로세스 결과를 달성해야 하나요?
93
94Expected outputs:
95
96- role/outcome and must-have versus trainable-criteria brief
97- structured interview scorecard and evidence-based debrief template
98- hiring-process, interviewer, and decision-owner plan
99- inclusion, privacy, policy, and missing-evidence flags with a next route
100
101Artifact expectations:
102
103- prepared people-operations brief when a wrapper captures it
104
105Safety rules:
106
107- Keep protected characteristics and missing interview evidence out of unsupported candidate recommendations.
108- Do not claim HRIS, ATS, outreach, interview, or employment-status actions occurred.
109
110## Runtime Evidence
111
112Preferred harness for this skill: `ops-review`.
113
114```sh
115omh runtime record --skill people-ops --harness ops-review --status started
116```
117
118Record observed delegation results; otherwise return `not_available` or `not_observed`.
119Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
120- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
121Preserve workflow intent and stop conditions; verify before claiming completion.
122
123Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
124
125Shared product, compatibility, topology, memory, harness, and execution rules: `omh-routing/references/skill-common-rail.md`. Load it when applicable; otherwise name an unavailable capability.
rlaope