ai-tool-handoff

Coordinates bulk contract clause extraction handoff to Luminance or Kira and QAs the output.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/tk1cntt/PhapChe --skill ai-tool-handoff-tk1cntt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-tool-handoff
Source: https://github.com/tk1cntt/PhapChe/tree/main/docs/claude-for-legal-main/corporate-legal/skills/ai-tool-handoff
Command: npx skills add https://github.com/tk1cntt/PhapChe --skill ai-tool-handoff-tk1cntt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Legal due diligence often involves reviewing hundreds of contracts for specific clauses like change-of-control or exclusivity. This Skill manages the handoff of high-volume extraction to dedicated AI review tools (Luminance, Kira) and applies a QA layer so the tool's output can be trusted before it feeds into diligence findings. ## Core Features & Use Cases - Handoff Decision Logic: Determines when a document category warrants tool handoff based on volume (>50 documents), clause type suitability, and document uniformity. - Load Request Generation: Produces structured load requests specifying documents, extraction targets, and filtering instructions for whoever runs the tool. - Trust-Level QA: Applies the configured trust level (use as-is, spot-check a percentage, or full human review of flagged documents) and reports error rates. - Judgment Layer: Evaluates whether flagged clauses (e.g., change-of-control) are actually triggered by the specific deal structure, producing material findings and consent items. - Use Case: During M&A diligence, 500 customer contracts need change-of-control review. The Skill generates a Luminance load request, spot-checks 10% of flagged results, then determines which CoC clauses are actually triggered by the stock-sale structure. ## Quick Start Send these 300 customer contracts to Luminance for change-of-control and exclusivity extraction, then QA the results.

Frequently Asked Questions about ai-tool-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off bulk contract review to Luminance or Kira?

Identify the document batch from the VDR inventory, specify extraction targets per your practice configuration, and generate a load request listing documents, clause types, and filtering instructions. When results return, apply the configured trust level to QA the output.

When should I use Luminance instead of reviewing contracts directly?

Hand off when a category has more than 50 documents, the extraction target is a clause type the tool handles well (CoC, assignment, exclusivity, MFN, termination), and documents are reasonably uniform. Below that threshold, direct review or tabular review is faster.

What documents should not be sent to AI extraction tools?

Avoid handing off bespoke or heavily negotiated documents, side letters, and amendments, since tools miss context-dependent interactions with main agreements. Also skip anything where the question is deal impact rather than clause existence.

How does spot-check QA work on AI extraction results?

Randomly sample the configured percentage of flagged documents, read the actual clause in each, and compare it to the tool's extraction. If the error rate is low, accept the batch; if errors appear, widen the sample or trigger full re-review.

Can the tool decide whether a change-of-control clause is triggered?

No. The tool finds clauses, but determining whether a CoC provision is triggered requires judgment about deal structure (stock sale vs. asset sale vs. merger), the contract's definition of control, and applicable carve-outs. That judgment layer is applied after extraction.