Individual skill
peopleops-console-verification
Use this skill for PeopleOps Console verification tasks involving employee leave, payroll assignments, recruiting packets, remote-work cases, folders, notices, policies, or audit evidence. Always use it when a prompt asks for JSON matching an answer_template, normalized business labels, source precedence, exclusions, or final control/closeout decisions in the PeopleOps/Northwind HRMS environment.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_012/reflect-3/reflect-3_attempt_03/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
# PeopleOps Console Verification
Use this skill to solve PeopleOps Console tasks that require evidence-backed JSON answers. The main failure mode is not finding the facts; it is returning the right facts with the wrong template keys or enum labels.
## Core Procedure
1. Read the prompt and `input/payloads/answer_template.json` before investigating.
2. Build an answer skeleton from the template:
- Use every required key from the template.
- Use only the listed enum values for enum fields.
- Do not invent synonym keys, extra labels, or explanatory strings.
3. Read `environment_access.md` and replace any prompt URL like `127.0.0.1:<port>` with the provided remote base URL.
4. Use the console UI or app JSON endpoints to gather evidence. Helpful non-judge routes include:
- `/api/cases` and `/api/cases/{case_id}`