Menu

Individual skill

peopleops-console-reconciliation

0upvotes

Resolve PeopleOps Console evidence-reconciliation tasks across recruitment, leave, payroll, onboarding closeout, folder/notice review, and audit-heavy case checks. Use when a prompt asks you to open the runner URL, inspect authoritative records, apply source precedence over drafts or stale summaries, and return JSON that matches a provided answer template.

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

## Overview

Use this skill for PeopleOps Console tasks that ask for a final JSON record built from the console, case detail, ledgers, policy views, messages, notices, or audits.

## Workflow

1. Read the prompt and answer template before browsing the app.
2. Open the configured runner URL, sign in with the supplied credentials, and inspect the workspace named in the prompt.
3. Use [evidence-map.md](references/evidence-map.md) to identify the authoritative source for each field family.
4. Prefer submitted, approved, or assignment-history records over draft, stale, or summary-only records.
5. Match the answer template exactly. Use the template's enum labels as written, keep arrays as IDs only, and preserve booleans and numbers exactly.
6. Exclude records outside the decision scope, especially draft records and adjacent audit events that do not directly support the final decision.
Back to top