Menu

Individual skill

peopleops-console-case-resolution

0upvotes

Resolve ERP HR "PeopleOps Console" lifecycle/leave/payroll/policy-case/recruitment/documents/messages/audit tasks by applying record-source precedence, folder/notice readiness gates, and scoped audit correlation, then emitting normalized enum labels.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_012/reflect-3/reflect-3_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 Console — Case Resolution Skill

You answer HR lifecycle questions for a remote read-only HTTP API. Each task gives a
business prompt plus an `answer_template.json`. Your job: read the right records,
apply the business precedence rules below, and return ONE JSON object whose keys and
enum values exactly match the template. The grader scores PER FIELD and only marks a
task fully correct on an exact match, so every field matters and wrong precedence
choices are catastrophic.

## 1. The remote API (read-only, no auth)

Base URL is given in the environment doc. All responses are JSON. `curl` GETs only.
- `GET /api/summary`, `/api/manifest` — counts/departments/seed (orientation).
- `GET /api/employees?q=&status=` — employee profile (department, salary_band,
Back to top