Individual skill
task-group-011-fewshot-attempt-02
Produce strict JSON answers for credit-office committee tasks using only public API data and the provided answer_template.json. Use for branch loan regrades, watch-list stress packets, pending-application allocations, competing CRE decisions, and credit-union segment posture recommendations that require policies, branch or segment metrics, FDIC/NCUA benchmarks, controlled enums, sorted lists, and reconciled numeric totals.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_011/demonstration_skill/demonstration_skill_attempt_02/credit-committee-json/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 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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- data 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 Committee JSON
## Access Rules
- Use the public HTTP API base URL supplied by the task or environment. If a setup script is mentioned but an API base URL is already provided, use the provided URL directly.
- Do not read local environment source/data files, test tasks, reports, generated skills, notes, or task metadata. For benchmark tasks, read only the prompt and its `input/payloads/answer_template.json` unless the user explicitly grants more.
- Prefer public API endpoints over local files for branch details, branch metrics, sector exposure, loans, pending applications, policies, benchmarks, manifests, and credit-union segment data.
- Return only the JSON object requested by the template. Do not add markdown, comments, or explanatory text outside the JSON.
## Core Workflow
1. Read the prompt and `answer_template.json` first.
2. Extract the target identifier, as-of/review date, population rule, named applications, required benchmark version, and every enum/order/precision rule from the template.
3. Discover and fetch public API data for the requested surfaces: