legal-response
Skill1 starsChanged 7 months agoMITView on GitHub
Draft responses to common legal inquiries using templates with built-in escalation checks for situations requiring senior counsel. Use when responding to data subject requests, litigation holds, vendor questions, or regulatory inquiries. Trigger with "draft legal response", "respond to this legal inquiry", "DSR response", or "reply to legal notice".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- EvolutionAPI/evo-nexustheir own version, first seen Oct 8, 2026
- thestratcore/My-skillstheir own version, first seen Jul 10, 2026
- evolution-foundation/evo-nexustheir own version, first seen Apr 20, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- anthropics/knowledge-work-plugins★ 36ksame name
- EvolutionAPI/evo-nexus★ 545same name
- evolution-foundation/evo-nexus★ 535same name
- thestratcore/My-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Before drafting, check whether the matter should be escalated:
- Distinctive: line 41
If escalation triggers, output the escalation recommendation instead of a draft.
- Distinctive: line 49
Verify factual assertions, confirm deadlines, ensure no unintended admissions, check privilege preservation, and confirm every point in the …
- Distinctive: line 80
Always run escalation checks before drafting.
- Distinctive: line 81
Never waive privilege in a templated response.
- Distinctive: line 85
Never include more information than what was requested.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Legal Response Drafting
Draft responses to common legal inquiries using organizational templates. Includes escalation checks to ensure matters requiring senior or outside counsel are not handled with a standard template.
Workflow
Step 1: Classify the Inquiry
Determine type: DSR (access, deletion, correction), litigation hold, vendor legal question, regulatory inquiry, cease and desist, subpoena, or general correspondence.
Step 2: Run Escalation Checks
Before drafting, check whether the matter should be escalated:
- Senior counsel: Litigation risk above $100K, regulatory enforcement, executive involvement, M&A, novel questions.
- Outside counsel: Active litigation, government investigation, criminal exposure, specialized regulatory domains.
- Executive: PR risk, board-level disclosure, material financial exposure.
- Do not template: Ambiguous facts, references to ongoing litigation, or sender is an enforcement agency.
If escalation triggers, output the escalation recommendation instead of a draft.
Step 3: Select and Populate Template
Match to the appropriate response template. Populate with case-specific facts. Adjust tone based on relationship. Include required disclaimers and privilege markings.
Step 4: Validate
Verify factual assertions, confirm deadlines, ensure no unintended admissions, check privilege preservation, and confirm every point in the inquiry is addressed.
Output Format
## Legal Response Draft
**Inquiry Type**: [Classification] | **Received**: [Date] | **Due**: [Date]
**Escalation Check**: [PASSED / ESCALATED to (whom)]
### Draft Response
[Full text of the drafted response]
### Internal Notes
- Template used: [Template ID]
- Follow-up actions: [List with owners and dates]
- Deadline: Response must be sent by [date]Examples
User: "We received a GDPR data access request from a customer in France" Action: Classify as DSR-access, run escalation checks (standard -- no escalation), select GDPR Article 15 template, populate with 30-day deadline, and draft acknowledgment.
User: "A competitor sent us a cease and desist about our product name" Action: Classify as cease-and-desist, escalation triggered (IP dispute with litigation risk), output escalation recommendation to IP counsel.
User: "Our vendor is asking about our indemnification obligations under the MSA" Action: Classify as vendor-question, no escalation, review the MSA clause, draft response explaining contractual obligations.
Best Practices
- Always run escalation checks before drafting. A templated response to a matter needing senior judgment creates significant risk.
- Never waive privilege in a templated response.
- Calculate response deadlines from date of receipt, not date of drafting.
- For DSRs, verify requester identity before providing personal data.
- For regulatory responses, err on the side of escalation.
- Never include more information than what was requested.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

