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
- Read
input/payloads/answer_template.json— it defines the exact output shape and the allowed enum values for every code list. - Read
input/prompt.txt— it names the target applications, the review date or boundary date, and which endpoints are available. - Identify the domain from the endpoints and application-id patterns:
- Contractor — endpoints under
/api/contractor/, application ids likeC-TR*-*. See references/contractor.md. - Liquor — endpoints under
/api/liquor/, application ids likeL-TR*-*. See references/liquor.md. - Alcohol renewal — endpoints under
/api/alcohol/and/api/renewal/, license ids likeAL-TR*-*. See references/alcohol_renewal.md.
- Contractor — endpoints under
- Follow the domain-specific reference to pull records, cross-reference them, assign codes from the template's allowed values, and build the output.
Environment Setup
Every task provides <TASK_ENV_BASE_URL> in the prompt. Set the base URL before calling any endpoint:
- Base URL: use the value from the prompt verbatim (typically
http://task-env:9019). - All GET endpoints are public (no auth).
- POST
/api/sqlrequires headerX-Task-Token; use the value fromenvironment_access.md(search forX-Task-Token).
Always pull /api/policies first when it is listed. Policies may change the compliance baseline and affect deficiency detection.
Output Rules (all domains)
- Return only the JSON object — no markdown fences, no prose, no citations.
- Order application-level items by
application_idorlicense_noascending, or byrankascending for queues, exactly as the template instructs. - Sort every code list and id list in the order the template specifies (typically ascending lexical/numeric).
- Use empty arrays (
[]) when no codes or ids apply — nevernullor omitted keys. - When the template provides allowed enum values, use only those values. Do not invent codes.
- For dates, use
YYYY-MM-DD.
General Pattern: Read All Records Before Deciding
For any domain, follow this sequence:
- GET all relevant collections (applications, bonds, insurance, violations, etc.) in parallel.
- Optionally issue POST
/api/sqlqueries for focused lookups when the GET collections are large or when the answer template asks for data not easily extracted from GET results. - Cross-reference records by application/license id.
- Walk the template's allowed code list and check each condition that could trigger that code.
- Assign determination/posture, codes, risk tier, and summary fields.