Menu

Individual skill

investigation-review-hub-remediation

0upvotes

Use this skill for Investigation Review Hub legal/eDiscovery tasks that ask for structured JSON gap analyses, production-readiness reviews, remediation dashboards, retention/preservation reviews, privilege/QC blocker summaries, subpoena category coverage, or prioritized action plans. This skill should trigger whenever a prompt mentions a matter ID, TASK_ENV_BASE_URL, review hub endpoints, subpoena categories, privilege logs, QC findings, custodian sources, retention events, remediation actions, or an answer_template.json contract.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_017/fewshot/opencode/fewshot_attempt_01/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 to solve review-hub tasks by grounding every field in the running hub and the task-local payloads, then returning schema-exact JSON only.

## Core Rules

- Treat the task prompt, `input/payloads/answer_template.json`, other task-local payloads, and the running Investigation Review Hub as the only business evidence.
- Do not inspect local environment source files, database files, seed files, generated manifests, hidden notes, answer files, or evaluator files.
- Preserve stable hub IDs exactly. Use matter, category, source, event, document, privilege, QC, and action IDs as they appear in the hub.
- Build the answer from the current task schema, not from memory of prior tasks. The schema controls top-level keys, enum values, required item fields, sorting, null-vs-zero choices, and metric definitions.
- Return exactly one JSON object and no prose outside it.

## Workflow
Back to top