Menu

Individual skill

task-group-012-fewshot-attempt-03

0upvotes

Use for Northwind PeopleOps Console tasks that require reconciling HR lifecycle records, leave/payroll source precedence, recruitment outcomes, folder/notice readiness, audit evidence, and writing evaluator-ready answer.json files from a provided answer_template.json.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_012/demonstration_skill/demonstration_skill_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 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

# Northwind PeopleOps Console SOP

Use this skill when solving local PeopleOps Console tasks against the provided web/API URL. The job is evidence reconciliation, not workflow execution: inspect records, apply source-precedence rules, and return only JSON matching the task's `answer_template.json`.

## First pass

1. Read the task prompt and `input/payloads/answer_template.json` before using the app. Treat the template as the contract for keys, types, and exact enum strings.
2. Identify the target kind:
   - Employee/person task: employee ID such as `EMP-*`, often involving leave, payroll, onboarding, or profile summary conflicts.
   - Policy case task: case ID such as `CASE-*`, involving approvals, folders, notices, attachments, and audit.
   - Recruitment task: opening ID such as `REQ-*`, involving candidates, offers, cost ledgers, notice packets, and payroll handoff.
3. Open the provided URL. If a login screen appears, use `ops.lead@peopleops.local` / `PeopleOps#2026`; some local runs may already expose the console without auth.
4. Prefer direct API reads for completeness, using the UI to cross-check when helpful. Do not post comments or record actions unless the prompt explicitly asks.
5. Build a field-by-field evidence table before writing JSON: selected source, excluded source, policy rule, audit support, final control/action.
Back to top