Menu

Individual skill

investigation-review-hub-answer

0upvotes

Produce a single-JSON-object answer for an e-discovery / regulatory investigation review task served by the Investigation Review Hub (http://task-env:9017/). Use when a task asks for a production-readiness, retention/preservation, privilege/QC, or cross-system remediation dashboard keyed to a matter ID (MTR-*-GJ / MTR-*-SEC) and an answer_template.json defines the output schema.

experiments/claude_code_glm_5_2_max/reports/skills/task_group_017/self/self_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 — Structured-JSON Answer Skill

This skill produces the deliverable for tasks built on the shared **Investigation Review Hub**: a regulatory-investigation / e-discovery review system holding matter metadata, subpoena categories, production stats, custodian sources, review documents, privilege-log entries, QC findings, retention events, and remediation actions. The deliverable is always **exactly one JSON object** conforming to a task-supplied `answer_template.json`.

## What every task looks like

All tasks on this hub follow the same shape. Recognize it, then run the same playbook:

- A **prompt** naming a client, a matter ID (`MTR-<CLIENT>-GJ` or `MTR-<CLIENT>-SEC`), and a review workstream (rolling-production gap, retention/hold gap, production-readiness, privilege/QC, cross-system remediation dashboard).
- A **context/scope payload** (`request_context.json`, `review_scope.json`, or `matter_context.json`) carrying the matter ID, client, category labels/family, and the base URL.
- An **`answer_template.json`** that is the *authoritative* output contract: required top-level keys, per-item required keys, enum choices, ordering rules, and numeric precision. The template **never contains the answer**; it defines field names, types, ordering, and enums.
- The **base URL** `http://task-env:9017/`.

## Hard source constraints