Legal doc handler
Specialized instructions for reading, modifying, and filling PDF legal forms (e.g., California judicial council forms). Use this for any task involving PDF forms.From its SKILL.md
npx -y skills add cxcscmu/SkillLearnBench --skill legal-doc-handlerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.0 KB, 173 tokens by cl100k_base, as published. Nobody here has run it
Legal Document Handling
PDF Form Filling Strategy
- Use available PDF libraries (if installed) or CLI utilities (like pdftk or similar tools).
- CRITICAL: Always maintain the original document metadata unless explicitly told to modify it.
- Verification: Post-filling, inspect the form to confirm that key fields are populated with the correct data.
Best Practices
- Data Integrity: Never truncate or abbreviate information requested in official form fields.
- Confidentiality: Be mindful that legal documents contain PII. Avoid logging or printing sensitive document content in the conversation unless necessary for debugging.
- Workflow:
- Identify form fields.
- Map provided user data to fields.
- Perform the fill operation.
- Save as a new file (suffix "-filled").
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most legal skills give in 173 tokens
Counted across 234 of the 234 authors here whose files we hold, read 2026-08-07
- Use text operators for text fieldsin 11 of 234, across 6 files
- Consult qualified counsel before usein 11 of 234, across 3 files
- Use PatentSearch API for patent searchesin 10 of 234, across 5 files
- Confirm jurisdiction, employment type, and required clausesin 9 of 234, across 2 files
- Choose a document template and tailor role-specific termsin 9 of 234, across 2 files
- Validate compensation, benefits, and compliance requirementsin 9 of 234, across 2 files
- Add signature, confidentiality, and IP assignment terms as neededin 9 of 234, across 2 files
- Open the implementation playbook for detailed templatesin 9 of 234, across 2 files
- Use TSDR for trademark data retrievalin 9 of 234, across 4 files
- Ask for clarification if required inputs are missingin 8 of 234, across 2 files
- Set the USPTO_API_KEY environment variablein 8 of 234, across 3 files
- Use the uspto-opendata-python library for PEDSin 8 of 234, across 3 files
Said here and by no other author read
- use a PDF library or CLI utility
- maintain original document metadata
- inspect the form after filling
- confirm key fields are populated correctly
- never truncate or abbreviate requested information
- avoid printing sensitive content unless debugging
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.