Citable
Citable builds an interactive cite-checking table for US court filings (briefs...
Install
npx skills add lawve-ai/awesome-legal-skills --skill citable -g -a claude-code -y- Repository
- lawve-ai/awesome-legal-skills919
- Category
- Engineering
- Updated
- 16d ago
- License
- AGPL-3.0-only
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Citable builds an interactive cite-checking table for US court filings (briefs, memoranda, petitions, declarations, etc.). Every citation links to its pinpoint location in the record exhibit, the case (CourtListener), the statute (Cornell LII) or the treaty (flagged where one cannot be located), with a status and a note field per citation for the reviewer to fill. When the filing is revised, citable rebuilds the table, flags citation-related changes and carries the saved review forward. Use when the user asks to cite-check, build a citation table, link a brief's citations, or update a table for a revised draft.
citable
Produces citable-<document>.html (+ .csv) in the case folder: a local page, opened in Chrome, that locates sources. This is pattern-matched review: the scripts find and link the citations; the reviewer keeps the judgment role, checking each citation and recording the result in the status and note fields. For lawyers and paralegals cite-checking their own or an opponent's US filing.
Requirements
Run on the user's computer (device shell) in the folder holding the filings and exhibits. Check once: python3 (3.10+) with pdfplumber + Pillow; pdftotext, pdftoppm (poppler); tesseract (only for exhibits whose ¶ numbers are images). Missing tesseract → those links are marked approximate (amber), not wrong.
Scripts: scripts/inventory.py, scripts/build_table.py (needs scripts/template.html, scripts/data/ and scripts/vendor/ beside it; bundled, nothing to install). Copy the whole scripts/ folder into the case folder's parent or run it from the skill directory; never write into the user's PDFs. If the skill directory is not on the user's computer, copy the scripts as citable-scripts.tar.gz into the case folder (never into citable-backups/), unpack them to a scratch directory outside it, and tell the user the archive can be deleted. --out <path stem> writes the table elsewhere (links still reach the case folder). Before overwriting a table, the build copies it and its CSV to citable-backups/ beside it (timestamped; the user can delete old copies).
