Menu

Individual skill

peopleops-console

0upvotes

HR operations verification in the PeopleOps Console. Use when the task involves onboarding closeout, policy case folder/notice review, recruitment reconciliation, leave source precedence, payroll assignment readiness, or any PeopleOps lifecycle verification that requires cross-referencing employees, cases, policies, payroll ledgers, recruitment packets, documents, messages, and audit events through the REST API. Triggers on PeopleOps, People Ops, employee onboarding, policy case review, recruitment reconciliation, leave policy, payroll assignment, HR verification, or closeout workflows.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_012/fewshot/codex/fewshot_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 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)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# PeopleOps Console

Verify HR lifecycle records by fetching data from the REST API, applying business-policy rules, and returning structured JSON.

## Quick Start

1. Read the task prompt for the `<TASK_ENV_BASE_URL>` and credentials.
2. Fetch all relevant API collections in parallel: `/api/employees`, `/api/cases`, `/api/policies`, `/api/payroll-ledgers`, `/api/recruitment`, `/api/documents`, `/api/messages`, `/api/audit`.
3. Drill into specific records (single case, policy, audit event, attachment) only when needed.
4. Apply the business rules from [references/business_rules.md](references/business_rules.md) and use only the normalized enum values from [references/enum_catalog.md](references/enum_catalog.md).
5. Return a single JSON object matching the answer template in the payload.

## API Reference