Menu

Individual skill

investigation-review-hub-remediation-json

0upvotes

Use this skill whenever a task asks for a structured JSON gap analysis, production-readiness review, retention/preservation review, or cross-system remediation dashboard from an Investigation Review Hub. It is tailored for legal subpoena or regulatory-review matters where the answer must use hub record IDs, request category codes, privilege/QC/retention/source evidence, numeric metrics, prioritized actions, and a provided answer_template.json.

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

Use this skill for one-pass legal review tasks that require a JSON-only answer from an Investigation Review Hub. The recurring job is to gather all matter-scoped hub records, identify material production or preservation blockers, normalize them into the task's template enums, compute metrics, and return exactly one JSON object.

## Source Discipline

Use only sources allowed by the prompt:

- The task-local prompt and payloads, especially `answer_template.json`.
- The running hub endpoints named by the prompt or payloads.
- The read-only SQL endpoint when supplied.

Do not inspect local environment source, database files, seed files, generated manifests, hidden notes, evaluator files, or answer files. Treat the hub as source of record for matter facts. Task-local payload files may define client context, category labels, endpoint names, and output schema, but business evidence should come from the hub unless the prompt says otherwise.
Back to top