ericrisco/rsc-harness / skills/people-ops
people-ops
VerifiedUse when the offer is signed and you now have to run the person — an onboarding plan from preboarding through the 30/60/90 ramp, drafting or auditing an internal policy or handbook section, standing up the recurring people rhythm (1:1s, review and goal cycles, headcount), or offboarding a leaver. NOT sourcing, interviewing or the offer itself (that is `hiring`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.6 KB |
| evals/README.md | markdown | 969 B |
| evals/cases.yaml | config | 2.7 KB |
| references/templates.md | markdown | 6.2 KB |
evals/cases.yaml
View on GitHubskill: people-ops
should_trigger:
- prompt: "Our new engineer starts Monday — build me an onboarding plan with a 30/60/90."
why: Core onboarding artifact; offer is signed and the ramp plan is the central output.
- prompt: "Draft a remote-work policy for our handbook."
why: Core policy authoring — a handbook section with the privilege-not-right framing.
- prompt: "The offer's signed, what do I actually need to have ready before day one?"
why: Non-obvious — no word "onboarding"; this is the preboarding window plus the Day-1 legal clock.
- prompt: "Plan de onboarding y un calendario de 1:1s para el nuevo fichaje."
why: Spanish; combines onboarding with the operating rhythm (weekly 1:1s).
- prompt: "Someone's leaving next week — what's our offboarding checklist?"
why: The exit moment — same-day access revocation, knowledge handoff, exit conversation.
- prompt: "This employee handbook reads like a contract — can you fix it?"
why: Policy audit; the at-will / not-a-contract guardrail is exactly people-ops territory.
should_not_trigger:
- prompt: "Write a job description and screen these 40 candidates."
route_to: hiring
why: Sourcing and screening happen before acceptance; people-ops starts at offer-signed.
- prompt: "Document our deployment release process step by step."
route_to: sop-builder
why: A generic operational procedure, not a people policy.
- prompt: "Draft the actual employment contract and NDA for this hire."
route_to: contracts
why: Legally binding instruments; the handbook people-ops writes explicitly is not a contract.
- prompt: "Write our employee-data privacy notice and GDPR record-handling policy."
route_to: gdpr-privacy
why: A statutory data-protection regime, not an internal HR policy.
capability:
- scenario: >
A 12-person startup just hired its first non-founder employee, starting Monday.
Produce the onboarding plan plus a remote-work policy section for the new handbook.
must_include:
- A 30/60/90 plan framed learn → contribute → own
- Explicit manager actions (Day-1 task, week-1 goals conversation, buddy), not only HR tasks
- Paperwork placed in preboarding, not on Day 1
- The US I-9 / E-Verify timeline WITH a jurisdiction-confirm flag (this is US; EU/UK differ; many are not at-will)
- Remote policy framed "privilege, not a right" with concrete conditions (secured devices, core-hours availability, dedicated workspace)
- An at-will + "this is not a contract" disclaimer with a signed acknowledgment
- A weekly 1:1 set up from week one
- Does NOT write the employment contract itself; defers it to contracts
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |