Skip to content
Agentmart
Submit a tool

matter-journal

Manages client matter journals — persistent case files that give Claude full context on every client and matter.

Skill by bstevescherer

IndexedMIT★ 43
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/bstevescherer-matter-journal

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Manages client matter journals — persistent case files that give Claude full context on every client and matter. Use this skill when the user says "new client", "new matter", "I'm working on [X]", "open the [X] matter", "update the journal", "log this", "what's the status of", "close the [X] matter", "set up", "configure", or mentions creating a new matter or asks about a client by name. Also use when the user asks "what am I working on", wants to review active matters, or dictates notes after a call or meeting. This is a context management skill — it creates, loads, and logs to journals. It does not draft documents, send emails, or perform legal analysis, but it provides the context that makes those tasks dramatically better.

Use cases: productivity, legal

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found
Runs as
Python package

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/matter-journal

What's inside

Skill name
matter-journal
Description
Manages client matter journals — persistent case files that give Claude full context on every client and matter. Use this skill when the user says "new client", "new matter", "I'm working on [X]", "open the [X] matter", "update the journal", "log this", "what's the status of", "close the [X] matter", "set up", "configure", or mentions creating a new matter or asks about a client by name. Also use when the user asks "what am I working on", wants to review active matters, or dictates notes after a call or meeting. This is a context management skill — it creates, loads, and logs to journals. It does not draft documents, send emails, or perform legal analysis, but it provides the context that makes those tasks dramatically better.
License
MIT
Instructions
208 lines in SKILL.md · view on GitHub

Before installing

  • Ships executable scripts

Agent Skills spec issues

  • files: referenced but missing: references/claude-md-template.md, references/journal-template.md, references/scheduled-tasks.md

Files (7)

  • README.md
  • SKILL.md
  • claude-md-template.md · reference/
  • journal-template.md · reference/
  • scheduled-tasks.md · reference/
  • sync_index.py · scripts/
  • skill.yml

SKILL.md (first lines)

# Matter Journal

You manage a system of per-matter journals — one markdown file per client
matter that accumulates everything Claude learns about that matter over
time. The journal is a living case file: a header identifying the matter
and a chronological log of everything that happened.

The journal makes you a better collaborator on every legal task because
you carry forward full context — strategy, client preferences, opposing
counsel behavior, negotiation history, deadlines, impressions — across
sessions. The richer the journal, the better you perform.

## Architecture

```
Legal Matters/                     ← the folder the attorney opened
├── CLAUDE.md                      ← standing instructions (written during setup)
├── matters.json                   ← index of all matters (auto-maintained)
├── Chen-Trademark-2026/
│   └── journal.md
├── Smith-BreachOfContract-2026/
│   └── journal.md
```

`matters.json` is the index. Each entry has: id, folder, client,
matter_name, matter_type, aliases, parties (role-tagged), status,
created, last_session. Aliases and parties enable fuzzy matching when
the attorney mentions a name.

## First-Run Setup

If `matters.json` does not exist at the folder root, the system hasn't
been set up yet. This also triggers on "set up", "configure", "first time",
or any setup-related request.

1. Explain briefly what you're about to create: "I'll create two files —
   `matters.json` to track your matters, and `CLAUDE.md` so I automatically
   load the right case file when you mention a client. Over time I'll build
   up context on every matter so you never have to re-explain anything."
2. Wait for approval. On confirmation:
   - Read `references/claude-md-template.md` and write its contents to
     `CLAUDE.md` at the folder root
   - Create `matters.json` containing `[]`
3. Confirm: "Done. Want to create your first matter?"

Keep this conversational and quick. The attorney should never leave the
chat to set things up.

## Create Matter

Triggered by "new matter", "new client", or any indication the attorney
wants to open a new case file.

**Do not run a structured interview.** Extract what the attorney already
said — client name, matter type, description, any parties mentioned. If
the client name or matter type is genuinely missing, ask for just those
in a single question.

Then ask one thing: "Do you have any existing files or notes on this?
Drop them and I'll start the journal from there. Or if you have an
existing folder, I can add the journal there."

Three paths:

- **Attorney drops files** → Read them, create journal with a first log
  entry summarizing what's in the files. This gives rich starting context.
- **Attorney names an existing folder** → Create `journal.md` inside that
  folder. Don't restructure their files.
- **Attorney says no / just proceed** → Create a new folder named
  `[Client]-[ShortDescription]-[Year]/`

To assign a matter ID: read `matters.json`, find the highest `M-XXX`
number, increment by one.

Create `journal.md` using the template in `references/journal-template.md`,
filling in all known fields. Add the new entry to `matters.json` with
appropriate aliases (client first name, last name, full name, any
business names mentioned) and role-tagged parties.

Confirm conversationally: "Chen trademark matter is set up (M-003).
Anything else to add before we start?"

## Load Matter

Triggered when the attorney mentions a client, matter, or party name —
either explicitly ("I'm working on Chen") or in the course of asking
for work ("Draft a letter to BigCo about the Chen trademark").

**Matching:** Check the `client`, `matter_name`, `aliases`, and
`parties[].name` fields in `matters.json`. Case-insensitive, partial
match is fine (e.g., "Chen" matches "Sarah Chen").

- **Single match** → Load the journal.md. Show the last log entry briefly:
  "Chen — last entry 3/17: Drafted C&D to BigCo. What are we doing?"
- **Multiple matches** → Disambiguate with matter IDs:
  "Two Smith matters: M-012 breach of contract, M-031 trademark. Which one?"
- **No match** → "No matter on file for [X]. Want to create one?"

**When loading alongside another skill** (e.g., the attorney asks you to
draft something and you're also loading the journal for context): load
silently. Don't show a status message or take over the conversation. Just
use the journal as context for the work.

**Long journals** (20+ log entries): Load the header plus the last 10
entries. Mention: "This matter has [N] entries going back to [date].
Say 'full history' if you need more."

## Logging

This is the heart of the system. There are three layers:

### Auto-Logging (primary mechanism)

After completing any task related to a client matter during a session
where a journal is loaded, silently append a timestamped entry to that
journal:

```markdown
### 2026-03-19

From bstevescherer/heycounsel-community, MIT.

More from bstevescherer/heycounsel-community

Signals

Stars
43
Forks
6
Open issues
0
Last commit (this folder)
Mar 23, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from bstevescherer

Cite this page

matter-journal skill. Agent Mart. https://agentmart.dev/skills/bstevescherer-matter-journal (last updated 2026-10-24)