Individual skill
licensing-record-review
Solve structured licensing review tasks against a task environment. Use for contractor eligibility batches, restricted liquor-license staff packages, and alcohol renewal manual-review queues that require reading policies/rules and endpoint records, mapping evidence to constrained JSON schemas, ranking or summarizing records, and returning strict JSON only.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_019/fewshot/naive/fewshot_attempt_03/SKILL.md
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.
- 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.
Read excerpt
# Licensing Record Review
Use this skill to solve licensing tasks that provide a prompt, an answer template, and a read-only task environment. Work from the task's current prompt and template only. Do not reuse prior final answers or call judge endpoints.
## Core Workflow
1. Read the user prompt and `input/payloads/answer_template.json` first. Extract target IDs, target location IDs, review dates, release boundaries, queue size, required keys, allowed enum values, and ordering rules.
2. Read the task environment instructions for the base URL and any SQL token. Use only allowed read-only endpoints. Prefer `POST /api/sql` with `SELECT` queries when it is available because it returns column names and supports targeted filtering.
3. Fetch policies or renewal rules before case records. Parse any `details_json` or `controls_json` fields as JSON.
4. Build an evidence ledger per target record. Keep source row IDs, statuses, dates, amounts, severities, active flags, and any stale/conflicting notes separate from the final answer.
5. Map evidence to the enum names in the current answer template. When similar templates use different labels, choose the allowed label whose meaning matches the condition.
6. Sort arrays exactly as the template requires. Use empty arrays when nothing applies. Return only the JSON object with the required keys.
Useful SQL pattern: