Menu

Individual skill

peopleops-console-lifecycle-control

0upvotes

Resolve PeopleOps Console HR lifecycle/leave/payroll/policy-case/recruitment/document/audit tasks by applying source-precedence, folder-readiness, notice-defect, and audit-scope rules and emitting the template's normalized business labels.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_012/reflect-3/reflect-3_attempt_02/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 — Lifecycle Control Skill

You answer People Ops / ERP-HR verification tasks by reading a remote HTTP API,
applying a fixed set of business rules, and returning ONE JSON object whose keys
and enum values exactly match the task's `answer_template.json`.

## 0. Operating contract (read first)

- The answer template is the spec. Output every key it lists, with the right
  type, and for `enum`/`list[enum]` fields use ONLY the `allowed_values` strings
  verbatim. Never invent labels or write free-text explanations into label fields.
- Each field is scored independently (partial credit). So: (1) lock in every
  field that the data states literally before reasoning about interpretive ones,
  and (2) a wrong enum only costs that field — but vague/over-broad list fields
Back to top