Menu

Individual skill

peopleops-evidence-reconciliation

0upvotes

Solve PeopleOps Console reconciliation and control-review tasks that require producing exact JSON from a provided answer_template.json. Use when the task asks Codex to verify onboarding closeout, leave source precedence, payroll assignment/accrual readiness, remote-work or lifecycle case folder readiness, formal notice defects, recruitment outcomes, audit scope, excluded records, normalized business labels, or final People Ops control actions.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_012/fewshot/opencode/fewshot_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 Evidence Reconciliation

## Core Workflow

1. Read the user prompt and `input/payloads/answer_template.json` before inspecting data. Treat the template as the output contract: include exactly those keys, preserve key names, use only listed enum labels, and emit JSON only.
2. Get the task environment base URL from the prompt or local environment-access file. Use only allowed read endpoints unless the prompt explicitly asks for a permitted write such as posting a case comment.
3. Prefer API evidence over visual browsing when available. The UI can help orient navigation, but the API is easier to search, join, and verify.
4. Build a small evidence table for each requested field: selected value, source endpoint, source record id, excluded adjacent records, and reason. Do not rely on case summaries alone when the prompt asks for authoritative records, submitted records, assignment history, formal notices, folders, policies, ledgers, audit details, or messages.
5. Validate the final object against the template, then return only the JSON object. Do not include markdown, citations, explanations, or fields not present in the template.

## Useful Helpers

- `scripts/fetch_peopleops_context.py` fetches allowed PeopleOps API endpoints and optionally searches them for employee ids, case ids, opening ids, candidate ids, names, or record ids.
- `scripts/validate_answer.py` checks a draft JSON answer against the local answer template for exact keys, scalar/list types, and enum labels.