Menu

Individual skill

finance-ops-reporting

0upvotes

SOP for Crescent Finance Ops branch reporting, CBA compensation forecasting, and theatre payroll control tasks against the remote Finance Ops API.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_009/reflect-3/reflect-3_attempt_03/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
Yes
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

# Crescent Finance Ops Reporting SOP

This skill covers three task families served by one read-only HTTP API:
1. **Finance** — branch monthly-close packages and regional management views (income statement, growth, ratios, rankings).
2. **Compensation** — ensemble (orchestra) current-year summaries and multi-year board forecasts from rate books, rosters, and scenarios.
3. **Payroll** — weekly touring-production payroll control (per-service pay, premiums, vacation, guarantees, CBA conflict flags).

Each task ships three payload files. Read all three before computing:
- `prompt.txt` — domain + what to produce.
- `payloads/request_memo.json` — the target entity id (branch/region/ensemble/production), periods/years, scenario id, and a `*_focus` list of what to report. **`memo_note` text is flavor/distractor — ignore unrelated names (e.g. "Harbor North draft workbook"); always reconcile against the live API data for the requested target id.**
- `payloads/answer_template.json` — the **authoritative contract**: `required_top_level_keys` (return exactly these keys), `field_types` (exact nested key names + shapes), and a `description` line with rounding/ordering rules. Mirror its key names and nesting verbatim.

## 1. Remote API access