Localized reading guide
legal-responsePurpose, usage and source
Generate a response to a common legal inquiry using configured templates, with built-in escalation checks for situations that shouldn't use a templated reply. Use when responding to data subject requests, litigation hold notices, vendor legal questions, NDA requests from business teams, or subpoenas.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
legal/skills/legal-response/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Data
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Generate a response to a common legal inquiry using configured templates, with built-in escalation checks for situations that shouldn't use a templated reply. Use when responding to data subject requests, litigation hold notices, vendor legal questions, NDA requests from business teams, or subpoenas.
How the upstream workflow works
Subpoena / Legal Process Escalation Triggers
ALWAYS requires counsel review (templates are starting points only) Privilege issues identified Third-party data involved Cross-border production issues
Upstream passage · L97 ↗6. Subpoena / Legal Process
Acknowledgment of receipt Request for extension Compliance cover letter Key template elements:
Upstream passage · L299 ↗Step 1: Identify Inquiry Type
Accept the inquiry type from the user. If the type is ambiguous, show available categories and ask for clarification.
Upstream passage · L35 ↗/legal-response [inquiry-type]Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- /legal-response -- Generate Response from Templates
- Invocation
- Step 1: Identify Inquiry Type
- Step 2: Load Template
- Step 3: Check Escalation Triggers
- Universal Escalation Triggers (Apply to All Categories)
- Data Subject Request Escalation Triggers
- Discovery Hold Escalation Triggers
- Vendor Question Escalation Triggers
- NDA Request Escalation Triggers
- Subpoena / Legal Process Escalation Triggers
- Step 4: Gather Specific Details
- Step 5: Generate Response
- Customization Guidelines
- Step 6: Template Creation (If No Template Exists)
- 1. Data Subject Requests (DSRs)
- 2. Discovery Holds (Litigation Holds)
- 3. Privacy Inquiries
- 4. Vendor Legal Questions
- 5. NDA Requests
- 6. Subpoena / Legal Process
- 7. Insurance Notifications
- Template Organization
- Template Lifecycle
- Template Creation Guide
- 1. Define the Use Case
- 2. Identify Required Elements
- 3. Define Variables
- 4. Draft the Template
- 5. Define Escalation Triggers
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
b3a0585ee00a53ccb159fbf5b7dd4d4b45c39e5e65cc8f4f39cbb134fef493db