Individual skill
licensing-review
Structured licensing review for contractor eligibility batches, restricted liquor-license staff packages, and alcohol renewal manual-review queues. Use when Codex must inspect licensing records, policies, violations, evidence, financial coverage, settlements, or renewal boundaries and return a strict JSON decision package matching a provided schema.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_019/reflect-3/reflect-3_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 Review
## Core Workflow
1. Read the prompt and answer template before querying records.
2. Extract the target IDs, location IDs, review date or release boundary, required output keys, allowed enum codes, count requirements, and ordering rules.
3. Read current policy records and parse embedded JSON policy details. Map policies by family and by the task-specific class, trade, license class, or renewal boundary.
4. Pull only records relevant to the target IDs, predecessor IDs, and target locations. If a public record source appears incomplete or paginated and a query service is available in the environment, use concrete filtered queries to verify completeness.
5. Build the answer from the schema outward. Prefer empty arrays over omitted keys, sort arrays exactly as instructed, and keep summary counts and ID lists consistent with item-level decisions.
6. Do not add prose, citations, markdown, or extra fields to the final answer unless the template explicitly allows them.
## Contractor Eligibility
For each application, join application, bond, insurance, prior license, violation, correspondence, inspection, and policy records.