Menu

Individual skill

peopleops-console-reconciliation

0upvotes

Use this skill for PeopleOps Console reconciliation tasks that ask for JSON answers about onboarding closeout, leave source precedence, payroll assignment readiness, recruitment outcomes, document folder readiness, formal notice quality, audit scope, or normalized business labels. Trigger whenever a task mentions People Ops, HRMS, employee onboarding, payroll/leave assignments, recruitment packets, policy cases, folders, notices, or audit events.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_012/reflect-3/reflect-3_attempt_01/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 Reconciliation

## Core SOP

1. Read the prompt and `input/payloads/answer_template.json` before collecting data. The template is the contract: use its exact field names, enum labels, booleans, numbers, and array element types.
2. Use `environment_access.md` for the active base URL. When a prompt shows `127.0.0.1:<port>`, replace it with the remote base URL from the environment file.
3. Gather evidence by entity ID and by human name. Prefer the structured API behind the console over visual scraping when available.
4. Read policy documents referenced by the case or record before choosing normalized labels. Policy text often explains source precedence and draft exclusions.
5. Resolve source precedence, then fill the JSON. Do not narrate inside fields that expect normalized labels.
6. Before finalizing, check every array for the required element type. Candidate arrays should contain candidate IDs only when the prompt says so; file arrays should contain exact filenames.

## Useful Console Endpoints

The portal commonly exposes these JSON routes:
Back to top