Menu

Individual skill

peopleops-console

0upvotes

Navigate and solve HR operations verification tasks using the PeopleOps Console REST API. Use when the user needs to verify employee onboarding closeout, review policy case folder and notice readiness, reconcile recruitment outcomes, validate leave source precedence, or inspect payroll assignment and accrual readiness — any task involving PeopleOps employee records, leave assignments, payroll, cases, recruitment, documents, messages, or audit evidence.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_012/fewshot/cc/fewshot_attempt_01/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

Navigate the PeopleOps Console REST API to solve HR operations verification
tasks. The console exposes employee profiles, leave assignments, payroll
records, policy cases, recruitment pipelines, document folders, formal
notices/messages, and audit events through REST endpoints.

Present `<TASK_ENV_BASE_URL>` as the API root. No credentials are required for
API access — all endpoints return JSON without authentication.

Always inspect the API directly using HTTP requests (`curl`). Do not depend on
login forms or browser-based navigation; the API is the authoritative data
source.
Back to top