Skip to main content
skill CX Codex official · Anthropic

matter-workspace · anthropics, regulatory-legal — Claude Code skill: features and installation

The matter-workspace Claude Code skill manages separate workspaces for legal matters. Create a matter, switch the active context, list matters, or archive a closed one.

Apache-2.0 ★ 10,060 updated 2026-10-23

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add anthropics/claude-for-legal
/plugin install regulatory-legal@claude-for-legal
Open on GitHub

What matter-workspace does

The skill creates matter workspaces, switches the active matter, lists existing matters, and archives closed ones. Creating a matter starts with a short intake, then writes matter.md, history.md, and notes.md. The none command detaches work from any active matter and returns to practice-level context.

The active matter is recorded in the Active matter: line of ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md. The Matter workspaces section must be enabled; the default state is off. Closed matters move to _archived rather than being deleted. The skill shows planned changes and asks for confirmation before writing.

What it helps with

  • separate context for different clients and matters
  • create a matter workspace with intake notes
  • switch the active matter in the practice profile
  • archive a closed matter without deleting it

Example prompts for the agent

  • Create a workspace for acme-msa-2026 and collect its matter details.
  • List the matters and mark the active one.
  • Close zenith-renewal and move it out of the active matters.

How to install matter-workspace

1Plugin marketplace

/plugin marketplace add anthropics/claude-for-legal
/plugin install regulatory-legal@claude-for-legal

This installs the whole regulatory-legal plugin with all its skills

2Skills CLI (Vercel)

npx skills add anthropics/claude-for-legal --skill matter-workspace -a claude-code

3Manually: put the files in place

~/.claude/skills/matter-workspace/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/matter-workspace/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about matter-workspace

How do I install matter-workspace in Claude Code?

Add the marketplace with /plugin marketplace add anthropics/claude-for-legal, then install the plugin with /plugin install regulatory-legal@claude-for-legal.

What does matter-workspace do?

It creates and lists legal matter workspaces, changes the active matter, and archives closed matters. New workspaces include an intake and files for matter details, history, and notes.

When does matter-workspace run?

Matter management is enabled through the Matter workspaces section in the practice CLAUDE.md file. Its default state is off.

Source text

SKILL.md · Apache-2.0
---
name: matter-workspace
description: Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.
argument-hint: "<new | list | switch | close | none> [slug]"
---

# /matter-workspace

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.

## Subcommands

- `/regulatory-legal:matter-workspace new <slug>` — create a new matter workspace, run a short intake, write `matter.md`
- `/regulatory-legal:matter-workspace list` — list matters with status and active flag
- `/regulatory-legal:matter-workspace switch <slug>` — set the active matter
- `/regulatory-legal:matter-workspace close <slug>` — archive a matter (move to `~/.claude/plugins/config/claude-for-legal/regulatory-legal/matters/_archived/`, never delete)
- `/regulatory-legal:matter-workspace none` — detach from any active matter, work at practice-level only

## Instructions

1. Read `~/.claude/plugins/config/claude-for-legal/regulatory-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 `/regulatory-legal:cold-start-interview --redo` and select a private-practice setting. Otherwise, you don't need `/matter-workspace` at all." Don't error — the disabled state is the expected one for in-house users.
2. Use the file-management logic below.
3. Dispatch on the first token of `$ARGUMENTS`:
   - `new` → run the intake interview, write `~/.claude/plugins/config/claude-for-legal/regulatory-legal/matters/<slug>/matter.md`, seed `history.md` and `notes.md`.
   - `list` → enumerate `~/.claude/plugins/config/claude-for-legal/regulatory-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/regulatory-legal/matters/<slug>/` to `~/.claude/plugins/config/claude-for-legal/regulatory-legal/matters/_archived/<slug>/`, log the close date in `history.md`.
   - `none` → set `Active matter:` to `none — practice-level context only`.
4. Show the user what changed and confirm before writing.

## Notes

- The skill never reads across matters unless `Cross-matter context` is `on` in the practice-level CLAUDE.md.
- Archiving is not deletion — closed matters remain readable for retention/conflicts purposes.
- Slugs are lowercase with hyphens. If a slug is reused across archived and active, the archived one is preserved under `_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; it explains the disabled state and suggests `/regulatory-legal:cold-start-interview --redo` for users who actually need matter isolation.

## Storage layout

All matter data lives under:

```
~/.claude/plugins/config/claude-for-legal/regulatory-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-msa-2026`, `zenith-renewal`, `vendor-xyz-nda`.

## Active matter is in the practice CLAUDE.md

The `Active matter:` line under `## Matter workspaces` in the practice-level CLAUDE.md is the single source of truth. Switching a matter edits that line. No separate state file.

## Subcommand logic

### `new <slug>`

1. Confirm slug is not already present in `matters/<slug>/` or `matters/_archived/<slug>/`. If reused, ask the user to pick a different slug.
2. Run the intake interview:
   - **Client** (the party we represent, or the internal business unit if in-house)
   - **Counterparty** (the other side — may be multiple)
   - **Matter type** (read the plugin's practice profile for typical categories; for regulatory-legal: rulemaking | comment period | gap remediation | agency inquiry | enforcement response | standing topic | other)
   - **Confidentiality level** (standard | heightened | clean-team — heightened prompts extra care in cross-matter settings)
   - **Key facts** (2–5 sentences: what this matter is about, who the stakeholders are, what's at stake)
   - **Matter-specific overrides to the practice playbook** (e.g., "client requires 24-month LoL cap not 12", "counterparty is a strategic partner — relationship-preserving tone")
   - **Related matters** (slugs of any connected matters)
3. Write `matters/<slug>/matter.md` using the template below.
4. Seed `matters/<slug>/history.md` with a single "Opened" entry.
5. Create an empty `matters/<slug>/notes.md`.
6. Do **not** auto-switch to the new matter. Ask: "Want to switch to `<slug>` now? (`/regulatory-legal:matter-workspace switch <slug>`)"

### `list`

Enumerate `matters/*/matter.md`. Read each file's front-matter or first few lines to extract status. Print a table:

| Slug | Client | Matter type | Status | Opened | Active |
|---|---|---|---|---|---|

Mark the currently-active matter with `*`. Include `_archived/*` under a separate "Archived" heading if any exist.

### `switch <slug>`

1. Confirm `matters/<slug>/matter.md` exists. If not, offer `/regulatory-legal:matter-workspace new <slug>`.
2. Edit the `Active matter:` line in the practice-level CLAUDE.md to `Active matter: <slug>`.
3. Show the user the matter.md summary so they can confirm they're on the right matter.

### `close <slug>`

1. Confirm `matters/<slug>/` exists.
2. Append a "Closed" entry to `matters/<slug>/history.md` with today's date.
3. Move `matters/<slug>/` → `matters/_archived/<slug>/`.
4. If the closed matter was the active matter, set `Active matter:` to `none — practice-level context only`.

### `none`

Set `Active matter:` in the practice-level CLAUDE.md to `none — practice-level context only`. Confirm with the user.

## `matter.md` template

```markdown
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this` in the practice-level CLAUDE.md]

# Matter: [Client] — [short description]

**Slug:** [slug]
**Opened:** [YYYY-MM-DD]
**Status:** active
**Confidentiality:** [standard / heightened / clean-team]

---

## Parties

**Client:** [name]
**Counterparty:** [name(s)]

## Matter type

[vendor MSA | customer agreement | NDA | SaaS subscription | amendment | renewal | other — with one-line rationale]

## Key facts

[2–5 sentences. What this matter is about. Who the stakeholders are. What's at stake. What makes it different from the default playbook.]

## Matter-specific overrides

*Any deviation from the practice-level playbook that applies to this matter and only this matter.*

- [e.g., "LoL cap: client requires 24 months, not house standard 12."]
- [e.g., "Tone: relationship-preserving — counterparty is a strategic partner."]
- [e.g., "Governing law: must be English law, not Delaware."]

## Related matters

- [slug — one line why related]

## Notes on confidentiality

[If heightened or clean-team, describe why. Who may see matter files. Whether cross-matter context is permissible even if globally on.]
```

## `history.md` seed

```markdown
# History: [Client] — [short description]

Append-only event log. Most recent at top.

---

## [YYYY-MM-DD] — Matter opened

Intake completed. Slug: `[slug]`. Status: active.
[Any initial context worth preserving beyond matter.md — e.g., "Opened in response to inbound MSA draft from [counterparty]."]
```

## Cross-matter context

The practice-level CLAUDE.md has a `Cross-matter context:` flag. When it's `off` (the default), a skill working in matter A **never reads** files in `matters/B/` for any other `B`. Period. This is the confidentiality guarantee the setting exists to provide.

When it's `on`, a skill may read files across matter folders only when the user explicitly asks it to (e.g., "compare our position on liability caps across the last five vendor matters"). Even when `on`, the default is to load only the active matter unless the user asks for a cross-matter view.

## What this skill does not do

- **Run a conflicts check.** Conflicts are the practitioner's/firm's job; the intake captures what the user declares.
- **Enforce retention.** Closing archives a matter; it does not delete. Retention policy is out of scope.
- **Auto-route outputs.** The substantive skill decides where to write; this skill tells it *which folder* is active, not what to put in it.
- **Decide whether cross-matter is appropriate.** It reads the flag and obeys.

© Anthropic · Apache-2.0 · anthropics/claude-for-legal

Similar skills

All skills for Finance and business →

matter-workspace by other authors comes first.

matter-workspace official anthropics matter-workspace — a skill for Claude Code, Codex, Cursor, GitHub Copilot and other platforms that creates isolated workspaces for each matter or client. CX Codex +1 633installs matter-workspace official Anthropic matter-workspace — a skill for Claude Code that isolates client matter context in private legal practice. It manages separate folders for each engagement so contexts never mix. CX Codex +1 ★ 10,060repo stars matter-workspace official Anthropic The matter-workspace Claude Code skill manages separate workspaces for client matters. It creates, lists, switches, and archives matters, or clears the active matter. CX Codex +1 ★ 10,060repo stars matter-workspace official Anthropic The matter-workspace Claude Code skill manages separate workspaces for legal matters. It creates, lists, switches, and archives matters, or detaches the active one. CX Codex +1 ★ 10,060repo stars matter-workspace official Anthropic The matter-workspace Claude Code skill manages separate workspaces for client matters. It creates and switches matters, lists them, and archives closed ones. CX Codex +1 ★ 10,060repo stars warm-path-workspace crustdata warm-path-workspace builds an interactive HTML deal workspace for target accounts: buying-group maps, stakeholder dossiers, and weighted warm-intro paths mapped from your team's LinkedIn exports. CX Codex +1 342installs python-workspace terrylica python-workspace converts MQL5 indicators to Python and exports MetaTrader 5 data headlessly with automated correlation checks. CX Codex +1 131installs physics-matter phaserjs physics-matter helps AI agents configure Matter.js physics in Phaser 4, including rigid bodies, composite shapes, constraints, and mouse dragging. CX Codex +1 937installs Dark Matter Analyzer daffy0208 Dark Matter Analyzer audits codebases for hidden friction, documentation inflation, and divergence between goals and commits. Useful before major refactorings. CX Codex +1 128installs nx-workspace nrwl A skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode that gives AI agents the commands to navigate an Nx workspace. CX Codex +1 100,600installs orca-per-workspace-env stablyai The orca-per-workspace-env Claude Code skill sets up and checks Orca environment recipes for individual workspaces. It applies to environmentRecipes in orca.yaml, provider scripts, and orca vm recipe doctor failures. CX Codex +1 12,600installs

From the same set174

The whole set →
expansion-update expansion-update updates international expansion YAML trackers, recalculates unblocked items, flags overdue deadlines, and surfaces next priority tasks. CX Codex +1 615installs ramp ramp is a Claude Code skill that walks new legal clinic students through clinic procedures and tools. It starts when a student asks for an introduction or at the beginning of a semester. CX Codex +1 611installs semester-handoff semester-handoff writes a transition memo for every active case plus a cohort summary, so departing students hand their work to the incoming cohort cleanly. CX Codex +1 611installs log-leave log-leave adds an employee leave entry to a local YAML register and starts tracking legal deadlines. Useful when an employee goes on leave and HR or legal needs to monitor certification clocks immediately. CX Codex +1 611installs customize The customize Claude Code skill edits individual settings in a regulatory practice profile. It runs when someone asks to change watched regulators, a threshold, or another profile section. CX Codex +1 ★ 10,060repo stars cold-start-interview cold-start-interview — a Claude Code skill that configures a regulatory watchlist, indexes policy files, and records a materiality threshold. Run it for initial setup, a reset, or an integration check. CX Codex +1 ★ 10,060repo stars reg-change-monitor The reg-change-monitor subagent for Claude Code and Codex monitors regulatory feeds for changes. It filters data by a materiality threshold, creating a concise digest to deliver only significant updates. CX Codex ★ 10,060repo stars matter-workspace matter-workspace — a skill for Claude Code that isolates client matter context in private legal practice. It manages separate folders for each engagement so contexts never mix. CX Codex +1 ★ 10,060repo stars

Project sponsors

Companies that keep this analytics open