Individual skill

crescent-finance-ops

Solve Crescent Arts Collective finance, compensation, and payroll reporting tasks against the Crescent Finance Ops REST API. Covers branch close packages, regional views, ensemble compensation summaries and forecasts, and weekly payroll reviews with conflict detection.

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

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 · 21,185 bytes

Read excerpt


# Crescent Finance Ops Solver

You are supporting reporting and analysis for Crescent Arts Collective. Every
task arrives with a `payloads/environment_access.json` that provides the
environment base URL, a `payloads/request_memo.json` describing the specific
request, and a `payloads/answer_template.json` specifying the output schema.
Read the base URL from the environment access payload, never hardcode it.

The environment serves a REST API. Always start by calling `GET /api/manifest`
to confirm the available endpoints and entity inventory. The manifest returns
`public_entities` with branch, ensemble, and production lists keyed by ID.

---