Individual skill
finance-ops-reporting
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/self/self_attempt_02/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
- 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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- finance 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
SKILL.mdcore · 16,620 bytes
Read excerpt
# Crescent Finance Ops Reporting SOP
This group has THREE task families against one read-only HTTP API. Each task gives you
`prompt.txt`, `payloads/request_memo.json`, and `payloads/answer_template.json`. Your job
is to return ONE JSON object that exactly matches the template's keys/shapes.
## 0. Universal procedure (do this every task)
1. **Read `answer_template.json` first.** Its `required_top_level_keys` and `field_types`
ARE the contract. Emit exactly those keys, nested exactly as shown, no extras, no omissions.
2. **Read `request_memo.json`** for the target IDs (`target_branch_id`, `target_region_id`,
`ensemble_id`, `scenario_id`, `production_id`), periods, and focus lists.
3. **IGNORE the `base_url` inside `payloads/environment_access.json`** (it points at a wrong
localhost). Always use the remote base URL: `<remote-env-url>`.