Menu

Individual skill

credit-office-committee-json

0upvotes

Solve shared credit-office committee packet prompts by querying the task-env API, applying the public policy tables and benchmark data, and returning strict JSON that matches the provided answer template. Use this skill whenever a prompt asks for branch regrades, lending allocations, segment posture, watch-list stress, or competing CRE decisions from the shared credit office API, even if it does not explicitly say to use a skill or API.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_011/fewshot/opencode/fewshot_attempt_01/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.

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

# Credit Office Committee JSON

Use this skill for the staged shared credit-office tasks. The job is always the same at a high level: read the prompt, read the template, pull the right public API records, apply the policy tables, and return JSON only.

## Source Order

1. Treat `input/payloads/answer_template.json` as the exact schema.
2. Use the prompt for the branch, segment, application IDs, review date, and any special threshold language.
3. Query the task environment with the supplied `<TASK_ENV_BASE_URL>`.
4. Read `/api/manifest` and `/api/policies` before you compute anything nontrivial.
5. Use the branch, segment, loan, application, and benchmark endpoints named by the prompt.

Do not infer final values from the example answers. Use them only as shape and workflow guidance.
Back to top