Menu

Individual skill

licensing-review-json

0upvotes

Produce schema-conforming JSON for licensing-environment review tasks. Use when a prompt asks Codex to analyze task-environment records for contractor application eligibility batches, restricted liquor-license staff packages, or alcohol renewal manual-review queues, especially when outputs must match an answer_template.json exactly.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_019/fewshot/codex/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 JSON

## Core Workflow

1. Read the prompt and `input/payloads/answer_template.json` first. Extract the task family, target identifiers, review date or release boundary, endpoint list, required top-level keys, allowed enum values, ordering rules, and summary fields.
2. Fetch only the endpoint data needed for the target identifiers. Prefer the GET endpoints listed in the prompt. Treat `POST /api/sql` as optional: use it only when the environment provides credentials and it saves work.
3. Parse JSON-encoded fields such as `details_json` and `controls_json` before applying rules.
4. Derive facts from current records, then map them into the exact code vocabulary in the answer template. When two templates use different names for the same concept, choose the allowed name from the current template.
5. Return only the JSON object. Do not include prose, markdown, citations, comments, or keys not present in the template.

Use `scripts/collect_records.py` from this skill directory when endpoint filtering would save time:

```bash
python scripts/collect_records.py --base-url "$TASK_ENV_BASE_URL" --family contractor --ids C-001 C-002
Back to top