Individual skill

review-hub-remediation-json

Build structured JSON answers for Investigation Review Hub legal review tasks involving production gaps, retention and preservation losses, source collection gaps, privilege-log defects, QC miscoding, and remediation action plans. Use when a prompt asks for a JSON-only subpoena, SEC, grand jury, production-readiness, gap-analysis, or remediation dashboard answer from Review Hub API endpoints and an answer_template.json file.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_017/fewshot/deepagents/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

# Review Hub Remediation JSON

## Core Rule

Return exactly the JSON object requested by the task template. Treat the task prompt, task-local payloads, and the running Review Hub API as the only business evidence. Do not inspect local environment source, database files, generated manifests, hidden notes, evaluator files, or answer files.

## Workflow

1. Read the prompt, every task-local payload, and the full `answer_template.json`.
2. Extract the matter ID, base URL, any API key header, required top-level keys, enum values, field names, ordering rules, and numeric precision rules.
3. Collect Review Hub evidence for only the requested matter. Use `scripts/fetch_review_hub.py` if a generic fetch-and-filter bundle would help:

   ```bash
   python skill/scripts/fetch_review_hub.py "$TASK_ENV_BASE_URL" "$MATTER_ID" --api-key "$API_KEY" > hub.json