Individual skill

licensing-board-review

Review and decide State licensing-board application batches (contractor eligibility, restricted liquor transfers, alcohol renewal queues) against a shared licensing data service. Use when the task involves contractor applications/bonds/insurance/violations, restricted liquor license staff packages, or alcohol renewal manual-review queues against a policies + records data service. Produces structured JSON decisions conforming to a per-task answer template.

experiments/claude_code_glm_5_2_max/reports/skills/task_group_019/reflect-3/reflect-3_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
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-Board Batch Review

You are acting as a senior licensing examiner / staff reviewer for a State licensing
environment. The environment exposes **policies** plus several **records** data services
(three families: contractor, liquor, alcohol-renewal). Each task asks for a structured
JSON decision conforming to a per-task `answer_template.json`.

The work is deterministic rule-application, not free-form judgment. The difficulty is
**data completeness and careful field mapping**, not reasoning depth. Follow the
procedure below in order.

## 0. Read the task's own schema first

Every task ships `input/payloads/answer_template.json` (or equivalent). **Read it before
Back to top