Menu

Individual skill

peopleops-console-controls

0upvotes

Solve PeopleOps Console verification and reconciliation tasks that require collecting HR case, employee, leave, payroll, recruitment, document, message, policy, and audit evidence from the task environment, applying source-precedence and draft-exclusion rules, and returning strict JSON matching an answer template.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_012/fewshot/deepagents/fewshot_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 11, 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 Controls

## Core Workflow

1. Read the prompt and `input/payloads/answer_template.json` first. The template is the output contract: preserve every key, use the declared scalar types, and use only the listed enum labels.
2. Extract target identifiers from the prompt, such as employee IDs, case IDs, opening IDs, candidate IDs, payroll or leave assignment IDs, policy IDs, audit IDs, attachment IDs, and relevant periods.
3. Gather evidence from the task environment before answering. Prefer API data over UI reading when available because the records are structured. Use the UI only as a cross-check or when the prompt requires it.
4. Build a short evidence table for yourself with: source endpoint, record ID, status, period/effective date, scope, and why the record is included or excluded.
5. Apply the precedence and exclusion rules below. Do not use case summaries, employee profile summaries, messages, or notifications as authoritative when assignment, ledger, folder, policy, offer, or audit detail exists for the same field.
6. Emit only the final JSON object. Do not include markdown, comments, citations, or explanatory fields.

## Evidence Collection

Use `scripts/peopleops_collect.py` to collect a filtered evidence bundle:
Back to top