Menu

Individual skill

peopleops-console

0upvotes

Inspect PeopleOps Console casework and return exact JSON for onboarding closeout, leave-source precedence, recruitment reconciliation, payroll readiness, and document or notice reviews. Use when prompts mention the PeopleOps Console, employee leave or payroll records, recruitment openings, case folders, notices, audits, or ask for normalized business labels from a provided answer template.

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

Use this skill to solve PeopleOps Console tasks that require reconciling multiple record types into one JSON answer.

## Workflow

1. Read the task prompt and the answer template first.
2. Open the PeopleOps Console at the supplied runner URL and log in with the provided credentials.
3. Inspect only the workspace areas the prompt names:
   - employee, leave, payroll, recruitment, document, message, policy, and audit views as needed
4. Treat the prompt as a source-order hint, then resolve conflicts with this rule:
   - prefer submitted or approved assignment-history records over drafts, superseded records, stale profile summaries, and case-summary-only text
   - use direct packet, ledger, policy, or audit evidence over inferred status
   - exclude adjacent audit events when the prompt asks for a narrower scope
Back to top