Individual skill

peopleops-reconcile

Reconcile PeopleOps Console records across employees, leave, payroll, recruitment, policy cases, documents, messages, and audit logs. Use when a task asks for authoritative source precedence, folder or notice readiness, payroll assignment readiness, recruitment outcome reconciliation, closeout control decisions, or a normalized JSON answer from the task environment.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_012/fewshot/codex/fewshot_attempt_02/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 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 Reconcile

## Workflow
1. Open the runner manifest and summary first.
2. Read only the module records the prompt names.
3. Prefer the authoritative source for that module over profile summaries, drafts, superseded rows, or cross-module escalation notes.
4. Apply the rules in [references/api-map.md](references/api-map.md) for leave, payroll, folder, notice, recruitment, and audit evidence.
5. Match every requested field to the provided answer template and copy enum labels exactly.
6. Return JSON only.

## Decision Rules
- Treat approved or submitted assignment-history records as authoritative when they conflict with profile summaries or drafts.
- Treat current submitted salary assignments as authoritative for payroll readiness and accrual checks; exclude drafts and superseded assignments.
- Treat a folder as not ready until every required file and required tag is present.
Back to top