Menu

Individual skill

peopleops-evidence-reconciliation

0upvotes

Use for PeopleOps Console solver tasks that require reconciling employees, leave assignments, payroll assignments or accrual batches, recruitment openings, remote-work or policy cases, document folders, notices/messages, and audit evidence, then returning strict JSON from an answer_template.json. Trigger on prompts mentioning PeopleOps Console, onboarding closeout, leave source precedence, payroll readiness, recruitment reconciliation, policy-case folder or formal-notice quality, audit scope, normalized business labels, or final control results.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_012/fewshot/opencode/fewshot_attempt_03/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 task prompt and `input/payloads/answer_template.json` before querying the app. Treat the template as the output contract: required keys, JSON types, enum labels, and list element types come from it.
2. Identify the target entity from the prompt: employee, case, opening, candidate, payroll/accrual batch, audit event, policy, document folder, or notice packet.
3. Prefer the API over manual UI navigation when available. Use the base URL from the prompt or environment, then fetch the relevant endpoints. See [references/api_map.md](references/api_map.md).
4. Build an evidence table before filling JSON: field, candidate value, source record, status, scope, and exclusions. Summaries are hints, not controlling evidence when structured records conflict.
5. Apply the source-precedence and control rules in [references/evidence_rules.md](references/evidence_rules.md). The recurring pattern is to choose approved/submitted/current authoritative records and explicitly exclude drafts, superseded records, stale summaries, or adjacent-scope audit events.
6. Fill every template key exactly once. Use enum values exactly as written in the template, numbers as numbers, booleans as booleans, and lists as arrays of IDs or labels as requested.
7. Validate the JSON locally before final response. Return only the JSON object, with no markdown or explanation, when the prompt asks for JSON only.

## Bundled Helpers
Back to top