Menu

Individual skill

investigation-review-hub-json

Build structured JSON preservation, production-readiness, privilege, retention, QC, and remediation analyses from an Investigation Review Hub. Use when a task asks Codex to return a schema-conforming JSON object for a legal investigation matter using hub endpoints, task-local payloads, subpoena categories, productions, custodian sources, documents, privilege logs, QC findings, retention events, or remediation actions.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_017/fewshot/fewshot_attempt_02/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
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 Hub JSON

## Source Discipline

Use only the task prompt, task-local input payloads, and the running Review Hub endpoints named by the task. Do not inspect environment source files, database files, generated manifests, hidden notes, answer keys, or evaluation files. If a task provides `environment_access.md`, use it only to obtain the live base URL, API key, and allowed endpoint list.

Read every task-local payload before querying. Treat `answer_template.json` as the output contract: required keys, field names, enums, ordering rules, numeric precision, and JSON-only output requirements override all defaults here.

## Hub Access

Fetch the schema first, then retrieve matter-scoped evidence from every relevant endpoint:

```bash
BASE="<hub base url>"