Menu

Individual skill

licensing-review

0upvotes

Structured licensing review for state contractor applications, restricted liquor-license staff packages, and alcohol renewal manual-review queues. Use when a task asks Codex to inspect a licensing environment/API, apply policy/rule records, and return schema-conforming JSON decisions, risk codes, review queues, summaries, or staff package fields.

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

Use this skill to produce exact JSON for licensing review tasks backed by a running data service.

## Core Workflow

1. Read the prompt and the provided answer template before fetching data. Treat the template as the contract for field names, allowed values, ordering, lengths, and empty-list behavior.
2. Read environment access instructions only from the provided environment file or prompt. Do not invent base URLs, tokens, or endpoints.
3. Fetch all records needed for the target IDs or target location. Prefer public endpoints for small data; use SQL when public endpoints are truncated, paginated, or cannot express the necessary join.
4. Build a working table outside the final answer that shows each target, matched source records, triggered policy facts, selected codes, and summary membership.
5. Emit only the JSON object requested by the template. Do not include citations, markdown, comments, or extra keys.

If SQL is available, use the endpoint token exactly as supplied. Metadata introspection may be blocked, so query known tables by domain:
Back to top