Menu

Individual skill

licensing-record-review

0upvotes

Analyze licensing-environment records for schema-strict licensing decisions. Use when a task asks Codex to review contractor application batches, restricted liquor-license transfers or renewals, or alcohol renewal manual-review queues using policy and case-record endpoints, then return JSON decisions, risk codes, verification gaps, monitoring plans, ranked queues, and summaries.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_019/self/self_attempt_02/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.

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 Record Review

## Core Workflow

1. Read the prompt, environment-access instructions, and the full answer template before fetching records.
2. Extract target IDs, location IDs, review dates, boundary dates, queue size, required top-level keys, enum values, ordering rules, and summary requirements.
3. Use only the endpoints and SQL access authorized by the environment instructions. Do not browse the web for licensing facts.
4. Fetch all relevant policy and record endpoints for the target family. Parse nested JSON fields such as `details_json` and `controls_json` with a JSON parser.
5. Build target-indexed record maps, then evaluate each target against the current policy baseline and the answer template's allowed codes.
6. Treat missing expected records as evidence when the schema asks about coverage, verification, or review gaps.
7. Return only valid JSON conforming to the template. Use empty arrays for no applicable codes and never add prose, citations, comments, or extra keys.

## Data Handling
Back to top