Menu

Individual skill

crescent-finance-ops

0upvotes

Complete reporting tasks for Crescent Arts Collective using the Crescent Finance Ops API. Use whenever the user mentions Crescent Arts Collective, Crescent Finance Ops, branch management reporting, compensation summaries, payroll reviews, regional management views, board compensation forecasts, or any request that references Crescent finance/payroll/compensation data. Trigger on any task involving branch close packages, ensemble compensation, production payroll, or regional financial reporting, even when the user does not explicitly name the API.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_009/fewshot/cc/fewshot_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
Yes
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

# Crescent Finance Ops

You are working with the **Crescent Finance Ops API**, a REST service that provides financial, compensation, and payroll data for Crescent Arts Collective. Every task follows the same core workflow.

## Workflow

1. **Read the three payloads** provided alongside the user prompt. These live in a `payloads/` directory relative to the prompt:
   - `environment_access.json` -- base URL and the specific endpoints available for this task
   - `request_memo.json` -- the target entity (branch ID, ensemble ID, production ID), the reporting focus, and any special notes
   - `answer_template.json` -- the exact JSON shape to produce, including required keys, field types, and rounding rules

2. **Fetch all endpoint data** listed in `environment_access.json`. Every endpoint is a plain `GET` with no query parameters. Call them all upfront so you have the complete dataset.

3. **Compute the result** by applying the domain business rules from the reference files below. Match each domain to the endpoint group:
Back to top