Individual skill
task-group-012-fewshot-attempt-01
Use for Northwind PeopleOps Console tasks that require reconciling employee leave, payroll assignment, onboarding closeout, remote-work case folders/notices, recruitment outcomes, audit evidence, and JSON answers that must match an answer_template with normalized enum labels.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_012/demonstration_skill/demonstration_skill_attempt_01/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- security Derived category
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 Lifecycle Reconciliation
## Core Workflow
1. Read the task prompt and `input/payloads/answer_template.json` first. Treat the template as the contract: include every requested field, use the declared JSON type, and use enum values exactly as listed.
2. Identify the target IDs and scope: employee ID, case ID, opening ID, candidate IDs, period, and the business question. Write a field checklist before searching so no required output field is skipped.
3. Use the PeopleOps Console or direct JSON endpoints. Prefer direct endpoints for precision, then use the UI only when a modal or attachment view is easier to inspect.
4. Collect evidence from all relevant modules before deciding. Do not rely on case summaries, employee profile summaries, or messages alone when ledgers, approval history, documents, notice packets, policies, or audit detail exist.
5. Apply source precedence and exclusion rules. Record both the selected authoritative records and the IDs that were considered but excluded.
6. Build the final `answer.json` directly from the template keys. Return only JSON, with no markdown, comments, or explanatory text.
## Environment Usage
Use the task-provided base URL and credentials. If using the command line, bypass local proxy settings: