Individual skill
investigation-review-hub-remediation
Use this skill for Investigation Review Hub legal review tasks that require structured JSON gap analyses, production-readiness reviews, retention or preservation reviews, remediation dashboards, privilege/QC metrics, category coverage, or prioritized action plans from subpoena matter records. Trigger whenever the prompt mentions Investigation Review Hub, matter IDs, subpoena categories, productions, custodian sources, review documents, privilege logs, QC findings, retention events, remediation actions, or an answer_template.json JSON contract.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_017/fewshot/opencode/fewshot_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
- 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
SKILL.mdcore · 8,437 bytesSKILL.mdcore · 8,437 bytesSKILL.mdcore · 8,437 bytesSKILL.mdcore · 8,437 bytesSKILL.mdcore · 8,437 bytesSKILL.mdcore · 8,437 bytesSKILL.mdcore · 8,437 bytesSKILL.mdcore · 8,437 bytesSKILL.mdcore · 8,437 bytesSKILL.mdcore · 8,437 bytesSKILL.mdcore · 8,437 bytesSKILL.mdcore · 8,437 bytesreferences/record_to_output_map.mddoc · 6,086 bytesscripts/fetch_hub_snapshot.pyruns · 4,307 bytesscripts/validate_structured_answer.pyruns · 7,842 bytes
Read excerpt
# Investigation Review Hub Remediation
Use this skill to answer matter-scoped legal operations review tasks from an Investigation Review Hub. The expected output is usually a single JSON object that conforms exactly to a task-local `input/payloads/answer_template.json`.
## Hard Boundaries
- Use only the task prompt, task-local payload files, and the running Investigation Review Hub endpoints allowed for the task.
- Do not inspect local environment source code, database files, generated manifests, hidden notes, answer files, evaluator files, or unrelated matters.
- Filter every hub query by the requested `matter_id`. Broad all-matter pulls introduce noise and can contaminate the answer.
- Treat the answer template as binding: top-level keys, field names, enum values, required keys, ordering rules, numeric precision, and JSON-only final output all come from the template.
- Use stable record IDs exactly as they appear in the hub. Do not paraphrase IDs.
## Workflow
