Menu

Individual skill

peopleops-reconciliation

0upvotes

Reconcile PeopleOps Console tasks and produce exact JSON answers from provided answer templates for onboarding, leave, payroll, recruitment, approval, notice, and audit/source-precedence cases. Use when a prompt points to a task runner URL or task environment and asks for authoritative records, exclusion lists, normalized enum labels, or final control results.

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

## Procedure

1. Read the prompt, the answer template, and any payload files first. Treat `input/payloads/answer_template.json` as the schema contract for the run.
2. Identify the task family from the template fields and the evidence surfaces named in the prompt.
3. Open the runner URL from the prompt and inspect the live console or its structured data surfaces with the provided credentials.
4. Pull only the records that can decide that family. Prefer structured records over summaries when both exist.
5. Use authoritative sources:
   - submitted, approved, accepted, assigned, current-period, and audit-backed records
   - treat drafts, stale profile summaries, and message-only hints as secondary unless the template asks for them
6. Separate scope tightly. Include only audit events that directly support the requested decision. Put adjacent or out-of-scope audit IDs in excluded arrays when the template provides them.
7. Assemble one JSON object that matches the template exactly.
8. Validate the draft before answering. Check key names, types, enum labels, and array contents. Use `scripts/validate_answer.py` for a mechanical check when helpful.
Back to top