Menu

Individual skill

peopleops-console

0upvotes

Solve PeopleOps Console tasks that require reading employee, payroll, leave, policy, recruitment, audit, document, case, and message data from a REST API, applying business precedence rules to select authoritative records and exclude draft/superseded/stale sources, then returning structured JSON matching a provided answer template. Use this skill whenever the user mentions a PeopleOps Console, employee verification, onboarding closeout, leave or payroll reconciliation, recruitment reconciliation, policy case review, source precedence, or needs to navigate a task-environment REST API with HR business logic.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_012/fewshot/opencode/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 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 Solver

Solve PeopleOps Console verification and reconciliation tasks by gathering structured data from the task environment REST API, applying the domain's record-precedence rules, and producing a JSON answer that conforms to the supplied answer template.

## How to approach a PeopleOps task

Every PeopleOps task follows the same pattern. Treat each step as a gather-then-decide phase; don't jump to conclusions before you have all the evidence.

### 1. Connect and orient

The task will give you:
- A base URL for the task environment (shown as `<TASK_ENV_BASE_URL>`)
- Login credentials (always `ops.lead@peopleops.local` / `PeopleOps#2026` in these tasks)
- A business goal describing what to verify and which employee or case to inspect
Back to top