Update and verify court case document indexes in index.yaml with atomic commits.
npx skills add https://github.com/strigov/vassal-litigator --skill update-index
Please help me install this Agent Skill. Skill: update-index Source: https://github.com/strigov/vassal-litigator/tree/main/skills/update-index Command: npx skills add https://github.com/strigov/vassal-litigator --skill update-index
Keeps a court case document index up-to-date and verified by reading the index.yaml, scanning the filesystem, generating/refreshing md mirrors, and logging changes. It ensures consistency between the on-disk case files and the index metadata, preventing drift after file operations or manual edits.
Run an index refresh after updating files to ensure the case index reflects the current document set.
High-intent search queries and answers about installing and using this skill.
A four-phase contract—preview, confirm, apply, verify—maintains index accuracy by reading index.yaml, scanning documents, refreshing mirrors, and logging history. The orchestrator previews pending changes, waits for confirmation, applies updates atomically, and verifies the final state.
The best way to automate document index verification is to run a workflow that scans the filesystem, reads index.yaml, refreshes md mirrors, and logs provenance metadata. This validates that case records remain consistent after file operations or manual edits.
Index.yaml synchronization prevents metadata drift by scanning the filesystem, comparing it against the recorded index, refreshing md mirrors, and logging provenance and extraction metadata to history.md. This keeps case records consistent and auditable after any file operation.
Yes, you can refresh md mirrors and log history without manual intervention by running the update-index workflow after file operations. The orchestrator reads index.yaml, scans documents, updates mirrors, and logs provenance metadata automatically, though a confirm phase allows for oversight.
You should not use an automated case document index update when files are still being actively written or modified, as scanning a filesystem mid-operation can capture an incomplete state. Ensure all file operations are complete before running synchronization to avoid logging inaccurate provenance metadata.
The update-index workflow requires no external dependencies. It operates using an internal orchestrator to read index.yaml, scan the filesystem, refresh mirrors, and log history, and can delegate mechanical tasks to a subagent when needed for reliable index maintenance.
strigovAutomate intake and integration of client evidence into a legal case chronology.
strigovAnalyze legal cases and generate auditable Markdown and DOCX reports.
anilcan-karaExtract text from PDFs and scanned documents using pymupdf or marker-pdf.
CygnusfearCreate modular Obsidian-compatible markdown wikis for project plans.
