brief by anthropics/knowledge-work-plugins
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill brief如果您看到不熟悉的占位符或需要检查已连接的工具,请参阅 CONNECTORS.md。
为法律工作生成上下文简报。支持三种模式:每日简报、专题简报和事件简报。
重要提示:此命令协助法律工作流程,但不提供法律建议。简报在依赖使用前应由合格的法律专业人士审阅。
/brief daily # 法律相关事项的晨间简报
/brief topic [query] # 针对特定法律问题的研究简报
/brief incident [topic] # 针对发展中的情况的快速简报
如果未指定模式,则询问用户需要哪种类型的简报。
法律团队成员开始一天工作所需了解的所有事项的晨间摘要。
检查每个已连接的来源以获取法律相关事项:
电子邮件(如果已连接):
日历(如果已连接):
聊天(如果已连接):
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
合同生命周期管理(如果已连接):
客户关系管理(如果已连接):
## 每日法律简报 -- [日期]
### 紧急 / 需要行动
[需要立即关注的事项,按紧急程度排序]
### 合同管道
- **等待您审查**:[数量和列表]
- **等待对方回复**:[数量和列表]
- **即将截止**:[本周到期的事项]
### 新请求
[自上次简报以来收到的合同审查请求、保密协议请求、合规性问题]
### 今日日历
[具有法律相关性的会议以及需要做的准备]
### 团队动态
[来自法律团队频道的关键消息或更新]
### 本周截止日期
[即将到来的截止日期和申报日期]
### 不可用的来源
[任何未连接或返回错误的来源]
针对特定法律问题或主题,跨可用来源进行研究和简报。
## 专题简报:[主题]
### 摘要
[2-3句的执行摘要,概述发现]
### 背景
[来自内部来源的背景和历史信息]
### 当前状态
[根据可用文档,组织当前的立场或方法是什么]
### 关键考虑因素
[重要因素、风险或未决问题]
### 内部先例
[在内部来源中找到的先前决定、备忘录或立场]
### 信息缺口
[缺少哪些信息或哪些来源不可用]
### 建议后续步骤
[用户应如何处理这些信息]
针对需要立即法律关注的发展中情况(数据泄露、诉讼威胁、监管调查、知识产权纠纷等)的快速简报。
## 事件简报:[主题]
**准备时间**:[时间戳]
**分类**:[如果可确定,则为严重性评估]
### 情况摘要
[关于该事件已知的信息]
### 时间线
[根据可用来源按时间顺序总结的事件]
### 立即的法律考虑因素
[监管通知要求、证据保全义务、特权问题]
### 相关协议
[可能涉及的合同、保险单或其他协议]
### 内部响应
[根据电子邮件/聊天,已经发生了哪些响应活动]
### 关键联系人
[从来源中识别出的相关内部和外部联系人]
### 建议立即采取的行动
1. [最紧急的行动]
2. [第二优先级]
3. [等等...]
### 信息缺口
[尚不清楚且需要确定的信息]
### 已检查的来源
[搜索了哪些内容以及哪些内容不可用]
每周安装量
192
代码仓库
GitHub 星标数
10.3K
首次出现
11 天前
安全审计
安装于
gemini-cli183
opencode183
codex182
cursor182
kimi-cli181
github-copilot181
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate contextual briefings for legal work. Supports three modes: daily brief, topic brief, and incident brief.
Important : This command assists with legal workflows but does not provide legal advice. Briefings should be reviewed by qualified legal professionals before being relied upon.
/brief daily # Morning brief of legal-relevant items
/brief topic [query] # Research brief on a specific legal question
/brief incident [topic] # Rapid brief on a developing situation
If no mode is specified, ask the user which type of brief they need.
A morning summary of everything a legal team member needs to know to start their day.
Check each connected source for legal-relevant items:
Email (if connected):
Calendar (if connected):
Chat (if connected):
CLM (if connected):
CRM (if connected):
## Daily Legal Brief -- [Date]
### Urgent / Action Required
[Items needing immediate attention, sorted by urgency]
### Contract Pipeline
- **Awaiting Your Review**: [count and list]
- **Pending Counterparty Response**: [count and list]
- **Approaching Deadlines**: [items due this week]
### New Requests
[Contract review requests, NDA requests, compliance questions received since last brief]
### Calendar Today
[Meetings with legal relevance and what prep is needed]
### Team Activity
[Key messages or updates from legal team channels]
### This Week's Deadlines
[Upcoming deadlines and filing dates]
### Sources Not Available
[Any sources that were not connected or returned errors]
Research and brief on a specific legal question or topic across available sources.
## Topic Brief: [Topic]
### Summary
[2-3 sentence executive summary of findings]
### Background
[Context and history from internal sources]
### Current State
[What the organization's current position or approach is, based on available documents]
### Key Considerations
[Important factors, risks, or open questions]
### Internal Precedent
[Prior decisions, memos, or positions found in internal sources]
### Gaps
[What information is missing or what sources were not available]
### Recommended Next Steps
[What the user should do with this information]
Rapid briefing for developing situations that require immediate legal attention (data breaches, litigation threats, regulatory inquiries, IP disputes, etc.).
## Incident Brief: [Topic]
**Prepared**: [timestamp]
**Classification**: [severity assessment if determinable]
### Situation Summary
[What is known about the incident]
### Timeline
[Chronological summary of events based on available sources]
### Immediate Legal Considerations
[Regulatory notification requirements, preservation obligations, privilege concerns]
### Relevant Agreements
[Contracts, insurance policies, or other agreements that may be implicated]
### Internal Response
[What response activity has already occurred based on email/chat]
### Key Contacts
[Relevant internal and external contacts identified from sources]
### Recommended Immediate Actions
1. [Most urgent action]
2. [Second priority]
3. [etc.]
### Information Gaps
[What is not yet known and needs to be determined]
### Sources Checked
[What was searched and what was not available]
Weekly Installs
192
Repository
GitHub Stars
10.3K
First Seen
11 days ago
Security Audits
Gen Agent Trust HubPassSocketWarnSnykPass
Installed on
gemini-cli183
opencode183
codex182
cursor182
kimi-cli181
github-copilot181
通过 LiteLLM 代理让 Claude Code 对接 GitHub Copilot 运行 | 高级变通方案指南
31,600 周安装