Individual skill

licensing-review

Solve structured government licensing review tasks against a shared licensing API. Use for contractor eligibility batches, restricted liquor-license staff packages, alcohol renewal/manual-review queues, or similar prompts that require fetching licensing records, applying policies/rules, and returning schema-exact JSON matching answer_template.json with sorted arrays and consistent summaries.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_019/fewshot/opencode/fewshot_attempt_02/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 the final JSON for licensing-review tasks. The common failure modes are incomplete API fetches, mixing standard obligations with location-specific controls, including post-boundary records, and returning JSON that does not exactly match the template.

## Workflow

1. Read the user prompt and `input/payloads/answer_template.json` before fetching data.
2. Extract the target IDs, location IDs, review date or release boundary, target queue size, required endpoints, required keys, allowed enum values, and ordering rules.
3. Read [references/decision_patterns.md](references/decision_patterns.md) for the relevant task family:
   - Contractor application eligibility batch.
   - Restricted liquor-license staff package.
   - Alcohol renewal manual-review queue.
4. Fetch records from the task environment.
   - Use the base URL supplied by the prompt or environment instructions.
Back to top