Menu

Individual skill

investigation-review-hub-remediation

0upvotes

Solve Investigation Review Hub legal production, preservation, privilege, QC, retention, and remediation dashboard tasks. Use when a prompt asks Codex to query a running review hub at TASK_ENV_BASE_URL and return a strict JSON object conforming to an answer_template.json schema.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_017/fewshot/naive/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 Hub Remediation

Produce a schema-conformant JSON answer from the running Investigation Review Hub. Treat the hub and task-local payloads as the only business evidence.

## Source Rules

1. Read the prompt, every task-local payload, and the answer template before querying.
2. Identify the matter ID, base URL, allowed endpoints, and any required API key/header from the prompt or payloads.
3. Use only the running hub endpoints and task-local payloads. Do not inspect local environment source, database files, seed files, generated manifests, hidden notes, evaluator code, prior answers, or non-task paths.
4. Prefer hub stable IDs for matters, request categories, sources, documents, privilege records, QC findings, retention events, productions, and remediation actions. Do not invent evidence IDs.
5. Return exactly one JSON object. Do not include prose outside the JSON.

Optional helper: `scripts/hub_snapshot.py` can collect the common read-only endpoints into one JSON snapshot:
Back to top