Individual skill
investigation-review-hub-gap-analysis
Produce a structured JSON gap/remediation analysis for a litigation or investigation matter from an "Investigation Review Hub" style data source (matters, subpoena categories, productions, custodian sources, review documents, privilege entries, QC findings, retention events, remediation actions). Use when a task asks for a first-rolling-production gap analysis, retention/litigation-hold gap review, production-readiness review, or cross-system remediation dashboard, and the answer must conform to a provided answer_template.json. The core skill is separating the handful of MATERIAL escalated records from the surrounding realistic NOISE, then mapping them faithfully into the template's objects, metrics, enums, and ordering.
experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_017/reflect-3/reflect-3_attempt_03/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
- data 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 — structured gap / remediation analysis
## What these tasks look like
You are given, in the task's `input/` directory:
- A `prompt.txt` naming a client, a `matter_id` (e.g. a stable `MTR-…` identifier), and the deliverable (gap analysis / retention review / readiness review / remediation dashboard).
- A payload file (`request_context.json`, `review_scope.json`, `matter_context.json`, …) that gives client-facing context and sometimes category labels. **Treat payloads as context only — the authoritative evidence lives in the hub.**
- An `answer_template.json` that fully specifies the output contract: `required_top_level_keys`, the object schemas, `enums`/`enum_choices`, `ordering_rules`, and numeric precision. **This file does not contain the answer; it defines the shape.**
The hub itself is a read-only data service reachable through the run's environment access file (a base URL + credential header it provides). It exposes one read endpoint per record type and a read-only SQL `POST` query endpoint. **Read connection details (base URL, credential, exact paths) from the run's environment access file at solve time — do not assume them.** Return **exactly one JSON object** conforming to the template and nothing else.
## The hub data model (verify at runtime with the schema endpoint)
