Manage matter workspaces to separate, switch, and archive client contexts.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "matter-workspace" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/ip-legal/skills/matter-workspace/SKILL.md 2. Save it as ~/.claude/skills/matter-workspace/SKILL.md 3. Reload skills and tell me it's ready
Create a new matter workspace with the slug acme-trademark-opposition and run the short intake.
A new matter workspace is created and files such as matter.md are initialized.
Switch to the matter workspace with the slug acme-trademark-opposition.
The active matter is updated so subsequent work uses that matter context.
List all matter workspaces, then set the active matter to none.
A list of matters and statuses is shown, then context is detached to practice-level only.
It helps practitioners handling multiple client matters keep each client or engagement context separate. After switching the active matter, subsequent work stays focused on that matter.
When a matter is finished, it can be closed and archived instead of deleted for retention, review, or conflicts purposes. Archived matters remain readable.
When work does not belong to a specific matter, users can detach from the active matter and operate at practice-level context only. This suits general workflows or practice-wide information.
The documentation explains the purpose of the matter-workspace skill and its subcommands for creating, listing, switching, closing, and detaching from matter workspaces. It emphasizes context isolation for multi-client private practice so information does not leak across matters. It also notes that the feature is off by default for in-house users, and that closing a matter archives it rather than deleting it.
Practitioners work across multiple clients and matters. A matter workspace keeps one client or engagement's context separate from every other. This skill manages those workspaces.
/ip-legal:matter-workspace new <slug> — create a new matter workspace, run a short intake, write matter.md/ip-legal:matter-workspace list — list matters with status and active flag/ip-legal:matter-workspace switch <slug> — set the active matter/ip-legal:matter-workspace close <slug> — archive a matter (move to ~/.claude/plugins/config/claude-for-legal/ip-legal/matters/_archived/, never delete)/ip-legal:matter-workspace none — detach from any active matter, work at practice-level only~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md — confirm the ## Matter workspaces section is populated. If Enabled is ✗, tell the user: "Matter workspaces are off — you're configured as an in-house practice with one client, so the plugin works from practice-level context automatically. If you actually work across multiple clients, re-run /ip-legal:cold-start-interview --redo and select a private-practice setting. Otherwise, you don't need /ip-legal:matter-workspace at all." Don't error — the disabled state is the expected one for in-house users.$ARGUMENTS:
new → run the intake interview, write ~/.claude/plugins/config/claude-for-legal/ip-legal/matters/<slug>/matter.md, seed history.md and notes.md.list → enumerate ~/.claude/plugins/config/claude-for-legal/ip-legal/matters/*/matter.md, print a table, mark the active matter.switch → update the Active matter: line in the practice-level CLAUDE.md.close → move ~/.claude/plugins/config/claude-for-legal/ip-legal/matters/<slug>/ to ~/.claude/plugins/config/claude-for-legal/ip-legal/matters/_archived/<slug>/, log the close date in history.md.none → set Active matter: to none — practice-level context only.Cross-matter context is on in the practice-level CLAUDE.md._archived/<slug>/.Multi-client practitioners (private practice — solo, small firm, large firm) work across many matters. Context from one must not leak into another. This skill is the thin file-management layer that makes that true.
Default state is off. In-house users never see this — they run at practice-level only. Matter workspaces turn on at cold-start for private-practice users, or by editing ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗, this skill does not run; instead it explains the disabled state and suggests /ip-legal:cold-start-interview --redo for users who actually need matter isolation.
All matter data lives under:
~/.claude/plugins/config/claude-for-legal/ip-legal/
├── CLAUDE.md # practice-level practice profile
└── matters/
├── <slug>/
│ ├── matter.md # client, counterparty, matter type, key facts, overrides
│ ├── history.md # dated log of events, decisions, drafts, reviews
│ ├── notes.md # free-form working notes
│ └── outputs/ # skill outputs for this matter (optional subfolder)
└── _archived/
└── <slug>/ # closed matters — readable but not active
Slugs are lowercase with hyphens. Examples: acme-trademark-2026, zenith-dmca, novacorp-fto.
…
It manages matter workspaces, including creating, listing, switching, closing and archiving, and detaching from the current active matter. Its core purpose is to isolate context across multiple clients and matters.
The docs say this feature is off by default for in-house users. If `Enabled` is `✗` under `Matter workspaces` in the practice-level configuration, it does not run and work stays at practice-level context only.
No. The docs state that closing moves the matter into an archive directory rather than deleting it, and archived matters remain readable.
Search watched skill registries, preview matches, and inspect SKILL.md before installing.
Safely review and install community skills with explicit user approval.
Get a concise briefing on one legal matter's status, changes, deadlines, and risks.
Safely uninstall hub-installed community skills with confirmation and audit logging.
Temporarily disable or re-enable an installed community skill without deleting files.
Draft DMCA notices, triage incoming claims, and prepare counter-notice drafts.
Manage Rocket Matter matters, clients, time, billing, and legal operations by chat.
Browse and manage files in your Moxt AI workspace from any MCP client.
Provide controlled workspaces, state tracking, and auditable handoffs for coding agents.
Track action items and mutual obligations with AI suggestions you approve.
Let AI coding agents manage multiple workspace repositories in one session.
Helps users triage workspace content items for next-step handling.