Menu

Individual skill

investigation-review-hub-remediation

Solve Investigation Review Hub legal remediation tasks that require schema-conformant JSON for subpoena gap analyses, retention/preservation reviews, production readiness, privilege/QC blockers, and cross-system remediation dashboards.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_017/fewshot/naive/fewshot_attempt_02/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 JSON answer from an Investigation Review Hub. The usual inputs are a prompt, one or more task-local payload files, and an `answer_template.json`; the business evidence must come from the running hub endpoints.

## Ground Rules

- Read the prompt and every file in `input/payloads/` before querying.
- Treat `answer_template.json` as the contract for top-level keys, required item keys, enum spellings, null/zero conventions, metrics, and ordering.
- Use task-local payloads only for scope, labels, matter ID, base URL, API header, and output schema. Use hub endpoints for matter facts, records, counts, statuses, and remediation actions.
- Do not inspect environment source files, database files, generated manifests, hidden notes, judge/admin endpoints, task answers, or evaluator code.
- Return exactly one JSON object and no prose. Use stable hub IDs exactly as they appear.

## Collect Hub Evidence