Individual skill

licensing-json-review

Use this skill for structured licensing-environment JSON tasks involving contractor application eligibility batches, restricted liquor-license staff packages, or alcohol renewal manual-review queues. Use it when the prompt mentions TASK_ENV_BASE_URL, licensing API endpoints, answer_template.json, policy-backed deficiency or control codes, or renewal queue ranking.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_019/fewshot/cc/fewshot_attempt_03/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 JSON Review

Use this skill when a task asks for a licensing decision, staff package, or renewal queue as JSON that must match `input/payloads/answer_template.json`.

## Core Workflow

1. Read the prompt and `input/payloads/answer_template.json` before querying data.
   Extract the target IDs, target location, review date or release boundary, queue size, required top-level keys, allowed enum codes, and all ordering rules.
2. Resolve the task environment base URL from the prompt or environment instructions. Fetch `/api/policies` first and parse each `details_json`.
3. Fetch only records needed for the target IDs when the endpoint supports filters. Repeated query parameters may return only the first value, so loop over targets unless SQL is available and authorized.
4. Treat `POST /api/sql` as optional. If it rejects the request or no token is available, use the REST endpoints and filter locally when an endpoint lacks the needed filter.
5. Build a small evidence table before writing JSON: one row per target, with the policy applied, source records used, output codes selected, and any excluded records with reasons.
6. Apply the domain rules in [references/licensing_rules.md](references/licensing_rules.md). Use the local answer template as the authority whenever schema names, code casing, or ordering differ.
7. Return only the JSON object. Do not include prose, markdown, citations, comments, or extra keys.