add-opponent

Automate intake, classification, labeling, and routing of opponent-provided legal documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The manual intake and organization of opponent documents can be error‑prone and time consuming. This skill automates receiving, classifying, labeling, and routing opponent-provided documents to the correct case sections, ensuring consistent metadata and ready-to-review mirrors.

Core Features & Use Cases

  • Centralized intake of opponent documents (responses, evidence, notices) with automatic labeling and mirroring.
  • Verification, routing, and metadata extraction to prepare documents for review or appeal.
  • Use Case: When the opponent submits a response, intake the documents, classify the head document and attachments, and route them to the proper parties for immediate review.

Quick Start

Intake opponent documents and prepare them for review in the current case.

Frequently Asked Questions about add-opponent

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

FAQPage Schema
How do I automate intake and organization of opponent-provided legal documents?

Automate opponent document intake by routing submissions through an Incoming documents folder, applying automatic labeling and mirroring to classify responses, evidence, and court notices for consistent case review preparation.

What is the best way to classify opponent evidence and route it to the correct case parties?

Classify opponent evidence by processing submissions through automated routing and metadata extraction, separating head documents from attachments, and directing them to defined parties for immediate review or appeal preparation.

How does opponent document intake work with existing case management workflows?

Opponent document intake works with case management workflows by reading party definitions from a .vassal/case.yaml file, processing files from an Incoming documents folder, and generating ready-to-review mirrors with consistent metadata.

Do I need a specific case configuration file to organize opponent responses?

Yes, organizing opponent responses requires a .vassal/case.yaml file with defined parties and a designated Incoming documents folder set up prior to processing submissions through the workflow.

Can I prepare opponent court notices for appeal review after intake?

Yes, after intake the workflow verifies, routes, and extracts metadata from opponent court notices, preparing ready-to-review mirrors that can be used directly for appeal preparation or further case analysis.

What limitations exist when processing opponent documents through automated case workflows?

Processing opponent documents requires a pre-configured .vassal/case.yaml with defined parties and a properly structured Incoming documents folder; without these dependencies, the automated intake, labeling, and routing cannot execute correctly.