Menu

Individual skill

investigation-review-json

Build schema-conforming JSON answers for Investigation Review Hub legal review tasks. Use when a prompt asks Codex to analyze subpoena, grand jury, SEC, DOJ, production-readiness, retention, preservation, privilege-log, QC, custodian-source, remediation, or cross-system dashboard evidence from a running Investigation Review Hub and return a single structured JSON object.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_017/fewshot/codex/fewshot_attempt_01/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

# Investigation Review JSON

## Core Workflow

1. Read the user prompt, `input/payloads/answer_template.json`, and any task-local context payloads before querying the hub.
2. Treat the running Investigation Review Hub and task-local payloads as the only business evidence. Do not inspect environment source files, database files, generated manifests, answer files, or evaluator files.
3. Identify the matter ID, hub base URL, required top-level keys, enum choices, field types, and ordering rules from the prompt and template.
4. Fetch matter-scoped hub evidence from schema, matters, categories, productions, custodian sources, documents, privilege log, QC findings, retention events, and remediation actions. Prefer the bundled snapshot helper:

```bash
python3 skill/scripts/hub_snapshot.py --base-url "$TASK_ENV_BASE_URL" --matter-id "$MATTER_ID" --api-key review-key-017 > /tmp/hub_snapshot.json
```

If the task gives a different API key or says no key is needed, pass the task value or omit `--api-key`.