[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718DBVTFC5Y416NE4HZV78S":3,"skill-same:01M718DBVTFC5Y416NE4HZV78S":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M718DBVTFC5Y416NE4HZV78S","legal-response",null,"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.","anthropics\u002Fknowledge-work-plugins","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7188MPC48111TN566QNQE3X",35660,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Flegal\u002Fskills\u002Flegal-response\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"legal","legal response","reply","templates","questions","vendor","requests","with","type","business","use","teams","for","escalation","data","generate","common","when","litigation","nda","2026-11-10 10:12:30",false,"---\nname: legal-response\ndescription: 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.\nargument-hint: \"[inquiry-type]\"\n---\n\n# \u002Flegal-response -- Generate Response from Templates\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nGenerate 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.\n\n**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.\n\n## Invocation\n\n```\n\u002Flegal-response [inquiry-type]\n```\n\nCommon inquiry types:\n- `dsr` or `data-subject-request` -- Data subject access\u002Fdeletion\u002Fcorrection requests\n- `hold` or `discovery-hold` -- Litigation hold notices\n- `vendor` or `vendor-question` -- Vendor legal questions\n- `nda` or `nda-request` -- NDA requests from business teams\n- `privacy` or `privacy-inquiry` -- Privacy-related questions\n- `subpoena` -- Subpoena or legal process responses\n- `insurance` -- Insurance claim notifications\n- `custom` -- Use a custom template\n\nIf no inquiry type is provided, ask the user what type of response they need and show available categories.\n\n## Workflow\n\n### Step 1: Identify Inquiry Type\n\nAccept the inquiry type from the user. If the type is ambiguous, show available categories and ask for clarification.\n\n### Step 2: Load Template\n\nLook for templates in local settings (e.g., `legal.local.md` or a templates directory).\n\n**If templates are configured:**\n- Load the appropriate template for the inquiry type\n- Identify required variables (recipient name, dates, specific details)\n\n**If no templates are configured:**\n- Inform the user that no templates were found for this inquiry type\n- Offer to help create a template (see Template Creation Guide below)\n- Provide a reasonable default response structure based on the inquiry type\n\n### Step 3: Check Escalation Triggers\n\nBefore generating any response, evaluate whether this situation has characteristics that should NOT use a templated response.\n\n#### Universal Escalation Triggers (Apply to All Categories)\n- The matter involves potential litigation or regulatory investigation\n- The inquiry is from a regulator, government agency, or law enforcement\n- The response could create a binding legal commitment or waiver\n- The matter involves potential criminal liability\n- Media attention is involved or likely\n- The situation is unprecedented (no prior handling by the team)\n- Multiple jurisdictions are involved with conflicting requirements\n- The matter involves executive leadership or board members\n\n#### Data Subject Request Escalation Triggers\n- Request involves a minor's data, or is from\u002Fon behalf of a minor\n- Request is from a regulatory authority (not an individual)\n- Request involves data that is subject to a litigation hold\n- Requester is a current or former employee with an active dispute or HR matter\n- Request scope is unusually broad or appears to be a fishing expedition\n- Request involves data processed in a jurisdiction with unique requirements\n- Request involves special category data (health, biometric, genetic)\n\n#### Discovery Hold Escalation Triggers\n- The matter involves potential criminal liability\n- The preservation scope is unclear, disputed, or potentially overbroad\n- There are questions about whether certain data is within scope\n- Prior holds for the same or related matter exist\n- The hold may affect ongoing business operations significantly\n- Hold conflicts with regulatory deletion requirements\n- Custodian objects to the hold scope\n\n#### Vendor Question Escalation Triggers\n- The question involves a dispute or potential breach\n- The vendor is threatening litigation or termination\n- The question involves regulatory compliance (not just contract terms)\n- The response could create a binding commitment or waiver\n- Response could affect ongoing negotiation\n\n#### NDA Request Escalation Triggers\n- The counterparty is a competitor\n- The NDA involves government classified information\n- The business context suggests the NDA is for a potential M&A transaction\n- The request involves unusual subject matter (AI training data, biometric data, etc.)\n\n#### Subpoena \u002F Legal Process Escalation Triggers\n- **ALWAYS requires counsel review** (templates are starting points only)\n- Privilege issues identified\n- Third-party data involved\n- Cross-border production issues\n- Unreasonable timeline\n\n**When an escalation trigger is detected:**\n1. **Stop**: Do not generate a templated response\n2. **Alert**: Inform the user that an escalation trigger has been detected\n3. **Explain**: Describe which trigger was detected and why it matters\n4. **Recommend**: Suggest the appropriate escalation path (senior counsel, outside counsel, specific team member)\n5. **Offer**: Provide a draft for counsel review (clearly marked as \"DRAFT - FOR COUNSEL REVIEW ONLY\") rather than a final response\n\n### Step 4: Gather Specific Details\n\nPrompt the user for the details needed to customize the response:\n\n**Data Subject Request:**\n- Requester name and contact information\n- Type of request (access, deletion, correction, portability, opt-out)\n- What data is involved\n- Applicable regulation (GDPR, CCPA, CPRA, other)\n- Response deadline\n\n**Discovery Hold:**\n- Matter name and reference number\n- Custodians (who needs to preserve)\n- Scope of preservation (date range, data types, systems)\n- Outside counsel contact\n- Effective date\n\n**Vendor Question:**\n- Vendor name\n- Reference agreement (if applicable)\n- Specific question being addressed\n- Relevant contract provisions\n\n**NDA Request:**\n- Requesting business team and contact\n- Counterparty name\n- Purpose of the NDA\n- Mutual or unilateral\n- Any special requirements\n\n### Step 5: Generate Response\n\nPopulate the template with the gathered details. Ensure the response:\n- Uses appropriate tone (professional, clear, not overly legalistic for business audiences)\n- Includes all required legal elements for the response type\n- References specific dates, deadlines, and obligations\n- Provides clear next steps for the recipient\n- Includes appropriate disclaimers or caveats\n\nPresent the draft response to the user for review before sending.\n\n#### Customization Guidelines\n\n**Required customization** — Every templated response MUST be customized with:\n- Correct names, dates, and reference numbers\n- Specific facts of the situation\n- Applicable jurisdiction and regulation\n- Correct response deadlines based on when the inquiry was received\n- Appropriate signature block and contact information\n\n**Tone adjustment** — Adjust tone based on:\n- **Audience**: Internal vs. external, business vs. legal, individual vs. regulatory authority\n- **Relationship**: New counterparty vs. existing partner vs. adversarial party\n- **Sensitivity**: Routine inquiry vs. contentious matter vs. regulatory investigation\n- **Urgency**: Standard timeline vs. expedited response needed\n\n**Jurisdiction-specific adjustments:**\n- Verify that cited regulations are correct for the requester's jurisdiction\n- Adjust timelines to match applicable law\n- Include jurisdiction-specific rights information\n- Use jurisdiction-appropriate legal terminology\n\n### Step 6: Template Creation (If No Template Exists)\n\nIf 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.\n\n## Response Categories\n\n### 1. Data Subject Requests (DSRs)\n\n**Sub-categories**:\n- Acknowledgment of receipt\n- Identity verification request\n- Fulfillment response (access, deletion, correction)\n- Partial denial with explanation\n- Full denial with explanation\n- Extension notification\n\n**Key template elements**:\n- Reference to applicable regulation (GDPR, CCPA, etc.)\n- Specific timeline for response\n- Identity verification requirements\n- Rights of the data subject (including right to complain to supervisory authority)\n- Contact information for follow-up\n\n**Example template structure**:\n```\nSubject: Your Data [Access\u002FDeletion\u002FCorrection] Request - Reference {{request_id}}\n\nDear {{requester_name}},\n\nWe have received your request dated {{request_date}} to [access\u002Fdelete\u002Fcorrect] your personal data under [applicable regulation].\n\n[Acknowledgment \u002F verification request \u002F fulfillment details \u002F denial basis]\n\nWe will respond substantively by {{response_deadline}}.\n\n[Contact information]\n[Rights information]\n```\n\n### 2. Discovery Holds (Litigation Holds)\n\n**Sub-categories**:\n- Initial hold notice to custodians\n- Hold reminder \u002F periodic reaffirmation\n- Hold modification (scope change)\n- Hold release\n\n**Key template elements**:\n- Matter name and reference number\n- Clear preservation obligations\n- Scope of preservation (date range, data types, systems, communication types)\n- Prohibition on spoliation\n- Contact for questions\n- Acknowledgment requirement\n\n**Example template structure**:\n```\nSubject: LEGAL HOLD NOTICE - {{matter_name}} - Action Required\n\nPRIVILEGED AND CONFIDENTIAL\nATTORNEY-CLIENT COMMUNICATION\n\nDear {{custodian_name}},\n\nYou are receiving this notice because you may possess documents, communications, or data relevant to the matter referenced above.\n\nPRESERVATION OBLIGATION:\nEffective immediately, you must preserve all documents and electronically stored information (ESI) related to:\n- Subject matter: {{hold_scope}}\n- Date range: {{start_date}} to present\n- Document types: {{document_types}}\n\nDO NOT delete, destroy, modify, or discard any potentially relevant materials.\n\n[Specific instructions for systems, email, chat, local files]\n\nPlease acknowledge receipt of this notice by {{acknowledgment_deadline}}.\n\nContact {{legal_contact}} with any questions.\n```\n\n### 3. Privacy Inquiries\n\n**Sub-categories**:\n- Cookie\u002Ftracking inquiry responses\n- Privacy policy questions\n- Data sharing practice inquiries\n- Children's data inquiries\n- Cross-border transfer questions\n\n**Key template elements**:\n- Reference to the organization's privacy notice\n- Specific answers based on current practices\n- Links to relevant privacy documentation\n- Contact information for the privacy team\n\n### 4. Vendor Legal Questions\n\n**Sub-categories**:\n- Contract status inquiry response\n- Amendment request response\n- Compliance certification requests\n- Audit request responses\n- Insurance certificate requests\n\n**Key template elements**:\n- Reference to the applicable agreement\n- Specific response to the vendor's question\n- Any required caveats or limitations\n- Next steps and timeline\n\n### 5. NDA Requests\n\n**Sub-categories**:\n- Sending the organization's standard form NDA\n- Accepting a counterparty's NDA (with markup)\n- Declining an NDA request with explanation\n- NDA renewal or extension\n\n**Key template elements**:\n- Purpose of the NDA\n- Standard terms summary\n- Execution instructions\n- Timeline expectations\n\n### 6. Subpoena \u002F Legal Process\n\n**Sub-categories**:\n- Acknowledgment of receipt\n- Objection letter\n- Request for extension\n- Compliance cover letter\n\n**Key template elements**:\n- Case reference and jurisdiction\n- Specific objections (if any)\n- Preservation confirmation\n- Timeline for compliance\n- Privilege log reference (if applicable)\n\n**Critical note**: Subpoena responses almost always require individualized counsel review. Templates serve as starting frameworks, not final responses.\n\n### 7. Insurance Notifications\n\n**Sub-categories**:\n- Initial claim notification\n- Supplemental information\n- Reservation of rights response\n\n**Key template elements**:\n- Policy number and coverage period\n- Description of the matter or incident\n- Timeline of events\n- Requested coverage confirmation\n\n## Template Management Methodology\n\n### Template Organization\n\nTemplates should be organized by category and maintained in the team's local settings. Each template should include:\n\n1. **Category**: The type of inquiry the template addresses\n2. **Template name**: A descriptive identifier\n3. **Use case**: When this template is appropriate\n4. **Escalation triggers**: When this template should NOT be used\n5. **Required variables**: Information that must be customized for each use\n6. **Template body**: The response text with variable placeholders\n7. **Follow-up actions**: Standard steps after sending the response\n8. **Last reviewed date**: When the template was last verified for accuracy\n\n### Template Lifecycle\n\n1. **Creation**: Draft template based on best practices and team input\n2. **Review**: Legal team review and approval of template content\n3. **Publication**: Add to template library with metadata\n4. **Use**: Generate responses using the template\n5. **Feedback**: Track when templates are modified during use to identify improvement opportunities\n6. **Update**: Revise templates when laws, policies, or best practices change\n7. **Retirement**: Archive templates that are no longer applicable\n\n## Template Creation Guide\n\nWhen helping users create new templates:\n\n### 1. Define the Use Case\n- What type of inquiry does this address?\n- How frequently does this come up?\n- Who is the typical audience?\n- What is the typical urgency level?\n\n### 2. Identify Required Elements\n- What information must be included in every response?\n- What regulatory requirements apply?\n- What organizational policies govern this type of response?\n\n### 3. Define Variables\n- What changes with each use? (names, dates, specifics)\n- What stays the same? (legal requirements, standard language)\n- Use clear variable names: `{{requester_name}}`, `{{response_deadline}}`, `{{matter_reference}}`\n\n### 4. Draft the Template\n- Write in clear, professional language\n- Avoid unnecessary legal jargon for business audiences\n- Include all legally required elements\n- Add placeholders for all variable content\n- Include a subject line template if for email use\n\n### 5. Define Escalation Triggers\n- What situations should NOT use this template?\n- What characteristics indicate the matter needs individualized attention?\n- Be specific: vague triggers are not useful\n\n### 6. Add Metadata\n- Template name and category\n- Version number and last reviewed date\n- Author and approver\n- Follow-up actions checklist\n\n### Template Format\n\n```markdown\n## Template: {{template_name}}\n**Category**: {{category}}\n**Version**: {{version}} | **Last Reviewed**: {{date}}\n**Approved By**: {{approver}}\n\n### Use When\n- [Condition 1]\n- [Condition 2]\n\n### Do NOT Use When (Escalation Triggers)\n- [Trigger 1]\n- [Trigger 2]\n\n### Variables\n| Variable | Description | Example |\n|---|---|---|\n| {{var1}} | [what it is] | [example value] |\n| {{var2}} | [what it is] | [example value] |\n\n### Subject Line\n[Subject template with {{variables}}]\n\n### Body\n[Response body with {{variables}}]\n\n### Follow-Up Actions\n1. [Action 1]\n2. [Action 2]\n\n### Notes\n[Any special instructions for users of this template]\n```\n\n## Output Format\n\n```\n## Generated Response: [Inquiry Type]\n\n**To**: [recipient]\n**Subject**: [subject line]\n\n---\n\n[Response body]\n\n---\n\n### Escalation Check\n[Confirmation that no escalation triggers were detected, OR flagged triggers with recommendations]\n\n### Follow-Up Actions\n1. [Post-send actions]\n2. [Calendar reminders to set]\n3. [Tracking or logging requirements]\n```\n\n## Notes\n\n- Always present the draft response for user review before suggesting it be sent\n- If connected to email via MCP, offer to create a draft email with the response\n- Track response deadlines and offer to set calendar reminders\n- For regulated responses (DSRs, subpoenas), always note the applicable deadline and regulatory requirements\n- Templates should be living documents; suggest updates when the user modifies a templated response, so the template can be improved over time\n","# \u002Flegal-response -- Generate Response from Templates\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nGenerate 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.\n\n**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.\n\n## Invocation\n\n```\n\u002Flegal-response [inquiry-type]\n```\n\nCommon inquiry types:\n- `dsr` or `data-subject-request` -- Data subject access\u002Fdeletion\u002Fcorrection requests\n- `hold` or `discovery-hold` -- Litigation hold notices\n- `vendor` or `vendor-question` -- Vendor legal questions\n- `nda` or `nda-request` -- NDA requests from business teams\n- `privacy` or `privacy-inquiry` -- Privacy-related questions\n- `subpoena` -- Subpoena or legal process responses\n- `insurance` -- Insurance claim notifications\n- `custom` -- Use a custom template\n\nIf no inquiry type is provided, ask the user what type of response they need and show available categories.\n\n## Workflow\n\n### Step 1: Identify Inquiry Type\n\nAccept the inquiry type from the user. If the type is ambiguous, show available categories and ask for clarification.\n\n### Step 2: Load Template\n\nLook for templates in local settings (e.g., `legal.local.md` or a templates directory).\n\n**If templates are configured:**\n- Load the appropriate template for the inquiry type\n- Identify required variables (recipient name, dates, specific details)\n\n**If no templates are configured:**\n- Inform the user that no templates were found for this inquiry type\n- Offer to help create a template (see Template Creation Guide below)\n- Provide a reasonable default response structure based on the inquiry type\n\n### Step 3: Check Escalation Triggers\n\nBefore generating any response, evaluate whether this situation has characteristics that should NOT use a templated response.\n\n#### Universal Escalation Triggers (Apply to All Categories)\n- The matter involves potential litigation or regulatory investigation\n- The inquiry is from a regulator, government agency, or law enforcement\n- The response could create a binding legal commitment or waiver\n- The matter involves potential criminal liability\n- Media attention is involved or likely\n- The situation is unprecedented (no prior handling by the team)\n- Multiple jurisdictions are involved with conflicting requirements\n- The matter involves executive leadership or board members\n\n#### Data Subject Request Escalation Triggers\n- Request involves a minor's data, or is from\u002Fon behalf of a minor\n- Request is from a regulatory authority (not an individual)\n- Request involves data that is subject to a litigation hold\n- Requester is a current or former employee with an active dispute or HR matter\n- Request scope is unusually broad or appears to be a fishing expedition\n- Request involves data processed in a jurisdiction with unique requirements\n- Request involves special category data (health, biometric, genetic)\n\n#### Discovery Hold Escalation Triggers\n- The matter involves potential criminal liability\n- The preservation scope is unclear, disputed, or potentially overbroad\n- There are questions about whether certain data is within scope\n- Prior holds for the same or related matter exist\n- The hold may affect ongoing business operations significantly\n- Hold conflicts with regulatory deletion requirements\n- Custodian objects to the hold scope\n\n#### Vendor Question Escalation Triggers\n- The question involves a dispute or potential breach\n- The vendor is threatening litigation or termination\n- The question involves regulatory compliance (not just contract terms)\n- The response could create a binding commitment or waiver\n- Response could affect ongoing negotiation\n\n#### NDA Request Escalation Triggers\n- The counterparty is a competitor\n- The NDA involves government classified information\n- The business context suggests the NDA is for a potential M&A transaction\n- The request involves unusual subject matter (AI training data, biometric data, etc.)\n\n#### Subpoena \u002F Legal Process Escalation Triggers\n- **ALWAYS requires counsel review** (templates are starting points only)\n- Privilege issues identified\n- Third-party data involved\n- Cross-border production issues\n- Unreasonable timeline\n\n**When an escalation trigger is detected:**\n1. **Stop**: Do not generate a templated response\n2. **Alert**: Inform the user that an escalation trigger has been detected\n3. **Explain**: Describe which trigger was detected and why it matters\n4. **Recommend**: Suggest the appropriate escalation path (senior counsel, outside counsel, specific team member)\n5. **Offer**: Provide a draft for counsel review (clearly marked as \"DRAFT - FOR COUNSEL REVIEW ONLY\") rather than a final response\n\n### Step 4: Gather Specific Details\n\nPrompt the user for the details needed to customize the response:\n\n**Data Subject Request:**\n- Requester name and contact information\n- Type of request (access, deletion, correction, portability, opt-out)\n- What data is involved\n- Applicable regulation (GDPR, CCPA, CPRA, other)\n- Response deadline\n\n**Discovery Hold:**\n- Matter name and reference number\n- Custodians (who needs to preserve)\n- Scope of preservation (date range, data types, systems)\n- Outside counsel contact\n- Effective date\n\n**Vendor Question:**\n- Vendor name\n- Reference agreement (if applicable)\n- Specific question being addressed\n- Relevant contract provisions\n\n**NDA Request:**\n- Requesting business team and contact\n- Counterparty name\n- Purpose of the NDA\n- Mutual or unilateral\n- Any special requirements\n\n### Step 5: Generate Response\n\nPopulate the template with the gathered details. Ensure the response:\n- Uses appropriate tone (professional, clear, not overly legalistic for business audiences)\n- Includes all required legal elements for the response type\n- References specific dates, deadlines, and obligations\n- Provides clear next steps for the recipient\n- Includes appropriate disclaimers or caveats\n\nPresent the draft response to the user for review before sending.\n\n#### Customization Guidelines\n\n**Required customization** — Every templated response MUST be customized with:\n- Correct names, dates, and reference numbers\n- Specific facts of the situation\n- Applicable jurisdiction and regulation\n- Correct response deadlines based on when the inquiry was received\n- Appropriate signature block and contact information\n\n**Tone adjustment** — Adjust tone based on:\n- **Audience**: Internal vs. external, business vs. legal, individual vs. regulatory authority\n- **Relationship**: New counterparty vs. existing partner vs. adversarial party\n- **Sensitivity**: Routine inquiry vs. contentious matter vs. regulatory investigation\n- **Urgency**: Standard timeline vs. expedited response needed\n\n**Jurisdiction-specific adjustments:**\n- Verify that cited regulations are correct for the requester's jurisdiction\n- Adjust timelines to match applicable law\n- Include jurisdiction-specific rights information\n- Use jurisdiction-appropriate legal terminology\n\n### Step 6: Template Creation (If No Template Exists)\n\nIf 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.\n\n## Response Categories\n\n### 1. Data Subject Requests (DSRs)\n\n**Sub-categories**:\n- Acknowledgment of receipt\n- Identity verification request\n- Fulfillment response (access, deletion, correction)\n- Partial denial with explanation\n- Full denial with explanation\n- Extension notification\n\n**Key template elements**:\n- Reference to applicable regulation (GDPR, CCPA, etc.)\n- Specific timeline for response\n- Identity verification requirements\n- Rights of the data subject (including right to complain to supervisory authority)\n- Contact information for follow-up\n\n**Example template structure**:\n```\nSubject: Your Data [Access\u002FDeletion\u002FCorrection] Request - Reference {{request_id}}\n\nDear {{requester_name}},\n\nWe have received your request dated {{request_date}} to [access\u002Fdelete\u002Fcorrect] your personal data under [applicable regulation].\n\n[Acknowledgment \u002F verification request \u002F fulfillment details \u002F denial basis]\n\nWe will respond substantively by {{response_deadline}}.\n\n[Contact information]\n[Rights information]\n```\n\n### 2. Discovery Holds (Litigation Holds)\n\n**Sub-categories**:\n- Initial hold notice to custodians\n- Hold reminder \u002F periodic reaffirmation\n- Hold modification (scope change)\n- Hold release\n\n**Key template elements**:\n- Matter name and reference number\n- Clear preservation obligations\n- Scope of preservation (date range, data types, systems, communication types)\n- Prohibition on spoliation\n- Contact for questions\n- Acknowledgment requirement\n\n**Example template structure**:\n```\nSubject: LEGAL HOLD NOTICE - {{matter_name}} - Action Required\n\nPRIVILEGED AND CONFIDENTIAL\nATTORNEY-CLIENT COMMUNICATION\n\nDear {{custodian_name}},\n\nYou are receiving this notice because you may possess documents, communications, or data relevant to the matter referenced above.\n\nPRESERVATION OBLIGATION:\nEffective immediately, you must preserve all documents and electronically stored information (ESI) related to:\n- Subject matter: {{hold_scope}}\n- Date range: {{start_date}} to present\n- Document types: {{document_types}}\n\nDO NOT delete, destroy, modify, or discard any potentially relevant materials.\n\n[Specific instructions for systems, email, chat, local files]\n\nPlease acknowledge receipt of this notice by {{acknowledgment_deadline}}.\n\nContact {{legal_contact}} with any questions.\n```\n\n### 3. Privacy Inquiries\n\n**Sub-categories**:\n- Cookie\u002Ftracking inquiry responses\n- Privacy policy questions\n- Data sharing practice inquiries\n- Children's data inquiries\n- Cross-border transfer questions\n\n**Key template elements**:\n- Reference to the organization's privacy notice\n- Specific answers based on current practices\n- Links to relevant privacy documentation\n- Contact information for the privacy team\n\n### 4. Vendor Legal Questions\n\n**Sub-categories**:\n- Contract status inquiry response\n- Amendment request response\n- Compliance certification requests\n- Audit request responses\n- Insurance certificate requests\n\n**Key template elements**:\n- Reference to the applicable agreement\n- Specific response to the vendor's question\n- Any required caveats or limitations\n- Next steps and timeline\n\n### 5. NDA Requests\n\n**Sub-categories**:\n- Sending the organization's standard form NDA\n- Accepting a counterparty's NDA (with markup)\n- Declining an NDA request with explanation\n- NDA renewal or extension\n\n**Key template elements**:\n- Purpose of the NDA\n- Standard terms summary\n- Execution instructions\n- Timeline expectations\n\n### 6. Subpoena \u002F Legal Process\n\n**Sub-categories**:\n- Acknowledgment of receipt\n- Objection letter\n- Request for extension\n- Compliance cover letter\n\n**Key template elements**:\n- Case reference and jurisdiction\n- Specific objections (if any)\n- Preservation confirmation\n- Timeline for compliance\n- Privilege log reference (if applicable)\n\n**Critical note**: Subpoena responses almost always require individualized counsel review. Templates serve as starting frameworks, not final responses.\n\n### 7. Insurance Notifications\n\n**Sub-categories**:\n- Initial claim notification\n- Supplemental information\n- Reservation of rights response\n\n**Key template elements**:\n- Policy number and coverage period\n- Description of the matter or incident\n- Timeline of events\n- Requested coverage confirmation\n\n## Template Management Methodology\n\n### Template Organization\n\nTemplates should be organized by category and maintained in the team's local settings. Each template should include:\n\n1. **Category**: The type of inquiry the template addresses\n2. **Template name**: A descriptive identifier\n3. **Use case**: When this template is appropriate\n4. **Escalation triggers**: When this template should NOT be used\n5. **Required variables**: Information that must be customized for each use\n6. **Template body**: The response text with variable placeholders\n7. **Follow-up actions**: Standard steps after sending the response\n8. **Last reviewed date**: When the template was last verified for accuracy\n\n### Template Lifecycle\n\n1. **Creation**: Draft template based on best practices and team input\n2. **Review**: Legal team review and approval of template content\n3. **Publication**: Add to template library with metadata\n4. **Use**: Generate responses using the template\n5. **Feedback**: Track when templates are modified during use to identify improvement opportunities\n6. **Update**: Revise templates when laws, policies, or best practices change\n7. **Retirement**: Archive templates that are no longer applicable\n\n## Template Creation Guide\n\nWhen helping users create new templates:\n\n### 1. Define the Use Case\n- What type of inquiry does this address?\n- How frequently does this come up?\n- Who is the typical audience?\n- What is the typical urgency level?\n\n### 2. Identify Required Elements\n- What information must be included in every response?\n- What regulatory requirements apply?\n- What organizational policies govern this type of response?\n\n### 3. Define Variables\n- What changes with each use? (names, dates, specifics)\n- What stays the same? (legal requirements, standard language)\n- Use clear variable names: `{{requester_name}}`, `{{response_deadline}}`, `{{matter_reference}}`\n\n### 4. Draft the Template\n- Write in clear, professional language\n- Avoid unnecessary legal jargon for business audiences\n- Include all legally required elements\n- Add placeholders for all variable content\n- Include a subject line template if for email use\n\n### 5. Define Escalation Triggers\n- What situations should NOT use this template?\n- What characteristics indicate the matter needs individualized attention?\n- Be specific: vague triggers are not useful\n\n### 6. Add Metadata\n- Template name and category\n- Version number and last reviewed date\n- Author and approver\n- Follow-up actions checklist\n\n### Template Format\n\n```markdown\n## Template: {{template_name}}\n**Category**: {{category}}\n**Version**: {{version}} | **Last Reviewed**: {{date}}\n**Approved By**: {{approver}}\n\n### Use When\n- [Condition 1]\n- [Condition 2]\n\n### Do NOT Use When (Escalation Triggers)\n- [Trigger 1]\n- [Trigger 2]\n\n### Variables\n| Variable | Description | Example |\n|---|---|---|\n| {{var1}} | [what it is] | [example value] |\n| {{var2}} | [what it is] | [example value] |\n\n### Subject Line\n[Subject template with {{variables}}]\n\n### Body\n[Response body with {{variables}}]\n\n### Follow-Up Actions\n1. [Action 1]\n2. [Action 2]\n\n### Notes\n[Any special instructions for users of this template]\n```\n\n## Output Format\n\n```\n## Generated Response: [Inquiry Type]\n\n**To**: [recipient]\n**Subject**: [subject line]\n\n---\n\n[Response body]\n\n---\n\n### Escalation Check\n[Confirmation that no escalation triggers were detected, OR flagged triggers with recommendations]\n\n### Follow-Up Actions\n1. [Post-send actions]\n2. [Calendar reminders to set]\n3. [Tracking or logging requirements]\n```\n\n## Notes\n\n- Always present the draft response for user review before suggesting it be sent\n- If connected to email via MCP, offer to create a draft email with the response\n- Track response deadlines and offer to set calendar reminders\n- For regulated responses (DSRs, subpoenas), always note the applicable deadline and regulatory requirements\n- Templates should be living documents; suggest updates when the user modifies a templated response, so the template can be improved over time\n",{"name":5,"description":7,"argument-hint":49},"[inquiry-type]","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","legal\u002Fskills\u002Flegal-response",3944,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-14 06:21:52",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill legal-response",{"tool":64,"command":65},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill legal-response",{"tool":67,"command":68},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill legal-response","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Flegal\u002Fskills\u002Flegal-response\u002FSKILL.md",true,[],[73,99,124,145,172,198],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":44},"01M718Y97HCGW12Q53PSJDY03W","ticket-deflector","Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says \"draft a response,\" \"answer this customer,\" \"where's my order,\" \"I want a refund,\" \"check my orders,\" or \"anything about to blow up.\"","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fticket-deflector\u002FSKILL.md",[],[80,81,82,83,84,85,86,41,87,88,89,90,91,92,93,94,95,96,97,98],"ticket","ticket deflector","mode","up","payments","open","writing","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past","read",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":44},"01M718Y55HFAN5705ME5VEDZ9K","tax-season-organizer","Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags.\nAny tax request routes first to \u002Ftax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: \"books are closed, now do the 1099s,\" \"run the quarterly estimate off the closed numbers,\" or \"just the contractor W-9 list.\"","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Ftax-season-organizer\u002FSKILL.md",[],[106,107,108,109,110,111,112,113,114,115,41,116,117,118,119,120,98,121,122,123],"tax season organizer","tax","us federal","which","netsuite","paid","end","usd","only","now","books","xero","scanning","run","request","flags","list","stripe",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":44},"01M718Y13VVPHDD9NTDBVFJ2AZ","tax-prep","Prepares tax materials as a two-link chain — month-end-prep confirms the books are closed and reconciled first, then tax-season-organizer calculates the quarterly estimated payment or builds the year-end 1099-NEC list and accountant packet from those closed numbers. Requires a ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); uses Gusto, PayPal, and Stripe when connected, else CSV upload. US federal tax math; a non-US business gets the closed-books packet. Prep material for a CPA, never tax advice, nothing filed. Trigger on \"quarterly taxes,\" \"estimated tax payment,\" \"how much should I set aside,\" \"1099s,\" \"1099-NEC,\" \"W-9s,\" \"year-end tax prep,\" \"get my books ready for my accountant,\" any phrasing that suggests a tax deadline is coming, or a question about net profit or YTD income that sounds like worry about a tax bill. An owner who says the period's books are already closed routes to tax-season-organizer directly.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Ftax-prep\u002FSKILL.md",[],[131,107,132,133,108,134,135,110,136,137,138,139,140,36,141,112,142,143,144,33],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","trigger","material","question","paypal",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":154,"publishedAt":44},"01M718XWTWQZ01GYSG9T8RW8TW","speed-to-lead","Makes sure no inbound lead goes unanswered. Watches web forms, the shared inbox, and the CRM for new inquiries, qualifies each one against the owner's criteria, drafts a reply in the owner's voice with real meeting times for the owner to approve and send, routes anything hot to a human right away, and logs the whole thing to the CRM. Never sends on its own. Built to run on a schedule so overnight inquiries are drafted and sorted by morning, and works from forwarded or pasted inquiries when no connector is available. Use this whenever the owner is worried about inbound leads or response time — including phrasings like \"leads are going cold,\" \"did anyone answer that inquiry,\" \"I keep missing form submissions,\" \"nothing falls through the cracks,\" \"handle my inbound,\" \"respond to this lead,\" or \"we lose people because nobody gets back fast enough.\" Reach for it for a single unanswered inquiry as readily as for a standing setup.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fspeed-to-lead\u002FSKILL.md",[151],{"categoryNo":152,"categoryName":153,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员",[155,156,157,158,159,160,136,161,162,163,164,165,166,167,41,168,169,89,170,171],"speed to lead","lead","speed","shared","back","cold","time","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":181,"publishedAt":44},"01M718XQYMN1KY3TPS33967FK0","social-content-engine","Runs the owner's content operation as a standing thing rather than a one-off: keeps a rolling posting calendar, learns the owner's voice, generates on-brand Canva graphics, writes captions that sound like them, repurposes one asset into every channel format, and stages posts for approval instead of publishing on its own. Pulls product photos and prices from Shopify when connected; with no connectors, drafts the calendar and asset briefs for manual posting. Use this whenever the owner talks about posting, content, or social — including \"I need to post more,\" \"we've gone quiet on Instagram,\" \"what should we post this month,\" \"make the content,\" \"give me a month of posts,\" \"write this in my voice,\" \"repurpose this,\" or \"set up our content calendar.\" Reach for it for a single post as readily as for a full quarter. One handoff: a finished, approved campaign brief goes to canva-creator; this skill owns the standing operation.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fsocial-content-engine\u002FSKILL.md",[178],{"categoryNo":179,"categoryName":180,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[182,183,184,185,186,187,133,188,189,190,191,83,192,41,193,194,195,98,196,197],"social","social content engine","engine","content engine","social content","content","brief","posts","Captions","prices","campaign","me","product","calendar","write","drafts",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":44},"01M718XMPJVH0EVRVP998BVZPC","smb-router","The front door to the Small Business plugin. Listens to what the owner needs right now — vague or specific — and routes them to the best skill or slash command for the moment. Also serves as a guide: explains what's available, suggests what to try next, and adapts recommendations based on stored business context. Trigger whenever the owner asks \"what can you do,\" \"help me with my business,\" \"what should I focus on,\" \"I don't know where to start,\" or any open-ended business request that doesn't clearly match a single skill.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fsmb-router\u002FSKILL.md",[],[205,206,207,134,208,36,141,209,85,210,115,33,211,212,213,31,214,193,215,93],"router","smb","smb router","do","front","single","you","vague","can","plugin","focus"]