Individual skill

licensing-review-solver

Solve structured licensing review tasks that use a read-only task environment and require strict JSON answers, including contractor eligibility batches, restricted liquor-license staff packages, and alcohol renewal manual-review queues. Use when the prompt references licensing endpoints, policies, contractor applications/bonds/insurance/history/violations, liquor applications/settlements/privileges/incidents/site evidence, alcohol renewal licensees/violations/rules, or an answer_template.json schema.

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

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

## Core Workflow

1. Read the prompt, `input/payloads/answer_template.json`, and the task's `environment_access.md`.
2. Use only endpoints and SQL access allowed by `environment_access.md`. Never call `/api/judge`.
3. Fetch policies first, then fetch every business endpoint named in the prompt. Prefer SQL for targeted joins or filtering when a token is provided.
4. Parse JSON-in-string fields such as policy `details_json` and settlement `controls_json`.
5. Build the answer from source records and the template. Use exactly the required keys, allowed enum values, casing, ordering rules, and empty arrays where nothing applies.
6. Before finalizing, validate that summary counts and ID lists are consistent with item-level records. Return only the JSON object.

Useful helpers:

```bash