Individual skill

peopleops-console

Solve PeopleOps Console business verification tasks by fetching API evidence, applying source-precedence and draft-exclusion rules, scoping audit events to the correct domain, and producing normalized JSON answers with enumerated business labels.

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

This skill covers PeopleOps business verification workflows: onboarding closeout, case folder and notice review, recruitment reconciliation, leave source precedence, and payroll assignment readiness. Every task supplies an answer template and expects a single JSON object using the template's enumerated labels.

## Connection and Credentials

The prompt provides `<TASK_ENV_BASE_URL>`. Use these fixed credentials:

- Email: `ops.lead@peopleops.local`
[Credential-related source omitted]

All API responses are JSON. The solver reads data through GET endpoints; the only available POST endpoint is `/api/cases/{case_id}/comments`. The `/api/judge` endpoint is disabled and must not be called.

## Available Endpoints
Back to top