$ loading_
Get a concise briefing on one legal matter's status, changes, deadlines, and risks.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "matter-briefing" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/litigation-legal/skills/matter-briefing/SKILL.md 2. Save it as ~/.claude/skills/matter-briefing/SKILL.md 3. Reload skills and tell me it's ready
Brief me on the matter with slug acme-v-zenith. Organize it by current posture, recent changes, next deadline, open questions, and a risk reassessment check.
A single-matter briefing summarizing current status, recent developments, next timing, and risk points to reassess.
Where are we on the nova-employment-dispute matter? Give me a briefing suitable for updating the GC.
A management-ready summary covering the stage, key changes, next actions, and unresolved questions.
Generate a briefing from the existing matter records and specifically flag whether the risk field still reflects reality; also note if it has not been updated for over 30 days.
A matter briefing with a risk reassessment prompt and a staleness warning if applicable.
Legal or business support staff can quickly assemble the current posture, recent changes, and next deadline for one matter before updating the GC. This helps create a clear verbal update in very little time.
Before speaking with outside counsel, users can review the latest status, open questions, and risk reassessment prompt for a single matter. This helps clarify what to ask and which decisions need attention.
When a matter has not been updated recently, this skill can flag if the record is more than 30 days old. Users can use that signal to decide whether to add new events or revisit the risk rating.
The documentation describes a skill for generating a fast briefing on a single legal matter before a GC update or an outside counsel call. It loads the matter log, matter narrative, history, and risk calibration context, then summarizes the current posture, recent changes, next deadline, open questions, and a risk reassessment prompt. It also flags stale records older than 30 days and refuses to proceed if the matter has not gone through intake and the conflicts check.
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → risk calibration + relevant stakeholders.~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md + ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md + log row from _log.yaml.risk: field still reflect reality?").last_updated > 30 days, say so.Give the counsel a clean read on one matter in the time it takes to walk to a conference room. Current posture, what's changed, what's next, what's worth reconsidering.
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml — structured row~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md — narrative intake~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md — event log~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md — risk calibration (so "risk: high" means something specific, not generic)Conflicts gate — unbypassable. Before briefing, check _log.yaml for the matter slug. If the matter is not in _log.yaml, refuse and route:
"I don't see [matter slug] in the matter log. Run
/litigation-legal:matter-intakefirst so the conflicts check runs and the matter workspace is set up. I won't build a briefing on a matter that hasn't been intaken — the conflicts check is the gate."
Slug (required). If ambiguous or missing, ask the user to pick from a list of active matters.
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
# [Matter Name] — Briefing as of [today]
**Status:** [status / stage]
**Risk:** [rating] ([severity] × [likelihood])
**Materiality:** [category]
**Outside counsel:** [firm — lead]
**Last updated:** [date] [flag ⚠️ STALE if >30d]
**Conflicts:** [status — flag ⚠️ if `pending` or `not-run`]
---
## One-paragraph summary
[Current posture. What are we doing and why. Name the pivot fact if one is captured.]
## What's changed recently
[Last 3-5 entries from history.md, most recent first. If history is thin, say so.]
## What's next
- **Immediate deadline:** [next_deadline + what it is]
- **Upcoming milestones:** [anything dated in matter.md or recent history]
- **Decisions pending:** [open questions flagged in matter.md]
## Exposure
[Range + any change since intake. If reserved, current reserve + whether recalibration is overdue.]
## Internal owners
[Who's looped in; whether anyone should be looped in and isn't]
## Risk re-assessment check
*A prompt, not an answer.*
- Does `risk: [rating]` still feel right, or has the case moved?
- Does `materiality: [category]` still match? (New facts might push toward reserve or disclosure.)
- Any new stakeholder the matter needs (e.g., CISO becomes relevant after a discovery development)?
## Open questions
[From matter.md and anything unresolved in history]
## For the conversation
[If user specified a purpose — "brief me before the call with outside counsel" — tailor the final section: questions to ask, decisions to get, updates to extract. If no purpose given, omit this section.]
If last_updated > 30 days ago: flag at the top AND suggest running /litigation-legal:matter-update [slug] after the meeting to capture whatever's discussed.
This is not marketing. Say what's known; flag what's not. If a matter has thin history and was just opened, the briefing is short — and that's correct. Don't pad.
…
It produces a briefing for one matter, focusing on the current posture, recent changes, next deadline, open questions, and a prompt to reassess whether the risk field is still accurate.
The docs indicate that a matter slug is required. If the matter is missing or ambiguous, the user should choose from active matters; if it is not in the matter log, matter intake must be run first.
The docs describe an unbypassable conflicts gate: if the matter is not listed in `_log.yaml`, the skill will not generate a briefing and instead requires the intake workflow to be completed first.
Safely review and install community skills with explicit user approval.
Search watched skill registries, preview matches, and inspect SKILL.md before installing.
Safely uninstall hub-installed community skills with confirmation and audit logging.
Temporarily disable or re-enable an installed community skill without deleting files.
Manage matter workspaces to separate, switch, and archive client contexts.
Draft DMCA notices, triage incoming claims, and prepare counter-notice drafts.
Prepare structured legal meeting briefings and track follow-up action items.
Generate legal briefings for daily updates, research, and incident response.
Draft common legal responses from templates with built-in escalation checks.
Assess legal risk and decide escalation using severity-likelihood criteria.
Standardize new matter intake and generate matter files plus a structured log.
Generate a prioritized daily sales briefing from meetings, CRM, and email.