Menu

Individual skill

investigation-review-hub-remediation-json

0upvotes

Solve Investigation Review Hub legal production, preservation, privilege, QC, retention, and remediation dashboard tasks as exact structured JSON.

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

# Investigation Review Hub Remediation JSON

Use this skill when a task asks for a structured JSON gap analysis, production-readiness review, retention review, or remediation dashboard using the Investigation Review Hub.

## Boundaries

- Return exactly one JSON object matching `input/payloads/answer_template.json`; do not include prose outside the JSON.
- Use only the task prompt, task-local payloads, and the Investigation Review Hub endpoints named by the task environment.
- Do not inspect local environment source files, database files, generated manifests, hidden notes, answer files, judge/admin endpoints, or evaluator code.
- Treat hub record IDs as authoritative. Do not invent matter, source, event, QC finding, document, privilege, action, or category IDs.

## First Pass

1. Read the prompt, `answer_template.json`, and every task-local context payload.
Back to top