Individual skill

licensing-review

Use for structured licensing review tasks involving contractor applications, restricted liquor-license packages, or alcohol renewal queues where Codex must gather task-provided records, apply policy/rule thresholds, and return exact JSON matching a supplied template.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_019/reflect-3/reflect-3_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.

agent Repository topic
ai Repository topic
benchmark Repository topic
llm Repository topic
self-evolving Repository topic
self-learning Repository topic
skills Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 7,866 bytes

Read excerpt


# Licensing Review

## Core Workflow

1. Read the prompt, output template, and task-provided data access instructions before querying records.
2. Treat the output template as authoritative: use exactly its keys, allowed enum values, ordering rules, empty-array conventions, date format, and summary fields.
3. Gather records with structured filters. If a public data response appears capped or incomplete, use the task-provided structured query mechanism when available and filter by the target identifiers.
4. Normalize parsed JSON fields inside records, especially policy `details_json` and settlement/control payloads.
5. Build an evidence table by target id before drafting JSON. Keep raw facts separate from derived decisions.
6. Reconcile summaries from item-level decisions after all item rows are final.
7. Return only the requested JSON. Do not include citations, rationale prose, markdown, or extra keys unless the template explicitly permits them.

## Contractor Application Reviews