Menu

Individual skill

licensing-review

0upvotes

Structured licensing review for state regulatory boards. Covers contractor eligibility batches, restricted liquor license staff packages, and alcohol renewal manual-review queues. Use when the task involves reviewing licensing applications with determination codes, deficiency flags, risk tiers, or renewal ranking against a boundary date, especially when a JSON answer template is provided with enum vocabularies and the environment exposes GET endpoints under /api/ plus an optional POST /api/sql.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_019/fewshot/codex/fewshot_attempt_01/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
Yes
Observed behavior
Instructions only
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

## Overview

This skill covers three licensing-review domains typical of state regulatory boards. Each domain pulls records from a task-specific HTTP data service, cross-references related records per application, and produces a structured JSON decision that strictly matches the provided `answer_template.json`.

## Quick-Start Workflow

1. Read `input/payloads/answer_template.json` — it defines the **exact output shape** and the **allowed enum values** for every code list.
2. Read `input/prompt.txt` — it names the target applications, the review date or boundary date, and which endpoints are available.
3. Identify the domain from the endpoints and application-id patterns:
   - **Contractor** — endpoints under `/api/contractor/`, application ids like `C-TR*-*`. See [references/contractor.md](references/contractor.md).
   - **Liquor** — endpoints under `/api/liquor/`, application ids like `L-TR*-*`. See [references/liquor.md](references/liquor.md).
   - **Alcohol renewal** — endpoints under `/api/alcohol/` and `/api/renewal/`, license ids like `AL-TR*-*`. See [references/alcohol_renewal.md](references/alcohol_renewal.md).
Back to top