records-sync

Index legal case records and draft documents into a local case-records database.

52|12|Updated May 17, 2026
One-click install
npx skills add https://github.com/jurisupport/jurisupport-plugins --skill records-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: records-sync
Source: https://github.com/jurisupport/jurisupport-plugins/tree/main/plugins/jurisupport/skills/records-sync
Command: npx skills add https://github.com/jurisupport/jurisupport-plugins --skill records-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Synchronizes two related legal folders (case records and draft documents) into a single local case-records database without copying originals, enabling cross-referencing and historical context for faster legal writing and review.

Core Features & Use Cases

  • Syncs case records and drafted pleadings into the case-records database, linking by case number.
  • Stores text chunks, original paths, source categories (record/draft, argument/application) for robust search and audit trails.
  • Default parses only arguments and applications, with an option to include all document types via --doc-scope all.
  • Maintains original documents and provides quick health checks and search utilities for reference.

Quick Start

Run the sync_records.sh script to index your case records and draft documents into the local case-records database.

Frequently Asked Questions about records-sync

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

FAQPage Schema
How do I sync case records and draft documents into a local database?

To sync case records and drafts into a local database, run the sync_records.sh script, which indexes both folders without copying originals and links them by case number for cross-referencing.

What does indexing legal documents into a case-records database do?

Indexing legal documents into a case-records database stores text chunks, original paths, and source categories, enabling historical context and robust search for faster legal writing and review.

Can I include all document types when syncing case records and drafts?

Yes, you can include all document types when syncing case records by applying the optional --doc-scope all parameter with the sync script, overriding the default behavior of parsing only arguments and applications.

Does syncing legal case files into a local database copy my original documents?

No, syncing legal case files into a local database does not copy original documents; it indexes their text chunks and metadata while maintaining the original files in their existing paths for audit trails.

Why sync case records and drafted pleadings into a unified database?

Syncing case records and drafted pleadings into a unified database solves the problem of keeping related legal folders cross-referenced, providing fast search and historical context for legal writing workflows.

What do I need to set up before syncing case records into a local database?

Before syncing case records into a local database, you need the local case-records setup established and your case records and draft documents organized into folders for the sync script to index.