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.
Instructions your experts follow when using this skill.
Packaging adaptation by AutoGPT, 2026-09-25. Original authorship and licence are retained. Changes are limited to the recorded name, metadata and local references; see ATTRIBUTION.md in this package.
If you see unfamiliar placeholders or need to check which tools are connected, see .
Generate a response to a common legal inquiry using configured templates. Customizes the response with specific details and includes escalation triggers for situations that should not use a templated response.
Important: This command assists with legal workflows but does not provide legal advice. Generated responses should be reviewed by qualified legal professionals before being sent, especially for regulated communications.
/legal-response [inquiry-type]
Common inquiry types:
dsr or data-subject-request -- Data subject access/deletion/correction requestshold or discovery-hold -- Litigation hold noticesvendor or vendor-question -- Vendor legal questionsnda or nda-request -- NDA requests from business teamsprivacy or privacy-inquiry -- Privacy-related questionssubpoena -- Subpoena or legal process responsesinsurance -- Insurance claim notificationscustom -- Use a custom templateIf no inquiry type is provided, ask the user what type of response they need and show available categories.
Accept the inquiry type from the user. If the type is ambiguous, show available categories and ask for clarification.
Look for templates in local settings (e.g., legal.local.md or a templates directory).
If templates are configured:
If no templates are configured:
Before generating any response, evaluate whether this situation has characteristics that should NOT use a templated response.
When an escalation trigger is detected:
Prompt the user for the details needed to customize the response:
Data Subject Request:
Discovery Hold:
Vendor Question:
NDA Request:
Populate the template with the gathered details. Ensure the response:
Present the draft response to the user for review before sending.
Required customization — Every templated response MUST be customized with:
Tone adjustment — Adjust tone based on:
Jurisdiction-specific adjustments:
If the user wants to create a new template, walk through the Template Creation Guide (see below) and present the finished template for review. Suggest the user save the approved template to their local settings for future use.
Sub-categories:
Key template elements:
Example template structure:
Subject: Your Data [Access/Deletion/Correction] Request - Reference {{request_id}}
Dear {{requester_name}},
We have received your request dated {{request_date}} to [access/delete/correct] your personal data under [applicable regulation].
[Acknowledgment / verification request / fulfillment details / denial basis]
We will respond substantively by {{response_deadline}}.
[Contact information]
[Rights information]
Sub-categories:
Key template elements:
Example template structure:
Subject: LEGAL HOLD NOTICE - {{matter_name}} - Action Required
PRIVILEGED AND CONFIDENTIAL
ATTORNEY-CLIENT COMMUNICATION
Dear {{custodian_name}},
You are receiving this notice because you may possess documents, communications, or data relevant to the matter referenced above.
PRESERVATION OBLIGATION:
Effective immediately, you must preserve all documents and electronically stored information (ESI) related to:
- Subject matter: {{hold_scope}}
- Date range: {{start_date}} to present
- Document types: {{document_types}}
DO NOT delete, destroy, modify, or discard any potentially relevant materials.
[Specific instructions for systems, email, chat, local files]
Please acknowledge receipt of this notice by {{acknowledgment_deadline}}.
Contact {{legal_contact}} with any questions.
Sub-categories:
Key template elements:
Sub-categories:
Key template elements:
Sub-categories:
Key template elements:
Sub-categories:
Key template elements:
Critical note: Subpoena responses almost always require individualized counsel review. Templates serve as starting frameworks, not final responses.
Sub-categories:
Key template elements:
Templates should be organized by category and maintained in the team's local settings. Each template should include:
When helping users create new templates:
{{requester_name}}, {{response_deadline}}, {{matter_reference}}## Template: {{template_name}}
**Category**: {{category}}
**Version**: {{version}} | **Last Reviewed**: {{date}}
**Approved By**: {{approver}}
### Use When
- [Condition 1]
- [Condition 2]
### Do NOT Use When (Escalation Triggers)
- [Trigger 1]
- [Trigger 2]
### Variables
| Variable | Description | Example |
|---|---|---|
| {{var1}} | [what it is] | [example value] |
| {{var2}} | [what it is] | [example value] |
### Subject Line
[Subject template with {{variables}}]
### Body
[Response body with {{variables}}]
### Follow-Up Actions
1. [Action 1]
2. [Action 2]
### Notes
[Any special instructions for users of this template]
## Generated Response: [Inquiry Type]
**To**: [recipient]
**Subject**: [subject line]
---
[Response body]
---
### Escalation Check
[Confirmation that no escalation triggers were detected, OR flagged triggers with recommendations]
### Follow-Up Actions
1. [Post-send actions]
2. [Calendar reminders to set]
3. [Tracking or logging requirements]
Files installed alongside these instructions.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.