Menu

Individual skill

licensing-data-review

0upvotes

Use this skill for state licensing or regulatory review tasks that require querying a task environment and returning strict JSON decisions, staff packages, or manual-review queues. It is especially relevant for contractor application eligibility batches, restricted liquor-license transfer or renewal packages, and alcohol renewal release queues involving policies, applications, bonds, insurance, license history, violations, correspondence, settlements, privileges, incidents, site evidence, or renewal rules.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_019/fewshot/cc/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
No
Observed behavior
Network or broad shell
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 Data Review

Use this skill when the user asks for a structured licensing decision or review package from a task environment. The important pattern is not memo writing; it is careful source-data reconciliation followed by schema-faithful JSON.

## Core Workflow

1. Read the prompt and the answer template before fetching data.
   - Extract the target IDs, target location, release boundary, review date, queue size, and listed endpoints.
   - Treat the template as the output contract. Use exactly its keys, enum values, ordering rules, and empty-array conventions.
2. Fetch policy records first, then the domain records.
   - Prefer SQL only if the environment explicitly provides working SQL access. Otherwise use the HTTP endpoints.
   - Large endpoints may be paginated or capped. Add a generous `?limit=1000` or query per target ID when possible.
   - Parse nested JSON fields such as `details_json` and `controls_json`.
3. Build a compact evidence table before deciding.
Back to top