Individual skill
peopleops-lifecycle-reconciliation
Solve PeopleOps Console lifecycle verification tasks by reconciling authoritative HR, leave, payroll, recruitment, document, notice, policy, and audit evidence into exact-template JSON.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_012/fewshot/naive/fewshot_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
Use this skill for PeopleOps Console tasks that ask you to verify lifecycle readiness, source precedence, recruitment outcomes, leave setup, payroll assignment, folder readiness, formal notice quality, or scoped audit evidence.
## Core Rule
Build the answer from the current task's `input/payloads/answer_template.json`, not from memory. The template is the schema and the source of every allowed normalized label. Return exactly the template's fields, with no extra fields, no markdown, and no explanatory text.
## Access Pattern
1. Open the configured `<TASK_ENV_BASE_URL>`.
2. Log in with credentials from the prompt if the app asks for them. Some environments are already authenticated.
3. Prefer direct business JSON endpoints when available because they reduce UI transcription errors. Useful endpoints usually mirror the app modules:
- `/api/manifest`
- `/api/summary`
- `/api/employees`