Menu

Individual skill

peopleops-lifecycle-reconciliation

0upvotes

Use this skill for PeopleOps Console tasks that ask Codex to reconcile HR lifecycle records across employees, cases, leave, payroll, recruitment, documents, messages, policies, and audit evidence. Trigger whenever the task mentions onboarding closeout, leave source precedence, payroll assignment readiness, accrual readiness, remote-work exception closeout, folder readiness, formal notices, recruitment reconciliation, candidate outcomes, or normalized PeopleOps answer templates.

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

Use this skill to produce JSON answers for PeopleOps Console reconciliation tasks. The recurring challenge is not finding one record; it is choosing the authoritative record when summaries, drafts, notices, folders, and audit events disagree.

## Operating Procedure

1. Read the prompt and the answer template first.
   - Treat the template as the schema of record.
   - Copy enum values exactly from the template; do not invent synonyms.
   - Keep arrays in the requested shape. If the prompt says candidate arrays contain IDs only, do not include names or explanations.

2. Open the environment using the provided remote base URL.
   - If the prompt shows `127.0.0.1:<port>`, replace it with the remote base URL from the environment access file.
   - The UI is useful for orientation, but the underlying JSON endpoints are the fastest way to verify records.
Back to top