Menu

Individual skill

licensing-structured-review

0upvotes

Use for structured licensing examiner tasks that require JSON decisions, restricted liquor staff packages, or alcohol renewal manual-review queues from a shared licensing data environment.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_019/self/self_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
Yes
Observed behavior
Instructions only
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 Structured Review

Use this skill when the user asks for a licensing review output from a task environment: contractor eligibility batches, restricted liquor-license control packages, or alcohol renewal manual-review queues.

## Core Workflow

1. Read the user prompt and the required output template before fetching data.
2. Read `environment_access.md` if a task environment is involved. Use only the base URL, endpoints, and SQL token listed there; do not use unrelated network sources.
3. Fetch only relevant records. Prefer target-filtered SQL when `/api/sql` is allowed; otherwise use the listed GET endpoints and filter locally.
4. Decode embedded JSON fields such as `details_json` and `controls_json`.
5. Build the answer from records and the template. Emit only allowed keys and enum values.
6. Recompute summary counts and summary ID arrays from item-level decisions. Do not hand-enter summaries independently.

If the prompt asks for JSON only, return no prose, markdown, comments, citations, or extra keys.
Back to top