Individual skill

investigation-review-hub-json

Produce schema-conformant structured JSON legal review outputs from an Investigation Review Hub. Use for subpoena, grand jury, SEC, DOJ, production-readiness, retention, preservation, privilege-log, QC, custodian-source, and remediation dashboard tasks that require hub-only evidence, stable record IDs, category rollups, metrics, and prioritized action plans.

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

# Investigation Review Hub JSON

## Objective

Produce a single JSON object that conforms exactly to the task's local answer template by using the
running Investigation Review Hub as the source of record.

## Workflow

1. Read the prompt and every task-local payload. Extract the matter ID, base URL placeholder or
   provided base URL, optional SQL/API key header, required top-level keys, enum choices, field
   definitions, numeric precision, and ordering rules.
2. Do not inspect local environment source files, database files, generated manifests, hidden notes,
   evaluator code, prior answers, or standard answer files. Use only task-local payloads and hub
Back to top