Menu

Individual skill

task-group-009-fewshot-attempt-03

0upvotes

Transferable SOP for Crescent Arts Collective Finance Ops API tasks in task_group_009 requiring branch close reporting, regional finance reporting, current-year ensemble compensation summaries, compensation forecasts, or touring theatre payroll/CBA review. Use when Codex must read input payloads, query the localhost Finance Ops API, calculate rounded JSON outputs, rank branches or regions, apply roster/scenario compensation rules, or compute payroll premiums, guarantees, vacation, substitute adjustments, and conflict flags.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_009/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

# Task Group 009 Finance Ops SOP

Use this skill to solve new Finance Ops reporting tasks from their active input payloads. Do not use train answers as a lookup table. Always derive results from the request memo, answer template, and the public endpoints listed in the task input.

## Access Protocol

1. Read only the task input artifacts: `prompt.txt`, `payloads/request_memo.json`, `payloads/environment_access.json`, and `payloads/answer_template.json`.
2. Get `base_url` and `available_endpoints` from `environment_access.json`.
3. Query only listed public endpoints under that base URL. Typical endpoints are:
   - Finance: `/api/finance/branches`, `/api/finance/period-map`, `/api/finance/accounts`, `/api/finance/records`
   - Compensation: `/api/compensation/rate-book`, `/api/compensation/rosters`, `/api/compensation/scenarios`
   - Payroll: `/api/payroll/rate-book`, `/api/payroll/productions`
4. Use `request_memo.json` to identify the target branch, region, ensemble, production, scenario, periods, and requested view.
5. Use `answer_template.json` as the output contract. Return one JSON object only, with exactly the requested keys and numeric JSON values.
Back to top