Menu

Individual skill

investigation-review-hub-remediation

0upvotes

Use when producing legal investigation, subpoena, SEC, grand jury, retention, production-readiness, gap-analysis, or remediation-dashboard JSON deliverables from an Investigation Review Hub API and a task-provided answer_template schema.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_017/self/self_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 Remediation

Use this skill for structured legal operations reviews where the Investigation Review Hub is the source of record and the final answer must conform to a task-local JSON schema.

## Core Workflow

1. Read the task prompt, every task-local payload, and the answer template before querying evidence.
2. Identify the matter ID, allowed sources, output schema, required top-level keys, enum choices, ordering rules, numeric precision, and any client-facing category labels.
3. Use only the task-authorized Investigation Review Hub endpoints for business evidence. Do not inspect environment source files, database files, generated manifests, hidden notes, standard answers, or local setup artifacts unless the prompt explicitly allows them.
4. If network details are provided separately, read that file and use only the listed base URL, headers, and endpoints. If SQL-style access is allowed, use the task-provided API header and inspect the hub schema before writing queries.
5. Filter every endpoint call or query by the requested matter ID. Use stable hub IDs exactly as returned for matters, categories, sources, documents, privilege-log records, QC findings, retention events, productions, and remediation actions.
6. Build the answer from evidence, then validate it against the answer template. Return exactly one JSON object when the prompt requires JSON only.

## Evidence Map
Back to top