Plain-English rationale for each core skill. Use this as a reference when you want to know what a skill replaces and why we built one for it instead of doing the work manually.

Personal setup

2 skills
/setup-profile

Each lawyer's Cowork Personal Preferences (Profile) layer is per-user - your role, practice focus, response-style preference, named-client carriage, individual rules. Without something like this skill, every new lawyer has to either skip Profile entirely or guess at what to paste, and most end up with a stale or empty Profile that doesn't tailor Claude to how they actually work.

This skill walks you through 5 short questions one at a time, then generates a paste-ready Profile block of about 300 to 500 characters and shows you exactly where to paste it in Cowork Settings. Two minutes, one-time per lawyer. Firm-wide rules (Australian English, no em dashes, drafts rule, fraud escalation, privilege handling) inherit from workspace-tier Organization Instructions and are NOT duplicated in your Profile.

/setup-firm-hub

Stands up a new Firm Hub project from scratch (a second client, a new practice area, a UAE office) without hand-editing the Tier 0 Organization Instructions or the Hub's Project Instructions and Context file. Without it, every new Hub means re-authoring three blocks of firm-specific prose by hand: about 14 KB of jurisdiction defaults, register, stages, privilege framework, drafting timing, and sign-off. That's roughly 60 minutes per Hub if you know what you're doing, longer if you don't.

This skill is a 10-to-15-minute interactive wizard. Two modes: Mode A is first-firm setup (generates Tier 0 plus Hub Project Instructions plus Hub Context file from 12 questions); Mode B adds another Hub when Tier 0 is already in place (11 questions, no Tier 0 step). The country pick auto-derives language register (AU / UK / US English), privilege framework (Legal Professional vs Attorney-Client), the footer disclaimer, and citation defaults; you can override any of them. Outputs three paste-ready files saved to disk plus paste-ready text shown in chat. Re-run anytime; saved answers are offered as defaults on the next pass.

Setting up matters

3 skills
/setup-matter

Sets up a single new matter folder with the 8-subfolder structure, a CLAUDE.md instruction file (debtor name, scenario type, jurisdiction, claim amount), and a MATTER-STATUS.txt state file.

Every drafting skill reads from these two files - without them, skills like /create-lod-origin and /pleadings have no matter context and have to ask for information every time.

/bulk-setup-matter

Does what /setup-matter does, but across all ~150 existing Origin matter folders in one pass. Reads the Origin Matter Tracker to get the details for each matter, previews what it will do (you approve before anything is written), then seeds CLAUDE.md + MATTER-STATUS.txt into every folder that's missing them.

This is a one-time migration - you run it once when you first stand up the system against your existing matters.

/intake-batch

Origin sends a weekly Excel of 15-20 new referral accounts. Without this skill, that's Nat's day: open a folder, copy the debtor details, draft the LoD, repeat.

This reads the Excel, previews every row as a plan you approve, then creates the folder structure, populates the matter files, and generates the opening Letter of Demand for each row in one go. Fraud rows get a folder and a halt banner but no LoD - the skill knows not to draft against those.

Working a matter session

3 skills
/session-start

Reads MATTER-STATUS.txt and tells you where this matter is: current stage, last action, next action, and how many days until the next deadline. Takes under 10 seconds.

Without it you'd be opening files and reading back through notes to work out where you left off - this replaces that.

/session-checkpoint

A quick mid-session save. Updates MATTER-STATUS.txt with what's been done so far and appends a note to the session log.

Run it if you're switching tasks partway through a session and don't want to lose progress. Lighter than closing out - no continuation prompt, no git commit.

/session-close

The proper end-of-session close-out. Updates MATTER-STATUS.txt with the final state, writes a session entry to the log, propagates any changed facts (amounts, parties, dates) back into CLAUDE.md, and produces a one-line continuation prompt for next time.

This is what keeps the firm brief and dashboard current - if you skip it, the tracker doesn't know what happened in that session.

Across-the-firm visibility

4 skills
/hub-session-start

Loads the Firm Hub's configuration from the connected SharePoint folder so the Hub guardrails are in effect. A Hub Cowork project is a bare shell - its rules and reference data (CLAUDE.md and HUB-origin.md) live as files in the SharePoint folder it's connected to, because Cowork projects can't be shared but SharePoint files can. This skill reads them.

You rarely run it by hand - /firm-brief and /tracker-dashboard run it for you as their first step. If it ever says the config isn't there, the firm hasn't seeded it yet (someone runs /setup-firm-hub Mode B once) or OneDrive hasn't synced it down.

/firm-brief

A 60-line morning summary across all active Origin matters, sorted by urgency: overdue first, then due today, then due this week, then on hold, then everything else. Readable in under 2 minutes.

Replaces the habit of opening the tracker and sorting by date manually. It reads from the same consolidated file as the dashboard - so if you've been closing out sessions properly, this is always current.

/tracker-dashboard

Replaces the Excel tracker. Renders an interactive visual dashboard with 7 sections mirroring your existing daily-report format: Overdue, Due Today, Due This Week, ASIC Reinstatement, Awaiting Closure, Portfolio Snapshot, and Flags. Click any matter row to see the full detail.

One command refreshes everything: the dashboard auto-aggregates all 150 matter status files behind the scenes if the data is more than 24 hours old, then renders. Why not just keep the Excel? It's an xlsx file, which is secretly a zip archive - SharePoint sync conflicts and interrupted saves can corrupt the zip's internal table of contents (the "missing central directory" error). The dashboard has no file format to corrupt.

/conflict-sweep

Scans the Origin SharePoint tree for OneDrive sync conflict-copy files - the duplicate siblings OneDrive creates (-conflicted copy, -DESKTOP-..., numbered duplicates) when two people edit the same file inside the sync window. Lists each one by matter and offers to show the diff so a human reconciles it that day rather than weeks later.

It catches conflicts after the fact. What reduces how often they happen is the in-use mark /session-start writes and the timestamp guard in /session-close. Best run daily - by a person, or as a Cowork scheduled task. It never deletes matter content on its own.

Drafting

2 skills
/create-lod-origin

Origin debt-recovery uses three different Letter of Demand shapes depending on the scenario: standard account, collective account (franchise / multi-site), and unjust enrichment (no formal contract).

This skill reads the matter's scenario type from CLAUDE.md, picks the right template, fills in the debtor details, claim amount, jurisdiction, and applicable legislation, and drops a draft .docx in Correspondence (Drafts)/. Without it you'd be copy-pasting from a precedent and manually substituting every field.

/special-paths

Some matters can't go down the standard pipeline. ASIC Reinstatement (for deregistered companies that need to be reinstated before you can sue them), Skip Trace (when you can't locate the debtor), Substituted Service (when you can't serve them in person), and On Hold.

This skill sets a flag on the matter that makes ALL standard drafting skills halt on that file - so nothing goes out by accident - and generates the correct document for that alternative path instead.

Emergency

1 skill
/tracker-repair

Excel .xlsx files are zip archives with an internal table of contents. When a SharePoint sync conflict or interrupted save damages that table, Excel can't find anything inside the file and refuses to open it - that's the "missing central directory" or "Content Types" error.

This skill rebuilds the table from the surviving file content and writes a NEW repaired copy alongside the original. Your original file is never modified. Run it from the Firm Hub project: upload the broken file into the chat, then type /tracker-repair.

A note on .txt vs .json

The tracker snapshot is stored as tracker-snapshot.txt, not tracker-snapshot.json. That's intentional. Microsoft's SharePoint search index does not crawl .json files by default - so the Anthropic M365 connector can read .txt content but can't read .json content via SharePoint Graph Search. The snapshot uses .txt as the extension and JSON as the format. The skills that read it call JSON.parse() on the text content.