Individual skill

licensing-env-review

Solve structured licensing review tasks against a provided task environment. Use this skill when Codex is asked to return schema-constrained JSON for contractor application eligibility batches, restricted liquor-license staff packages, alcohol or liquor renewal manual-review queues, or similar licensing endpoint reviews involving /api/policies, contractor, liquor, alcohol, renewal, or optional SQL endpoints plus input/payloads/answer_template.json.

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

Use this skill for endpoint-backed licensing tasks where the answer must be a single JSON object matching a staged template.

## Core Workflow

1. Read the prompt and `input/payloads/answer_template.json` before fetching data.
2. Extract the target IDs, location IDs, license numbers, review dates, release boundary, requested queue size, and all endpoint paths named in the prompt.
3. Read the task's environment access instructions only to obtain the base URL and allowed endpoints. Replace `<TASK_ENV_BASE_URL>` with that base URL.
4. Fetch only the endpoint families needed for the prompt. Prefer targeted GET filters when an endpoint supports them. If a filter returns an error or an endpoint is naturally global, fetch the endpoint and filter locally by target application ID, license number, prior license ID, location ID, or successor license.
5. Treat `POST /api/sql` as optional. Use it only when the environment credentials make it work; otherwise fall back to GET data.
6. Build a casebook keyed by the target identifiers. Parse any `details_json` or `controls_json` fields before applying business rules.
7. Apply the domain-specific rules in [references/decision-rules.md](references/decision-rules.md).
8. Emit only the JSON object requested by the template. Do not include prose, citations, markdown fences, comments, or keys absent from the template.