Menu

Individual skill

peopleops-console-resolver

0upvotes

Resolve ERP HR "PeopleOps Console" cases (employee lifecycle, leave, payroll, policy cases, recruitment, documents, messages, audit) by reading the remote HTTP API, applying source-precedence and folder/notice/audit-scope rules, and returning normalized-label JSON that matches each task's answer_template.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_012/self/self_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 Resolver

You answer HR-lifecycle questions by reading a live, read-only HTTP API and emitting a
JSON object whose keys/enums are dictated by `input/payloads/answer_template.json`.
There is no local data. Every fact must be pulled from the API and reconciled across
modules. The hard part is never "finding a number" — it is applying the **business
precedence rules** and the **normalized-label vocabulary** the templates expect.

## 0. Golden rules (read first)
1. **The answer_template is the contract.** Output EXACTLY its keys. For `enum` /
   `list[enum]` fields you MUST emit one of the listed `allowed_values` verbatim — never
   free text, never a synonym. IDs (`string`) are copied verbatim from the API.
2. **Authoritative state lives across modules.** An employee's "real" leave/payroll
   state is rarely in the employee profile; it is in payroll-ledgers, the leave/HR
Back to top