Menu

Individual skill

licensing-review-solver

0upvotes

Structured licensing data-service review for contractor eligibility batches, restricted liquor-license staff packages, and alcohol renewal manual-review queues. Use when a prompt provides licensing environment endpoints plus a JSON answer template and asks Codex to return exact JSON decisions, risk codes, monitoring plans, queue ranks, or summaries for contractor applications, liquor premises controls, or alcohol renewal releases.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_019/fewshot/naive/fewshot_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.

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 Solver

## Overview

Solve licensing review tasks by building a record-backed decision table from the task environment, applying the current policy records, mapping findings to the answer template's allowed code vocabulary, and returning only schema-conformant JSON.

## Core Workflow

1. Read the prompt and `input/payloads/answer_template.json` before querying data.
2. Extract the target identifiers, review date or release boundary, queue size, required endpoints, ordering rules, allowed enum values, and required summary keys.
3. Read the environment access instructions when present. Use the prompt base URL or the access file's base URL. If SQL is allowed, send the documented token header and only `SELECT` queries.
4. Query `/api/policies` for all task families. Query `/api/renewal/rules` for renewal queues.
5. Prefer filtered SQL queries over unfiltered endpoint dumps. Filter to the prompt's target application IDs, location IDs, license numbers, and any predecessor or successor license numbers discovered from target rows.
6. Normalize records into one case file per target. Keep the raw IDs needed for summary arrays.
Back to top