Menu

Individual skill

reflect-3_attempt_03

0upvotes

Not available

experiments/codex_gpt5_5_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
No
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.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

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.

Declared tags are partial or unavailable.

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 Skill

Use this skill for Crescent Finance Ops tasks that ask for branch close reporting, regional management reporting, compensation summaries or forecasts, and payroll review JSON outputs.

## Environment Habits

- Use the remote Finance Ops base URL from the task's `environment_access.json`. Do not assume or inspect a local environment.
- Read the task memo and answer template first. Treat the template as the source of truth for field names, nesting, ordering, rounding, and whether ratios are decimal percentages.
- Pull the complete active endpoint data needed for the request, then filter in memory by the requested branch, region, ensemble, production, scenario, period, or year. Avoid relying on memo notes when active API data disagrees.
- For finance tasks, fetch branches, period map, accounts, and records together. Use the period map to derive fiscal-year membership instead of hard-coding month labels unless the active period map confirms them.
- For compensation tasks, fetch the rate book and rosters; fetch scenarios only for forecast requests.
- For payroll tasks, fetch both the payroll rate book and productions. Use the production schedule and roster assignments together, not the schedule alone.

## General Output Rules
Back to top