Menu

Individual skill

licensing-review

0upvotes

Structured licensing review for contractor application batches, restricted liquor-license staff packages, and alcohol renewal manual-review queues using a task environment API, policy JSON, record endpoints or SQL, and JSON answer templates. Use when Codex must evaluate licensing eligibility, deficiencies, postures, verification gaps, renewal review ranking, or produce schema-conformant JSON from licensing environment records.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_019/fewshot/fewshot_attempt_02/SKILL.md

Read pinned source

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
Network or broad shell
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.

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

# Licensing Review

Use this skill to turn licensing environment records into a strict JSON answer. Work from the prompt, the provided answer template, and live records; do not reuse example answer values.

## Core Workflow

1. Read the prompt and `input/payloads/answer_template.json` first. Extract target IDs, target locations, boundary dates, review dates, queue size, required keys, allowed enum values, and ordering rules.
2. Read the environment access file supplied with the task. Use only its base URL and SQL token; do not guess credentials.
3. Fetch relevant records and policies. Prefer targeted SQL slices when SQL is available because GET dumps may omit records needed for a target slice; use GET endpoints as fallback or cross-check.
4. Parse JSON-in-string fields such as policy `details_json` and settlement `controls_json`.
5. Build the answer only from schema-supported fields and enum values. When a deficiency exists but the template lacks that exact code, omit it instead of inventing a key or code.
6. Sort arrays exactly as the template requires, use empty arrays where applicable, and return only JSON.

The bundled helper groups environment records without making determinations:
Back to top