Token导航 LogoToken导航

Agent Skill · 研究检索

legal-canned-responses(合法的预设回复)

legal-canned-responses 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

legal-canned-responses 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 56,028。

总安装 465周安装 19GitHub Stars 103下载 150核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:legal-canned-responses(合法的预设回复)
来源仓库:https://github.com/borghei/claude-skills
仓库路径:skills/legal-canned-responses
安装命令:
npx skills add https://github.com/borghei/claude-skills --skill legal-canned-responses
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill legal-canned-responses

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

legal-canned-responses 用于法律预设回复的查找与筛选,适合快速匹配常见法律场景回应模板。支持基于关键词或任务类型定位候选回复,适用于客服、咨询等标准化应答场景。通过 npx skills add 命令从 GitHub 仓库安装,需确认权限与维护状态。

建议在使用前核实是否涉及敏感信息处理或外部调用,确保合规性。可结合原始文档了解具体回复库内容与调用方式。

来源仓库内路径:skills/legal-canned-responses

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/borghei/claude-skills --skill legal-canned-res…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

legal-canned-responses 怎么安装?

在终端执行 npx skills add https://github.com/borghei/claude-skills --skill legal-canned-responses。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

legal-canned-responses 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

legal-canned-responses 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

legal-canned-responses 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

legal-canned-responses 用的人多吗?

公开数据是累计安装 465 次,近一周安装 19 次,下载 150 次,GitHub 103 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

legal-canned-responses 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
legal-canned-responses

合法的预设回复 · 本页

465103只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

⚠️ 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

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 "A reporter from the Wall Street Journal is asking about our data practices" --json

python scripts/escalation_detector.py \
  --category vendor \
  --text "The vendor is threatening litigation over the contract dispute"

Reference Guides

ReferencePurpose
references/response_templates.mdComplete templates for all 7 categories with sub-types
references/escalation_triggers.mdUniversal and category-specific escalation triggers

Workflows

Template Lifecycle

  1. Creation -- Draft response template for identified recurring inquiry type
  2. Review -- Legal counsel reviews template for accuracy, tone, and compliance
  3. Publication -- Template added to system with metadata, variables, and triggers
  4. Use -- Staff selects category/sub-type, fills variables, generates response
  5. Feedback -- Track usage and collect feedback on template effectiveness
  6. Update -- Revise templates based on feedback, legal changes, or policy updates
  7. Retirement -- Archive templates that are no longer applicable

Response Generation Workflow

  1. Classify Inquiry -- Determine category (DSR, NDA, subpoena, etc.) and sub-type
  2. Check Escalation -- Run escalation detector on inquiry text
  3. If Escalation Detected -- Stop; route to counsel with escalation report
  4. If No Escalation -- Generate response with appropriate template and variables
  5. Review & Send -- Review generated response before sending; adjust if needed

Response Categories

CategorySub-TypesDescription
Data Subject Requests (DSR)acknowledgment, verification, fulfillment, denial, extensionGDPR/CCPA data subject right requests
Discovery/Litigation Holdsinitial-notice, reminder, modification, releaseLitigation hold management
Privacy Inquiriescookies, data-sharing, children, transfersGeneral privacy questions
Vendor Legal Questionscontract-status, amendments, certifications, auditVendor/supplier legal matters
NDA Requestsstandard-form, counterparty-markup, decline, renewalNon-disclosure agreement lifecycle
Subpoena/Legal Processacknowledgment, objection, extension, complianceLegal process responses
Insurance Notificationsinitial-claim, supplemental-info, reservation-of-rightsInsurance claim management

DSR Sub-Types

Sub-TypeUse WhenKey Variables
acknowledgmentNew DSR receivedrequestor_name, request_type, request_date
verificationIdentity verification neededrequestor_name, verification_method
fulfillmentRequest completedrequestor_name, request_type, data_description
denialRequest denied with reasonrequestor_name, request_type, denial_reason
extensionNeed more timerequestor_name, request_type, extension_reason, new_deadline

Discovery/Litigation Hold Sub-Types

Sub-TypeUse WhenKey Variables
initial-noticeNew litigation hold issuedmatter_name, custodians, data_types
reminderPeriodic hold remindermatter_name, reminder_number
modificationHold scope changedmatter_name, modification_description
releaseHold liftedmatter_name, release_date

Escalation System

Universal Triggers (Always Escalate)

#TriggerWhy
1Potential or active litigationLegal exposure requires counsel assessment
2Regulatory investigation or inquiryRegulatory response requires strategic approach
3Government or law enforcement contactConstitutional and procedural rights at stake
4Binding legal commitment requestedCannot create legal obligations without counsel
5Criminal liability exposureRequires immediate counsel involvement
6Media attention or press inquiryReputational risk requires coordinated response
7Unprecedented or novel situationNo template exists; bespoke legal analysis needed
8Multi-jurisdictional conflictCross-border legal complexity requires expert analysis

Escalation Response Protocol

  1. Stop -- Do not send any templated response
  2. Alert -- Notify designated counsel immediately
  3. Explain -- Provide escalation context with matched triggers
  4. Recommend -- Suggest routing based on trigger type
  5. Draft -- Mark any preliminary draft "FOR COUNSEL REVIEW ONLY"

Troubleshooting

ProblemCauseSolution
Missing variable in outputRequired variable not providedCheck template requirements; provide all required --var parameters
Wrong template selectedCategory/sub-type mismatchReview category descriptions; ensure sub-type matches inquiry type
False positive escalationCommon words matching trigger patternsProvide --category to use category-specific triggers; review matched triggers
False negative escalationInquiry text too vagueAdd more context to inquiry text; run both universal and category-specific checks
Template too genericUsing default valuesReplace all placeholder values with actual organization-specific details
Discovery hold sent to wrong custodiansCustodian list outdatedVerify custodian list against current employees and systems
Subpoena response not flaggedMissing category contextAlways use --category subpoena for legal process; subpoena category always escalates
Response tone inappropriateWrong audience contextSelect appropriate sub-type; customize tone per audience

Success Criteria

  • Response Time: Templated responses generated within 5 minutes vs. 30+ minutes manual drafting
  • Escalation Accuracy: 100% of genuine escalation triggers detected (zero false negatives on CRITICAL triggers)
  • Template Coverage: Templates cover 80%+ of recurring legal inquiry types
  • Consistency: All responses within a category use consistent language, tone, and legal caveats
  • Audit Trail: Every generated response logged with category, sub-type, date, and escalation status

Scope & Limitations

This skill covers:

  • Template-based response generation for 7 common legal inquiry categories
  • Escalation detection using keyword and pattern matching against known triggers
  • Variable substitution for organization-specific customization
  • Response metadata generation for audit trail purposes

This skill does NOT cover:

  • Legal advice or attorney-client privileged analysis
  • Automated sending of responses (generation only; human review required)
  • Contract drafting, negotiation, or legal document creation
  • Case management, docketing, or deadline tracking
  • Jurisdiction-specific legal compliance validation of response content

Anti-Patterns

Anti-PatternWhy It FailsBetter Approach
Sending templated response without reviewMay miss context-specific nuances; legal riskAlways review generated response before sending
Ignoring escalation triggersCritical matters mishandled; legal exposureRun escalation detector on every inquiry; treat all triggers seriously
Using templates for novel situationsTemplates assume standard scenarios; novel situations need bespoke analysisEscalate novel situations to counsel; create new template after resolution
Hardcoding organization details in templatesTemplates become non-portable; updates missedUse variable substitution; maintain variables in configuration
Skipping identity verification for DSRsGDPR/CCPA require verification before fulfillmentAlways send verification sub-type before fulfillment

Tool Reference

scripts/response_generator.py

Generate formatted legal responses with variable substitution.

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

scripts/escalation_detector.py

Analyze inquiry text for escalation triggers.

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

平台分布

Codex

36.57%
按下载量换算55

Claude

30.08%
按下载量换算45

Cursor

17.06%
按下载量换算26

Gemini CLI

8.45%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills