Individual skill
reflect-3_attempt_03
Not available
experiments/claude_code_deepseek_v4_pro_max/reports/skills/task_group_017/reflect-3/reflect-3_attempt_03/SKILL.md
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.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
Declared tags are partial or unavailable.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SCHEMA_REFERENCE.mddoc · 6,304 bytesSKILL.mdcore · 11,139 bytesSKILL.mdcore · 11,139 bytesSKILL.mdcore · 11,139 bytes
Read excerpt
# Investigation Review Hub — Structured JSON Deliverable Skill
## When to use
Use this skill when a task prompt asks you to produce a structured JSON deliverable from an **Investigation Review Hub** — a read-only REST API serving matter metadata, subpoena categories, production stats, custodian sources, review documents, privilege logs, QC findings, retention events, and remediation actions. The prompt will reference `<TASK_ENV_BASE_URL>` and provide an `answer_template.json` schema. Return **only** the JSON object; no surrounding prose.
## Phase 1 — Inventory the input directory
Every task instance ships with these files inside `input/`:
| File | What it carries |
|---|---|
| `prompt.txt` | Business narrative, matter name, deliverable type, `<TASK_ENV_BASE_URL>` placeholder |
| `payloads/answer_template.json` | Required JSON schema: top-level keys, per-item required keys, enum choices, ordering rules, numeric precision |
| `payloads/request_context.json` *or* `review_scope.json` *or* `matter_context.json` | The `matter_id` string, client-facing category labels, any scope notes |