Menu

Individual skill

licensing-record-review

0upvotes

Structured licensing decision support for Codex tasks that use a shared task-environment API and require JSON-only answers for contractor eligibility batches, restricted liquor-license staff packages, or alcohol renewal manual-review queues. Use when prompts mention contractor applications, bonds, insurance, license history, violations, correspondence, inspections, restricted liquor settlements, site evidence, alcohol renewal rules, release boundaries, or manual-review queue ranking.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_019/fewshot/deepagents/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 Record Review

Use this skill to turn licensing-environment records into the exact JSON requested by the prompt's `answer_template.json`.

## Core Workflow

1. Read the prompt and the answer template before querying records.
2. Extract only the target identifiers named in the prompt: application IDs, location IDs, license numbers, review date, release boundary, and queue size.
3. Query the task environment using the staged base URL. Prefer per-ID filters. Do not learn from unrelated rows returned by broad endpoints.
4. Parse `details_json` and other JSON-in-string fields before applying rules.
5. Build the answer from the template's allowed keys and enum values. If a concept maps to different code names across templates, use the code names present in that template.
6. Sort arrays exactly as the template says. If the template accepts any order, still use a stable order unless it requests operational sequence.
7. Return only the final JSON object.
Back to top