matter-close
Close a matter — capture outcome, final exposure, and lessons, then archive it out of the active portfolio without deleting the record. Use when the user wants to close a matter, says "[matter] is done", or needs to record a settlement, dismissal, judgment, withdrawal, or consolidation outcome.
- Installs
- 598
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/anthropics/claude-for-legal --skill matter-close- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads matter-close automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
/matter-close
- Follow the workflow and reference below.
- Confirm slug and current status.
- Capture outcome: resolution type (settled, dismissed, judgment for/against, withdrawn, consolidated), date, final exposure/cost, lessons.
- Update
_log.yaml:status: closed, addclosed: YYYY-MM-DDandoutcome:fields. - Append final entry to
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md. - Matter stays in
_log.yamland~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/— not deleted./portfolio-statusfilters it from active rollups.
Matter Close
Purpose
Matters end. The outcome is the single most valuable data point the portfolio generates — it calibrates the risk framework for future matters. Closing a matter captures the outcome structurally so the record is useful, not just archived.
Load context
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml— find the row~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md— reference (intake context)~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md— append target
Conflicts gate — unbypassable. Before closing, 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. Nothing to close — either the slug is wrong or the matter was never intaken through
/litigation-legal:matter-intake. Check the slug first; if it genuinely was never intaken, there's no row to update and no file structure to close."
Input
Slug (required).
The close
1. Resolution type
settled— with counterparty, dollar amount, structural termsdismissed— with or without prejudice, by what mechanismjudgment-for-us— at what stage, appeal exposurejudgment-against-us— at what stage, appeal status, exposure crystallizedwithdrawn— by counterparty, circumstancesconsolidated— merged into another matter (provide slug of parent)other— with explanation
2. Resolution date
The date the matter actually ended (settlement executed, order issued, dismissal filed).
3. Final exposure
- Actual cost to company (settlement amount + fees + injunctive/structural cost)
- vs. initial exposure range at intake (did we call it?)
- Reserve accuracy (if reserved): booked vs. actual
4. Lessons
Two or three sentences. What did we get right? What did we misjudge? Anything the intake should have flagged earlier?
This is the part future counsel will reread. Be honest. "Misjudged likelihood — plaintiff firm was more aggressive than expected" is worth more than "resolved favorably."
5. Seed doc prompt
Settlement agreement, final order, dismissal — path if available. Not required.
Writing
Before closing the matter (the consequential act — the matter is archived and active tracking ends): Read ## Who's using this in ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md. If the Role is Non-lawyer:
Closing a matter has legal consequences — it ends active tracking, may affect any associated legal hold (run
/legal-hold --releaseseparately if appropriate), and establishes the final record the company relies on. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:[Generate a 1-page summary: the matter, resolution type and terms, final exposure vs. initial, reserve accuracy, related matters or appeals still live, what could go wrong with premature closure, what to ask the attorney.]
If you need to find a licensed attorney, solicitor, barrister, or other authorised legal professional in your jurisdiction: your professional regulator's referral service is the fastest starting point (state bar in the US, SRA/Bar Standards Board in England & Wales, Law Society in Scotland/NI/Ireland/Canada/Australia, or your jurisdiction's equivalent).
Do not write the close fields or append the close entry without an explicit yes.
Update ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml
status: closed
closed: [YYYY-MM-DD]
outcome: [resolution-type]
final_cost: [dollar amount]
last_updated: [today] # close is the last touch; record it
Retain all existing fields. Do not delete the row.
Append final entry to ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md
## [YYYY-MM-DD] — Matter closed: [resolution-type]
**Resolution:** [narrative — what happened, on what terms]
**Final cost:** [amount + structural terms if any]
**vs. initial exposure:** [compare to matter.md intake range]
**Reserve accuracy:** [if applicable]
**Lessons:**
[2-3 sentences — honest retrospective]
**Related doc:** [settlement agreement / final order / etc., if provided]
Touch ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md
Add a closing block at the end (don't modify earlier sections — they're the historical intake):
---
## Closed [YYYY-MM-DD]
[Resolution summary in one paragraph. Pointer to the final history entry for detail.]
Confirm
Show the user the full close entry and the yaml changes before writing.
What this skill does not do
- Delete matters. Closed matters stay in
_log.yamland on disk — they're the training set for the portfolio's judgment. - Re-open. If a closed matter comes back (appeal, related litigation), open a new matter that references the closed one in
matter.md. - Summarize lessons the user didn't say. If the user skips the lessons section, leave it empty rather than invent.
FAQ
What does the matter-close skill do?
Close a matter — capture outcome, final exposure, and lessons, then archive it out of the active portfolio without deleting the record. Use when the user wants to close a matter, says "[matter] is done", or needs to record a settlement, dismissal, judgment, withdrawal, or consolidation outcome.
How do I install matter-close?
Run npx skills add https://github.com/anthropics/claude-for-legal --skill matter-close in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/matter-close/ (personal) or .claude/skills/matter-close/ (project).
Which AI agents can use matter-close?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is matter-close safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains matter-close?
It is published by anthropics in anthropics/claude-for-legal, and it is an official skill from the maker of the technology it covers. It has 598 recorded installs.
More from anthropics/claude-for-legal
legal-writing
anthropics/claude-for-legal
Structural feedback on a legal writing draft (memo, brief, paper, exam essay) — organization, analysis depth, clarity, citation form. NEVER rewrites the draft. Use when the user says "feedback on my memo", "read my draft", or "critique my brief".
draft
anthropics/claude-for-legal
First draft of a common clinic document — practice-area templates (asylum applications, eviction answers, protective order petitions, demand letters), jurisdiction-aware formatting, explicitly a starting point requiring student analysis and attorney review. Use when a student needs a first draft of a motion, letter, petition, declaration, or other clinic document.
flashcards
anthropics/claude-for-legal
Generate or drill flashcards for black-letter memorization — Leitner-style buckets, per-subject markdown storage, drill mode with self-assessment. Use when the user says "drill flashcards", "make flashcards from", "quiz me on cards", or wants to memorize rules.
saas-msa-review
anthropics/claude-for-legal
Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.
review
anthropics/claude-for-legal
Review a vendor agreement, NDA, or SaaS subscription against your playbook. Identifies the agreement structure from titles, routes to the right review skill (vendor-agreement-review, nda-review, saas-msa-review), and integrates the output into a single memo. Use when the user says "review this contract", "check this MSA", "is this NDA okay", "look at this SaaS agreement", or attaches an inbound agreement for review.
policy-monitor
anthropics/claude-for-legal
Keep the privacy policy current with practice. Two modes: weekly sweep of saved PIAs, DPA reviews, and triage results to find policy drift; or direct query for a proposed new practice. Use when the user asks "does our policy cover this", "we want to start doing X — does the policy need updating", "run the policy monitor", "policy sweep", or wants to find where the privacy policy no longer matches what the team actually does.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.