Individual skill
skill
Solve public credit-office committee tasks that require querying <TASK_ENV_BASE_URL>, the branch or segment API, FDIC or NCUA benchmarks, and the provided answer_template.json to produce an exact JSON answer. Use this whenever the prompt mentions branch_id, segment_id, loan regrades, pending applications, DSCR stress, concentration limits, CRE comparisons, watch lists, or a committee-ready JSON output.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_011/fewshot/opencode/fewshot_attempt_02/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- 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
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Credit Office JSON Workflow
Use this skill for the staged credit-office prompts. The target output is always a single JSON object that matches the supplied `input/payloads/answer_template.json` exactly. Do not write prose outside the JSON.
## Start here
1. Read the prompt and the matching `input/payloads/answer_template.json`.
2. Read `/api/manifest` and `/api/policies` from the public task environment.
3. Use the prompt type and the template keys to decide which branch, segment, loans, applications, and benchmark tables you need.
4. Fetch only the API data needed for that template. The public API is the source of truth; do not guess from memory.
## API order
Prefer this sequence when you need a full picture: