Menu

Individual skill

peopleops-reconcile

0upvotes

Solve PeopleOps Console reconciliation and control tasks that require strict JSON answers from a task-provided answer template. Use when asked to verify onboarding closeout, remote-work or lifecycle folder readiness, leave source precedence, payroll assignment/accrual readiness, recruitment outcome packets, notice defects, audit scope, or cross-module People Ops controls against the running task environment.

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

Use this skill to solve PeopleOps Console tasks by reading the current prompt, the task's answer template, and the live read-only business evidence. Produce only the JSON object requested by the template.

## Core Workflow

1. Read the prompt and `input/payloads/answer_template.json` first. Treat the template as the output schema and the only source for normalized enum labels.
2. Use the configured task environment base URL from the prompt or environment access file. Prefer direct API reads over UI inspection when endpoints are available.
3. Pull a broad evidence snapshot before deciding:
   - `GET /api/manifest`
   - `GET /api/summary`
   - `GET /api/employees`
   - `GET /api/cases`
   - `GET /api/policies`
Back to top