Menu

Individual skill

review-hub-remediation

0upvotes

Build schema-conforming Investigation Review Hub gap, retention, production-readiness, and remediation dashboard JSON outputs. Use when a task provides an Investigation Review Hub base URL, matter ID, answer_template.json, and asks Codex to identify preservation, collection, privilege-log, waiver, responsiveness/QC, retention, category coverage, metrics, or prioritized remediation actions.

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

# Review Hub Remediation

Use this skill to turn Investigation Review Hub evidence into the exact JSON object requested by a task-local answer template.

## Workflow

1. Read the user prompt and every task-local payload. Treat `answer_template.json` as the output contract: required keys, enum spelling, field names, ordering, numeric precision, and whether null or zero is expected.
2. Extract the matter ID, hub base URL, and any SQL API-key header from the prompt or payloads. Do not inspect local environment source, databases, generated manifests, hidden notes, answer files, or evaluator files.
3. Collect hub evidence for the matter. Prefer SQL queries through the hub because REST search endpoints can be capped:

   ```bash
   python path/to/skill/scripts/collect_hub.py \
     --base-url "$TASK_ENV_BASE_URL" \
     --matter-id "$MATTER_ID" \
Back to top