Menu

Individual skill

peopleops-lifecycle-control-solver

0upvotes

Use this skill for PeopleOps Console tasks that ask you to reconcile onboarding, leave, payroll, remote-work, recruitment, document, notice, or audit evidence into a strict JSON answer template. It is especially useful when prompts mention source precedence, submitted versus draft records, folder readiness, notice defects, payroll handoff, accrual readiness, or normalized business labels.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_012/self/self_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 Lifecycle Control Solver

Use this skill to solve PeopleOps Console reconciliation tasks from the prompt, the provided answer template, and the remote PeopleOps environment. The core habit is to collect evidence from the authoritative module records first, then use case summaries only as orientation or fallback.

## Setup

1. Read `environment_access.md` in the task workspace and use its remote base URL in place of any `127.0.0.1:<port>` URL shown in the prompt.
2. Read the prompt and `input/payloads/answer_template.json` before gathering evidence. The template is the contract for field names, types, and allowed enum labels.
3. Prefer direct JSON endpoints for repeatability, while using the browser UI when visual confirmation is helpful.
4. Do not use any judge endpoint or feedback source. Return only the requested JSON when the prompt asks for JSON-only output.

Useful endpoints:

```text
Back to top