Menu

Individual skill

reflect-3_attempt_01

0upvotes

Not available

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_011/reflect-3/reflect-3_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
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.

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
# Credit Office Committee JSON Skill

Use this skill for Credit Office tasks that ask for committee-ready JSON using public branch, loan, application, policy, benchmark, sector-exposure, or credit-union segment data.

## Core Workflow

1. Read the prompt target IDs, review/as-of date, and required JSON shape. If an `answer_template.json` is present in the task input, follow its field names, enum values, and identifiers exactly.
2. Use only the public API surfaces named by the task/environment. Pull the entity record, latest relevant metrics, policies, relevant loans/applications/exposures, and the named benchmark set.
3. Work from the latest quarter unless the prompt names a different period. Preserve requested ordering for applications and use stable IDs exactly as returned by the API.
4. Return one valid JSON object only. Do not add prose outside JSON. Prefer explicit numeric fields over narrative-only conclusions.

## Risk Rating Regrades

- Numeric ratings worsen as the number increases.
- For re-derived loan ratings, apply the policy dominant-factor rule: calculate available DSCR rating, LTV/collateral rating, and delinquency minimum, then use the worst numeric rating among the available factors.
Back to top