Individual skill

peopleops-console-reconciliation

Solve PeopleOps Console reconciliation tasks that require verifying leave, payroll, recruitment, policy-case, folder, notice, or audit records and returning a normalized JSON answer from the provided template. Use this skill whenever the prompt mentions PeopleOps Console, employee leave precedence, payroll assignment readiness, recruitment outcome packets, case folder readiness, formal notice defects, audit evidence, or any task that asks you to choose authoritative submitted or approved records and exclude drafts or stale summaries.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_012/fewshot/cc/fewshot_attempt_01/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 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

These tasks are evidence-selection problems. The prompt names the entity and the answer template defines the exact JSON shape. Work from the template first, then collect only the records needed to justify each field.

## Compatibility

Use the task environment API or console available from the prompt. Prefer the API when it exposes the same record data, because it is easier to inspect exact fields and status values.

## Workflow

1. Read the prompt carefully and identify the entity type and identifier.
2. Open `input/payloads/answer_template.json` and copy the field names and allowed enum values exactly.
3. Inspect the smallest set of authoritative records needed to answer the prompt.
4. Resolve conflicts by source precedence, not by recency alone.