Menu

Individual skill

licensing-review-json

0upvotes

Use for licensing review tasks that query a provided task environment, apply contractor, restricted liquor, or alcohol renewal policies, and return a schema-only JSON decision package.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_019/self/self_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 JSON

Use this skill when a task asks for a structured licensing decision, staff package, or manual-review queue using a task environment. The common job is to gather policy and record evidence, map it into allowed output codes, and return only JSON conforming to the provided answer template.

## Operating Rules

1. Read the prompt, `environment_access.md`, and the referenced `input/payloads/answer_template.json`.
2. Use only endpoints authorized in `environment_access.md`. Use the provided base URL and the SQL token/header exactly as given.
3. Fetch `/api/policies` first, then fetch only the record families named in the prompt.
4. Prefer targeted SQL when GET endpoints are capped or broad. Endpoint-backed table names generally mirror the endpoint family, for example `contractor_applications`, `contractor_bonds`, `liquor_settlements`, `alcohol_violations`, and `renewal_rules`.
5. Do not use the system date for business cutoffs unless the prompt says to. Use the prompt's review date, release boundary, or policy boundary. If no date is supplied, rely on record statuses and the task's batch context.
6. Treat the answer template as the source of truth for field names, allowed codes, ordering, counts, and whether optional fields are allowed.
7. Return only the JSON object. No prose, markdown, comments, citations, or extra keys.
Back to top