intake

Automate legal document intake with OCR, renaming, and index updates.

5|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/strigov/vassal-litigator --skill intake-strigov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intake
Source: https://github.com/strigov/vassal-litigator/tree/main/skills/intake
Command: npx skills add https://github.com/strigov/vassal-litigator --skill intake-strigov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the intake and organization of client materials for a legal case, reducing manual sorting, labeling, and indexing work, and ensuring smooth integration with the case workflow.

Core Features & Use Cases

  • Intake and organization of incoming client documents, OCR processing, and automatic file renaming.
  • Creation of document mirrors, updating of the case index, and maintenance of the case history to support traceability.
  • Support for organizing documents into a chronological structure, preparing materials for hearings, and handing off tasks to Haiku-subagents for classification.

Quick Start

Provide a batch of incoming documents and instruct the AI to classify, rename, and index them into the case timeline.

Frequently Asked Questions about intake

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

FAQPage Schema
How do I automate OCR and renaming for incoming legal case documents?

Automating OCR and renaming for legal case documents is handled by ingesting incoming materials, applying OCR processing, and automatically renaming files to organize them into a chronological case structure.

What is the best way to organize client materials intake for legal cases?

Organizing client materials intake is best handled by automating document classification, creating document mirrors, updating the case index, and maintaining case history to ensure full traceability.

How does subagent dispatch work for legal document classification?

Subagent dispatch for legal document classification works by handing off intake tasks to Haiku-subagents, enabling deterministic planning and idempotent processing with history tracking for client materials.

Can I process document intake idempotently with history tracking?

Processing document intake idempotently with history tracking is fully supported, ensuring repeated operations do not duplicate work and maintaining a traceable record of all case materials.

How do I prepare client documents for a hearing timeline?

Preparing client documents for a hearing timeline involves organizing incoming materials into a chronological structure, creating document mirrors, and updating the case index to support the hearing workflow.

Do I need any dependencies to run automated legal document intake?

No external dependencies are required to run automated legal document intake, as the Skill operates independently to handle OCR, classification, and case index updates for client materials.