Menu

Individual skill

crescent-finance-ops-reporting

0upvotes

Use this skill for Crescent Arts Collective Finance Ops API tasks that ask for branch close reporting, regional management views, compensation summaries or forecasts, or weekly payroll reviews. It helps convert request memos, answer templates, and the remote Crescent Finance Ops API into one exact JSON answer with the correct formulas, ordering, rounding, and roster/rate-book edge-case handling.

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

## Core workflow

1. Read the task prompt, `payloads/request_memo.json`, `payloads/answer_template.json`, and `payloads/environment_access.json`.
2. Treat `answer_template.json` as the contract: return exactly one JSON object with the requested keys, field names, list ordering, and numeric rounding. Do not add narrative fields just because the memo asks for background context unless the template includes them.
3. Use the `base_url` from environment access and query the listed remote API endpoints directly. Do not assume a local task server or local cached data.
4. Inspect each endpoint's actual shape before calculating. Some endpoints return arrays, while rate books and scenarios are keyed objects.
5. Use a small script or structured calculation rather than manual arithmetic. Terminal output can truncate large `/records` responses, so fetch into memory before aggregating.
6. Return JSON numbers, not formatted strings. Currency fields round to 2 decimals. Percent, ratio, margin, and growth fields round to 4 decimals as decimal rates, e.g. `0.1234`, not `12.34`.

## General conventions

- Stable IDs are meaningful. Sort ID lists ascending unless the template says a rank or top/bottom fact requires another order.
Back to top