Individual skill
licensing-record-json-review
Use this skill for licensing-environment tasks that ask Codex to produce strict JSON decisions from contractor, liquor, alcohol renewal, policy, incident, financial coverage, correspondence, inspection, settlement, privilege, or site-evidence records. Trigger for State Contractors Licensing Board eligibility batches, restricted liquor-license staff packages, alcohol renewal manual-review queues, and similar prompts that reference TASK_ENV_BASE_URL endpoints and an answer_template.json schema.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_019/fewshot/opencode/fewshot_attempt_01/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- finance 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
# Licensing Record JSON Review
Use this skill to solve structured licensing review tasks against a task environment. The usual failure modes are incomplete endpoint reads, mixing distractor records into the target set, treating schema enums loosely, and writing prose outside the required JSON.
## Core Workflow
1. Read the user prompt and `input/payloads/answer_template.json` before fetching data.
2. Extract the target identifiers, review date or release boundary, required output keys, enum values, list ordering rules, and any target queue size.
3. Resolve `<TASK_ENV_BASE_URL>` from the prompt or environment instructions.
4. Fetch `GET /api/policies` and every domain endpoint named in the prompt.
5. Filter every dataset to the prompt targets. Prefer endpoint query parameters such as `?application_id=...`, `?location_id=...`, `?license_no=...`, and `?license_class=...` when available; unfiltered endpoints may be paged and may include many distractors.
6. Use SQL only when the environment gives a valid token or clear access instructions. Keep SQL target-restricted.
7. Build an intermediate worksheet per target: source records, applied policy thresholds, derived codes, and exclusions. Use it for reasoning, not final output.
8. Emit only JSON matching the template. Do not include citations, comments, markdown, or extra keys.