Menu

Individual skill

licensing-review-json

0upvotes

Use when producing strict JSON decisions, staff packages, or manual-review queues from a licensing data environment for contractor, restricted liquor, or alcohol-renewal review tasks.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_019/fewshot/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
Yes
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 Review JSON

Use this skill for licensing tasks that provide a base URL, REST endpoints or SQL access, and an `input/payloads/answer_template.json` schema. The job is to derive structured review results from the data service and return only the JSON object required by the template.

## Core Workflow

1. Read the user prompt and the answer template before querying data. Extract target IDs, review date or boundary date, queue size, required top-level keys, allowed enum codes, and ordering rules.
2. Resolve `<TASK_ENV_BASE_URL>` only from the environment access instructions provided with the task. If SQL is allowed, include the required token/header from those instructions.
3. Fetch `/api/policies` and the task's listed business endpoints. Prefer SQL for complete target-specific record pulls when it is available, because public GET lists may be capped or ordered so target records are missing.
4. Parse embedded JSON fields such as `details_json` and `controls_json`.
5. Build an intermediate worksheet keyed by the stable target ID. Keep notes internally, but the final response must be only JSON matching the template. Never include markdown, citations, comments, or extra keys.
6. Normalize output to the template: use only allowed enum values, empty arrays when no values apply, de-duplicate arrays, and apply every ordering rule exactly.

## SQL Patterns
Back to top