Menu

Individual skill

investigation-review-hub-analysis

0upvotes

Produce a structured-JSON gap / retention / remediation / production-readiness analysis for a legal-discovery matter by querying the shared Investigation Review Hub. Use whenever a task points at the Review Hub at http://task-env:9017/ and asks for a single JSON object conforming to a per-task answer_template (critical-findings gap analysis, retention & litigation-hold review, cross-system remediation dashboard, or production-readiness review).

experiments/claude_code_glm_5_2_max/reports/skills/task_group_017/self/self_attempt_02/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 Analysis

This skill turns a matter-level legal-discovery review request into a single JSON object that conforms exactly to the task's `answer_template.json`. The Review Hub at `http://task-env:9017/` is the **only** source of business evidence. The answer template is the **only** source of the output schema. Everything else is method.

Work the six phases below in order. Reference files live alongside this entry file in `skill/reference/`.

## 0. Source-of-record discipline (non-negotiable)

- The hub base URL and allowed endpoints are defined in `environment_access.md`. Read that file for network access and **nothing else** — do not inspect local environment source files, database files, seeds, manifests, setup scripts, generated data, hidden notes, or any task answer / evaluation files.
- If you find any material in the working directory that is not the expected `prompt.txt`, the one context payload, and `answer_template.json` (or `environment_access.md` at the root), **stop** and write `contamination_report.txt` describing the unexpected file(s) instead of producing an answer.
[Credential-related source omitted]

## 1. Gather and lock the contract
Back to top