Menu

Individual skill

licensing-review-decisions

0upvotes

Structured licensing decision support for task-environment regulatory records. Use this skill whenever the user asks Codex to review contractor licensing applications, restricted liquor-license applications or transfers, alcohol renewal hold queues, licensing policies, violations, bonds, insurance, inspections, settlements, site evidence, or any task that must return an exact JSON answer from licensing-environment API records.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_019/fewshot/opencode/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
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 Decisions

Use this skill to produce exact JSON answers for licensing review tasks backed by the shared task environment. The recurring work is not writing a memo; it is joining policy and record endpoints, applying the schema's allowed codes, and returning only valid JSON.

## First Pass

1. Read the prompt and `input/payloads/answer_template.json`.
2. Extract the domain, target identifiers, review date or boundary date, queue size, endpoint list, required keys, allowed enum codes, ordering rules, and whether SQL is listed as available.
3. Read the environment instructions for the base URL. Replace `<TASK_ENV_BASE_URL>` with that base URL.
4. Fetch the listed public endpoints. If SQL is listed and credentials are available in the environment instructions, use SQL for complete joins and to find rows not exposed through simple GET endpoints. If SQL returns an auth error, continue with the public endpoints and do not invent missing records.
5. Parse embedded JSON fields such as `details_json` and `controls_json`.
6. Keep a scratch table per target entity showing the record facts, derived codes, and why each code applies. Use the scratch table for reasoning only; final output must be JSON only.

Always trust the answer template over generic rules for field names, code names, sort order, and whether optional-looking fields are allowed.
Back to top