diligence-issue-extraction

diligence-issue-extraction is a skill for Claude Code from Buildwise-Studios/claude-for-hk-law. It costs 68 tokens per session (3,001 once invoked), scanned A, original, Apache-2.0.

A process for reviewing documents in a virtual data room, an online repository used during a business deal, and extracting material legal issues. It organizes findings by legal category and prepares them in a house-memo format.

In plain words
What is it for?
Use it for due diligence, which is the legal and business review before a transaction, including finding risks, categorizing them, and passing consent items to a closing checklist.
Why use it?
It reduces the work of reviewing a large deal document set and helps focus attention on issues that meet the relevant materiality thresholds.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Part of the corporate-legal plugin — 15 skills, 1 agent shipped together

Good fit Use it for due diligence, which is the legal and business review before a transaction, including finding risks, categorizing them, and passing consent items to a closing checklist.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/buildwise-studios/claude-for-hk-law/diligence-issue-extraction
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Buildwise-Studios/claude-for-hk-law --skill diligence-issue-extraction
Clone the repo
git clone --depth 1 https://github.com/Buildwise-Studios/claude-for-hk-law

Made for: Claude Code.

Or install corporate-legal, the plugin that ships this one along with the rest of its 15 skills, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for diligence-issue-extraction

README.md
[![agentmods](https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/diligence-issue-extraction/github.svg)](https://agentmods.dev/skills/buildwise-studios/claude-for-hk-law/diligence-issue-extraction)
Your own site
<a href="https://agentmods.dev/skills/buildwise-studios/claude-for-hk-law/diligence-issue-extraction"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/diligence-issue-extraction/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for diligence-issue-extraction

Your own site · 80×15
<a href="https://agentmods.dev/skills/buildwise-studios/claude-for-hk-law/diligence-issue-extraction"><img src="https://agentmods.dev/badge/skills/buildwise-studios/claude-for-hk-law/diligence-issue-extraction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,001 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.03001
Opus 5.5 $0.00027 $0.01200
Sonnet 5.5 $0.00014 $0.00600
Haiku 4.5 $0.00007 $0.00300

Measured 1mo ago against content hash 8c7287cdbbdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

diligence-issue-extraction scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

corporate-legal/skills/diligence-issue-extraction/SKILL.md · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/diligence-issue-extraction

  1. Load ~/.claude/plugins/config/claude-for-hk-law/corporate-legal/CLAUDE.md + ~/.claude/plugins/config/claude-for-hk-law/corporate-legal/deals/[code]/deal-context.md.
  2. Use the workflow below.
  3. Check ai-tool-handoff — if category is bulk and tool is configured, hand off first.
  4. Read docs, apply materiality filter, extract per category.
  5. Findings in house memo format. Hand off consents to closing checklist.

Matter context

Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /corporate-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-hk-law/corporate-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.


Purpose

The VDR has 2,000 documents. Somewhere in there are the 30 that matter for the deal. This skill reads documents against the diligence categories and materiality thresholds from ~/.claude/plugins/config/claude-for-hk-law/corporate-legal/CLAUDE.md, extracts issues, and writes them in house memo format.

Load context

  • ~/.claude/plugins/config/claude-for-hk-law/corporate-legal/CLAUDE.md → Diligence structure (categories, materiality thresholds)
  • ~/.claude/plugins/config/claude-for-hk-law/corporate-legal/CLAUDE.md → Issues memo format (how findings are stated)
  • ~/.claude/plugins/config/claude-for-hk-law/corporate-legal/deals/[code]/deal-context.md → deal-specific thresholds, VDR location

If deal-context.md doesn't exist, ask which deal this is for.

Workflow

Step 1: Inventory the VDR

If VDR MCP (Box/Intralinks/Datasite) is connected, pull the index. Map VDR folders to diligence request list categories. Note gaps — request list categories with no corresponding VDR content.

Read the full file on GitHub · 190 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 190 lines · 68 tokens per session scan A 8c7287cdbbdb

Subscribe to this mod's changes

diligence-issue-extraction is a skill published in the GitHub repository Buildwise-Studios/claude-for-hk-law (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 3,001 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

cloud-service-agreement

Draft and fill SaaS agreement templates — cloud contract, MSA, order form, software license, pilot agreement, design partner agreement. Includes variants with SLAs and AI terms. Produces signable DOCX from Common Paper standard forms. Use when user says "SaaS agreement," "cloud contract," "MSA," "order form,"…

open-agreements/open-agreements · 103 tokens

data-privacy-agreement

Draft and fill data privacy contract and agreement templates — DPA, data processing contract, GDPR, HIPAA BAA, business associate agreement, AI addendum. Produces signable DOCX files from Common Paper standard forms. Use when user says "DPA," "data processing agreement," "HIPAA BAA," "business associate agreement," or…

open-agreements/open-agreements · 123 tokens

kr-patent-full-workflow

A coordinator for writing a Korean patent specification from start to finish. It guides the work through invention interviews, claim preparation, technical details, consistency checks, and final DOCX output.

lsj4232/KR_PATENT_SKILL · 305 tokens

kr-patent-docx-builder

Nástroj na automatické vytváranie súborov DOCX s textom patentovej prihlášky podľa formulárov Kórejského úradu pre duševné vlastníctvo.

lsj4232/KR_PATENT_SKILL · 224 tokens

kr-patent-format-unify

A Microsoft Word document-formatting tool for Korean patent specifications. It finds newly added paragraphs and copies the surrounding paragraph and text formatting onto them.

lsj4232/KR_PATENT_SKILL · 560 tokens

kr-patent-navigation-pane

A tool for adding Word document outline levels to Korean patent specifications without changing their visible formatting.

lsj4232/KR_PATENT_SKILL · 394 tokens