Brief
Generate legal-team daily, topic, or incident briefings by scanning connected email, calendar, and internal sources—always for human attorney review.
Overview
brief is an agent skill most often used in Operate monitoring (also Validate scoping for topic research) that produces legal-context briefings in daily, topic, or incident modes for professional review.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill briefWhat is this skill?
- Three modes: daily morning brief, topic research brief, and incident rapid brief
- Scans connected email and calendar for contracts, compliance threads, and review requests
- Invocation patterns: `/brief daily`, `/brief topic <query>`, `/brief incident <topic>`
- Explicit disclaimer: assists workflows but does not provide legal advice
- Prompts for mode when unspecified instead of guessing intent
- 3 briefing modes: daily, topic, and incident
Adoption & trust: 1.4k installs on skills.sh; 19.6k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Legal-relevant signal is scattered across email and calendar and you need a fast, structured scan before counsel can act.
Who is it for?
Startup operators with legal connectors who need repeatable morning scans or incident context packets inside their agent environment.
Skip if: Solo indie builders without legal mail or calendar integrations seeking automated legal opinions or consumer-grade Q&A.
When should I use this skill?
User runs `/brief` with daily, topic, or incident mode—or asks for a legal morning scan, topic research brief, or rapid incident context.
What do I get? / Deliverables
You receive a mode-appropriate legal briefing draft from connected sources, ready for qualified attorney review—not final legal advice.
- Daily legal-relevant summary brief
- Topic research brief for a stated query
- Incident rapid-context brief for a developing situation
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Operate monitoring is the canonical shelf for ongoing legal-relevant signal and emerging incidents while the business runs. Monitoring fits recurring daily scans and rapid incident context assembly—not initial idea research or product build tasks.
Where it fits
Run `/brief daily` to surface overnight contract review requests before standup.
Run `/brief incident data breach` to aggregate developing threads for counsel.
Run `/brief topic` on a policy question before committing product scope.
Use incident mode when a regulatory inquiry lands during launch week.
How it compares
Workflow briefing skill over connected workspaces—not a replacement for outside counsel or a dedicated GRC platform.
Common Questions / FAQ
Who is brief for?
Founders and ops leads on small teams who monitor contracts and compliance via connected email and calendar and want agent-assisted summaries reviewed by attorneys.
When should I use brief?
Use `/brief daily` in Operate for morning legal scans, `/brief topic` when scoping a specific legal question across internal sources, and `/brief incident` when a breach, inquiry, or litigation threat needs rapid context during Ship or Operate response.
Is brief safe to install?
It can read sensitive mail and calendar data through connectors; review the Security Audits panel on this page and restrict connector scope before production use.
SKILL.md
READMESKILL.md - Brief
# /brief -- Legal Team Briefing > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../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. ## Invocation ``` /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. ## Modes --- ### Daily Brief A morning summary of everything a legal team member needs to know to start their day. #### Sources to Scan Check each connected source for legal-relevant items: **Email (if connected):** - New contract requests or review requests - Compliance questions or reports - Responses from counterparties on active negotiations - Flagged or urgent items from the legal team inbox - External counsel communications - Regulatory or legal update newsletters **Calendar (if connected):** - Today's meetings that need legal prep (board meetings, deal reviews, vendor calls) - Upcoming deadlines this week (contract expirations, filing deadlines, response deadlines) - Recurring legal team syncs **Chat (if connected):** - Overnight messages in legal team channels - Direct messages requesting legal input - Mentions of legal-relevant topics (contract, compliance, privacy, NDA, terms) - Escalations or urgent requests **CLM (if connected):** - Contracts awaiting review or signature - Approaching expiration dates (next 30 days) - Newly executed agreements **CRM (if connected):** - Deals moving to stages that require legal involvement - New opportunities flagged for legal review #### Output Format ``` ## 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] ``` --- ### Topic Brief Research and brief on a specific legal question or topic across available sources. #### Workflow 1. Accept the topic query from the user 2. Search across connected sources: - **Documents**: Internal memos, prior analyses, playbooks, precedent - **Email**: Prior communications on the topic - **Chat**: Team discussions about the topic - **CLM**: Related contracts or clauses 3. Synthesize findings into a structured brief #### Output Format ``` ## 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 po