Individual skill
peopleops-console-controls
Solve PeopleOps Console evidence-control tasks that require logging into a task environment, reconciling HR records, and returning JSON matching an answer_template. Use for onboarding closeout, remote-work case readiness, recruitment reconciliation, leave source precedence, payroll assignment, accrual readiness, formal notice, audit-scope, and folder control reviews.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_012/fewshot/deepagents/fewshot_attempt_03/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- security Derived category
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
## Workflow
1. Read the task prompt and `input/payloads/answer_template.json` before opening the app. Treat the template as the output contract: exact keys, exact enum labels, correct JSON types, no extra fields.
2. Open the configured task URL and log in with the credentials from the prompt. Search by the entity in scope: employee, case, requisition/opening, candidate, payroll assignment, batch, or audit event.
3. Collect source records before deciding. Prefer transactional records and documents over summaries: assignment history, ledgers, offer registers, folder contents, notice packets, policy documents, approval history, and audit event details. Use profile or case summaries only when stronger source records are absent or explicitly confirmed current.
4. Track every excluded record ID while reviewing. Exclude drafts, superseded records, stale profile summaries, prior-period assignments, wrong-scope audit events, and adjacent audit events that do not support the requested decision.
5. Fill the JSON with the normalized labels from the template, not prose. If several labels seem plausible, choose the one that states the authoritative evidence source and control outcome most specifically.
6. Validate the draft answer with `scripts/validate_answer.py` before finalizing.
## Evidence Rules
### Leave Precedence