Menu

Individual skill

investigation-review-hub-gap-analysis

0upvotes

Produce a structured JSON gap/remediation analysis for a legal investigation matter by querying an Investigation Review Hub API. Use when a task asks for a production gap analysis, retention/preservation review, cross-system remediation dashboard, or production-readiness review returned as a single JSON object conforming to a provided answer template.

experiments/claude_code_glm_5_2_max/reports/skills/task_group_017/reflect-3/reflect-3_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 Gap Analysis

This skill solves tasks that ask for a **structured JSON** gap / remediation analysis of a single
legal-investigation matter (grand jury or SEC subpoena). Each task gives you:

- a **prompt** describing the matter and deliverable,
- `input/payloads/answer_template.json` — the exact output schema (required keys, field types,
  **enum choices**, **ordering rules**, numeric precision),
- a context payload (`request_context.json` / `review_scope.json` / `matter_context.json`) with the
  matter id, client, and category labels,
- `environment_access.md` — the hub connection details and allowed endpoints for **this task**.

The deliverable is **one JSON object** that conforms to the template. No prose outside the JSON.
Back to top