Menu

Individual skill

investigation-review-hub-remediation

0upvotes

Use this skill for legal or eDiscovery tasks that require structured JSON gap analyses, production-readiness reviews, retention/preservation reviews, or remediation dashboards using the Investigation Review Hub API as the source of record.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_017/fewshot/fewshot_attempt_03/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 when a task asks for a structured legal review deliverable from an Investigation Review Hub: production gaps, subpoena/request category readiness, retention or preservation losses, privilege-log defects, QC miscoding, source collection gaps, available remediation sources, metrics, and prioritized action plans.

## Source Discipline

- Use only the task prompt, task-local payloads, and the running hub endpoints identified by the task or its environment access file.
- Do not inspect local environment source code, database files, seed files, manifests, hidden notes, standard answers, or evaluation files.
- Treat the hub as the source of record for business evidence. Task-local payloads provide output schema, matter context, labels, and constraints.
- If a SQL endpoint is provided, use it only through the documented API URL and credentials. Never use local database access.
- Return exactly the requested JSON object when the prompt asks for JSON only.

## Workflow
Back to top