legal-canned-responses

Generate templated responses for common legal inquiries with escalation detection. Use when drafting legal responses.

Zur Installation springen

Repository: ThomasMoreAI/legal-skills-open
Letzte Quellaktivität: 1. Juni 2026 um 17:27
Erkannte Sprache von SKILL.md: Englisch
Sterne: 40
Forks: 4

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Zurück zur Suche Zurück zur Installation

name	legal-canned-responses
title	Legal Canned Responses Skill
description	Generate templated responses for common legal inquiries with escalation detection. Use when drafting legal responses.
author	borghei
author_url	https://github.com/borghei/Claude-Skills/tree/main/legal/legal-canned-responses
license	MIT
version	0.1.0
execution_mode	open
jurisdiction	general
practice	general
language	en

⚠️ EXPERIMENTAL — This skill is provided for educational and informational purposes only. It does NOT constitute legal advice. All responsibility for usage rests with the user. Consult qualified legal professionals before acting on any output.

Legal Canned Responses Skill

Overview

Production-ready toolkit for generating templated responses to common legal inquiries with built-in escalation detection. Covers 7 response categories with multiple sub-types each, plus a universal and category-specific escalation trigger system. Designed for legal operations teams handling high volumes of recurring inquiries while ensuring critical matters are routed to counsel.

Table of Contents

Tools
Reference Guides
Workflows
Response Categories
Escalation System
Troubleshooting
Success Criteria
Scope & Limitations
Anti-Patterns
Tool Reference

Tools

1. Response Generator (`scripts/response_generator.py`)

Generate formatted legal responses from templates with variable substitution and escalation detection.

python scripts/response_generator.py \
  --category dsr --sub-type acknowledgment \
  --var requestor_name="Jane Doe" \
  --var request_type="access" \
  --var request_date="2026-04-10"

python scripts/response_generator.py \
  --category nda --sub-type standard-form \
  --var counterparty="Acme Corp" \
  --var purpose="due diligence" --json

python scripts/response_generator.py \
  --category discovery --sub-type initial-notice \
  --var matter_name="Smith v. Corp" \
  --var custodians="Engineering,Sales"

2. Escalation Detector (`scripts/escalation_detector.py`)

Analyze inquiry text for escalation triggers and recommend routing.

python scripts/escalation_detector.py \
  --text "We received a subpoena from the DOJ regarding our pricing practices"

python scripts/escalation_detector.py \
  --text  --json

python scripts/escalation_detector.py \
  --category vendor \
  --text

Category	Sub-Types	Description
Data Subject Requests (DSR)	acknowledgment, verification, fulfillment, denial, extension	GDPR/CCPA data subject right requests
Discovery/Litigation Holds	initial-notice, reminder, modification, release	Litigation hold management
Privacy Inquiries	cookies, data-sharing, children, transfers	General privacy questions
Vendor Legal Questions	contract-status, amendments, certifications, audit	Vendor/supplier legal matters
NDA Requests	standard-form, counterparty-markup, decline, renewal	Non-disclosure agreement lifecycle
Subpoena/Legal Process	acknowledgment, objection, extension, compliance	Legal process responses
Insurance Notifications	initial-claim, supplemental-info, reservation-of-rights	Insurance claim management

Sub-Type	Use When	Key Variables
acknowledgment	New DSR received	requestor_name, request_type, request_date
verification	Identity verification needed	requestor_name, verification_method
fulfillment	Request completed	requestor_name, request_type, data_description
denial	Request denied with reason	requestor_name, request_type, denial_reason
extension	Need more time	requestor_name, request_type, extension_reason, new_deadline

Sub-Type	Use When	Key Variables
initial-notice	New litigation hold issued	matter_name, custodians, data_types
reminder	Periodic hold reminder	matter_name, reminder_number
modification	Hold scope changed	matter_name, modification_description
release	Hold lifted	matter_name, release_date

#	Trigger	Why
1	Potential or active litigation	Legal exposure requires counsel assessment
2	Regulatory investigation or inquiry	Regulatory response requires strategic approach
3	Government or law enforcement contact	Constitutional and procedural rights at stake
4	Binding legal commitment requested	Cannot create legal obligations without counsel
5	Criminal liability exposure	Requires immediate counsel involvement
6	Media attention or press inquiry	Reputational risk requires coordinated response
7	Unprecedented or novel situation	No template exists; bespoke legal analysis needed
8	Multi-jurisdictional conflict	Cross-border legal complexity requires expert analysis

Problem	Cause	Solution
Missing variable in output	Required variable not provided	Check template requirements; provide all required `--var` parameters
Wrong template selected	Category/sub-type mismatch	Review category descriptions; ensure sub-type matches inquiry type
False positive escalation	Common words matching trigger patterns	Provide `--category` to use category-specific triggers; review matched triggers
False negative escalation	Inquiry text too vague	Add more context to inquiry text; run both universal and category-specific checks
Template too generic	Using default values	Replace all placeholder values with actual organization-specific details
Discovery hold sent to wrong custodians	Custodian list outdated	Verify custodian list against current employees and systems
Subpoena response not flagged	Missing category context	Always use `--category subpoena` for legal process; subpoena category always escalates
Response tone inappropriate	Wrong audience context	Select appropriate sub-type; customize tone per audience

Anti-Pattern	Why It Fails	Better Approach
Sending templated response without review	May miss context-specific nuances; legal risk	Always review generated response before sending
Ignoring escalation triggers	Critical matters mishandled; legal exposure	Run escalation detector on every inquiry; treat all triggers seriously
Using templates for novel situations	Templates assume standard scenarios; novel situations need bespoke analysis	Escalate novel situations to counsel; create new template after resolution
Hardcoding organization details in templates	Templates become non-portable; updates missed	Use variable substitution; maintain variables in configuration
Skipping identity verification for DSRs	GDPR/CCPA require verification before fulfillment	Always send verification sub-type before fulfillment

usage: response_generator.py [-h] [--json]
                              --category {dsr,discovery,privacy,vendor,nda,subpoena,insurance}
                              --sub-type SUB_TYPE
                              [--var KEY=VALUE [KEY=VALUE ...]]

options:
  -h, --help            Show help message and exit
  --json                Output in JSON format
  --category            Response category
  --sub-type            Response sub-type within category
  --var                 Variable substitution as KEY=VALUE pairs

usage: escalation_detector.py [-h] [--json]
                               --text TEXT
                               [--category {dsr,discovery,privacy,vendor,nda,subpoena,insurance}]

options:
  -h, --help            Show help message and exit
  --json                Output in JSON format
  --text                Inquiry text to analyze for escalation triggers
  --category            Optional category for category-specific trigger detection