Menu

Individual skill

review-hub-legal-remediation

0upvotes

Use this skill for Investigation Review Hub legal/eDiscovery tasks that ask for structured JSON gap analyses, production-readiness reviews, retention or litigation-hold reviews, privilege/QC remediation dashboards, subpoena category coverage, numeric risk metrics, or prioritized remediation action plans from hub endpoints and task-local answer templates.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_017/fewshot/opencode/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 Legal Remediation

Use this workflow when a task asks you to synthesize a legal review hub into a strict JSON answer. The common pattern is: read the prompt and task-local payloads, query the running hub for one matter, identify material preservation, collection, responsiveness, privilege, QC, retention, and archive issues, then emit exactly one JSON object matching `input/payloads/answer_template.json`.

## Boundary

- Use only task-local payload files and the Investigation Review Hub endpoints supplied by the prompt or environment note.
- Do not inspect environment source files, database files, seed files, generated manifests, hidden notes, prior answers, or evaluator files.
- Treat the hub as the source of record for business evidence. Use local payloads only for the answer schema and request context.
- Return only the requested JSON object. Do not include prose, citations, markdown fences, or diagnostic notes in the final answer.

## Fast Start

1. Read the user prompt, `input/payloads/answer_template.json`, and every other task-local payload.
Back to top