
Matter Close
OfficialFreeEfficiently close legal matters and capture outcomes.
Free · Opens the source repo
What Matter Close does
The Matter Close skill is designed to assist legal professionals in systematically closing matters while ensuring that all critical data points are captured and preserved. This skill is particularly useful for attorneys and legal staff who need to document the resolution of cases, whether they are settled, dismissed, or concluded through judgment. By following a structured workflow, users can record the outcome, final costs, and lessons learned, which are essential for future reference and risk assessment.
When a matter is closed, the skill prompts users to confirm the current status and then capture the resolution type, date, final exposure, and lessons learned. This information is not only recorded in the matter's history but also updated in the _log.yaml file, allowing for easy tracking of all matters within the portfolio. The skill ensures that closed matters remain accessible for future analysis without cluttering the active portfolio, thus maintaining an organized workflow.
The Matter Close skill is particularly beneficial for legal teams that manage multiple cases simultaneously, as it streamlines the closure process and ensures that valuable insights are not lost. By capturing lessons learned, the skill enables teams to refine their strategies and improve their handling of future matters. This reflective practice is crucial in the legal field, where understanding past outcomes can significantly impact future performance.
Overall, the Matter Close skill provides a structured approach to closing legal matters, ensuring that all necessary information is documented and archived appropriately. This not only aids in compliance and record-keeping but also enhances the overall effectiveness of legal operations.
When to use it
Use this skill when you need to formally close a legal matter and ensure that all relevant details are documented for future reference.
When not to use it
This skill is not suitable for reopening matters or deleting records, as it is specifically designed for the closure process.
What you can build with it
Closing a Settled Case
When a case has been settled, use this skill to document the settlement details and capture lessons learned for future reference.
Archiving a Dismissed Matter
If a matter has been dismissed, this skill allows you to formally close it while ensuring all relevant information is recorded.
Finalizing a Judgment Outcome
After a judgment has been issued, use this skill to capture the final exposure and any lessons learned from the case.
How to install Matter Close
View source1. Install with the skills CLI
npx skills add anthropics/claude-for-legal/matter-close --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by anthropics/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.
Frequently asked questions about Matter Close
Similar skills
Contract Review
Simplify contract analysis for small businesses.
Vendor Agreement Status
Streamline vendor agreement management across systems.
NDA Triage
Streamline your NDA screening process efficiently.
Contract Review
Streamline contract analysis against your negotiation playbook.
Meeting Briefing
Prepare structured legal meeting briefings and track actions.
Legal Risk Assessment
Evaluate and classify legal risks systematically.
