Individual skill
investigation-review-hub
Build structured legal investigation, subpoena, production-readiness, retention, privilege, QC, and remediation dashboards from an Investigation Review Hub task. Use when a prompt asks Codex to analyze matter-level evidence from a running review hub API and return a JSON object conforming to a task-local answer template.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_017/fewshot/fewshot_attempt_01/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- legal Derived category
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
## Source Rules
Use only the task prompt, files under the task input directory, and the running Investigation Review Hub endpoints documented by the task. If `environment_access.md` is present, read it for the base URL, API key, and allowed endpoints. Do not inspect local environment source files, database files, generated manifests, hidden notes, standard answers, or evaluation files.
Treat the hub as the source of record for business evidence. Treat task-local payloads as output contracts and client-facing request context only. Replace `<TASK_ENV_BASE_URL>` with the base URL from `environment_access.md` or the task's environment payload.
## Standard Workflow
1. Read the prompt and every file in `input/payloads/`.
2. Identify the `matter_id`, required top-level output keys, enum choices, required item fields, ordering rules, and numeric precision from the answer template.
3. Query the hub with the provided API key. Start with `GET /api/schema` unless the schema is already supplied, then collect matter-filtered records from the relevant endpoints:
- `/api/matters`