Mini-Mike is a set of AI skills built specifically for legal work, plugging into Claude — via Claude Cowork or Claude Code — so lawyers get the precision their work demands without leaving the platform they already use.
Built by allNeurons — a team of MAANG engineers and practicing lawyers.
Every output is a draft for attorney review — cited, flagged, and gated — not a legal conclusion. The skills read the documents, extract the fields, and cite every cell back to the source. A lawyer reviews, verifies, and takes responsibility. That review is faster because of this plugin; it is not skipped because of it.
| Role | Use it for |
|---|---|
| In-house counsel / GC reviewing vendor, customer, or lease contracts | mm-tabular-review for the General Key Terms pass |
| M&A counsel / real estate counsel running lease-heavy diligence | mm-tabular-review + the mm-coc-tabular-review Change of Control deep-dive |
| Legal ops / paralegals prepping diligence binders or contract summaries at volume | mm-tabular-review batch mode (5 documents at a time) |
- Open the Cowork tab, then open Customize in the left sidebar. (In chat on web or Desktop, just open Customize directly.)
- Go to the Plugins tab.
- Under Personal plugins, click +, then Add marketplace → Add from a repository.
- Enter the repository:
allNeurons-AI/mini-mike(or the full URL,https://github.com/allNeurons-AI/mini-mike). - Click Browse plugins, find
mini-mike, and click Install. - Try it: upload a contract and ask for a review, or type
/to findmini-mike:mm-tabular-review.
- Add the marketplace:
/plugin marketplace add allNeurons-AI/mini-mike - Install the plugin:
/plugin install mini-mike@allneurons - Activate it: run
/reload-pluginsto pick up the change without restarting, or just restart Claude Code. - Try a skill:
/mini-mike:mm-tabular-review, or just upload a contract and ask for a review.
In Claude Code, when asked to choose an installation scope, pick user scope (install for yourself across all projects) rather than project or local scope — those limit the plugin to reading files inside that one project folder (your contract PDFs in Downloads, a client file in Dropbox, wouldn't be reachable). Cowork/chat installs don't ask this.
Full walkthrough and troubleshooting: QUICKSTART.md.
- Start a new chat or task wherever you installed the plugin (Cowork, chat on web/Desktop, or Claude Code).
- Upload the contract(s) you want reviewed — one file or a batch, drag-and-drop or attach.
- Ask for a review, e.g. "review this contract" or "give me a tabular review of these" — or invoke it directly with
/mini-mike:mm-tabular-review. - Answer the setup question: the skill asks whether to use the default General Key Terms (20 columns) or your own custom key terms. Pick default for your first run.
- If a file is password-protected, the skill pauses and asks for the password or whether to skip that file.
- Partway through, it asks about Change of Control: say yes for the CoC deep-dive (adds Sheet 2, and asks the same default-vs-custom question for its 19 fields), or no to skip straight to the summary.
- Get your workbook: an Excel file with General Key Terms (Sheet 1), CoC analysis if you said yes (Sheet 2), and a Summary of deal-team action items (Sheet 3) — every cell cited back to the source document.
Since there's no saved config yet, every run asks the default-vs-custom questions fresh — see "How it learns" below for the roadmap on that.
| Command | Does |
|---|---|
/mini-mike:mm-tabular-review |
General Key Terms tabular review (Sheet 1, 20 columns) + Summary sheet (Sheet 3) of deal-team action items. Batches documents in groups of five. Offers a Change of Control hand-off partway through. |
/mini-mike:mm-coc-tabular-review |
Change of Control / Transfer deep-dive (Sheet 2), 19 fields. Normally invoked automatically by mm-tabular-review's CoC gate; can also be run standalone. |
None. Both skills operate on documents you upload or point them at directly (local files, pasted text) — no connector or config file is required to run either one. The recommended connectors below are optional conveniences, not dependencies.
| Skill | Type | Purpose |
|---|---|---|
| mm-tabular-review | Parent | Reviews one or more commercial contracts, produces a structured Excel workbook: General Key Terms (Sheet 1, section-cited) + Summary (Sheet 3). Asks up front: default key terms or custom. Handles password-protected files and contracts with amendments. |
| mm-coc-tabular-review | Child (of mm-tabular-review) |
Change of Control / Transfer Key-Terms Analysis (Sheet 2) — one answer row + one citation row per document across 19 M&A-critical fields, or custom fields. Derives the CoC risk rating consumed by Sheet 3. |
Today: both skills are plain markdown under skills/<name>/SKILL.md. There's no build step — fork the file and edit the steps, the gates, the column definitions, or the output format directly for house style. That's the whole customization mechanism right now.
Broader mechanism: Mini-Mike is built to be community-driven — when a team finds a gap or a better default, that improvement is meant to fold back into the shipped skill for everyone, not stay siloed in one firm's fork. The contribution path for that is in CONTRIBUTING.md.
- Every extracted cell is a citation-backed lead, not a finding. Verify against the source document before it informs a rep, schedule, or memo.
mm-coc-tabular-review's default 19 fields are shaped for retail/commercial leases (store number, landlord, landlord parent, lease expiry). Accurate out of the box for that use case; for other contract types, use the custom-fields path at the Phase 0 gate until a second default field set ships.- Password-protected PDFs: the skill pauses mid-batch and asks for the password or whether to skip that file. Expected behavior, not a bug.
- Documents are processed in batches of five by default.
More sub-skills, driven by community/practitioner feedback. Planned next:
- Due Diligence Issue Extraction — read VDR docs, extract issues per house categories/materiality thresholds into house memo format.
- Renewal Tracker — surfaces contracts with upcoming cancel-by deadlines from a maintained renewal register.
- Entity Compliance — filing deadlines by entity/jurisdiction, 30/60/90-day lookahead, CSV export.
- Amendment History — traces how a contract changed across a base agreement + amendments.
- Board Minutes — drafts board/committee minutes from calendar-detected meetings + agenda materials.
Planned agents:
- Playbook Monitor — proposes playbook updates once a clause position has been deviated from enough times.
- Renewal Watcher — scheduled weekly post of upcoming renewals to a configured channel.
- Data Room Watcher — monitors a VDR for new uploads, posts closing checklist status.
Planned connectors: Google Drive, Slack, DocuSign, Microsoft 365.
- Fork a skill for house style. Every skill is a markdown file under
skills/<name>/SKILL.md. Edit the steps, the gates, the column/field definitions, or the output format directly. - Swap or add connectors. Point
.mcp.jsonat your own Drive, Slack, DocuSign, or other MCP-compatible tool. Neither shipped skill calls a connector yet, so nothing breaks if you leave it as-is — this is forward-provisioning for skills and agents that will use them. - Add your own field/column set. Both skills have a Phase 0 gate that asks default vs. custom fields — if your house default differs from the shipped one (e.g., the CoC skill's retail-lease-shaped 19 fields), answer with your own set each run, or fork the skill to make your set the default.
- Track your changes against upstream. Since this repo will get community contributions (see Contributing below), keep your house fork on a branch or a private overlay so upstream updates don't silently clobber your edits.
No build step. Everything is markdown and JSON.
Everything here is markdown and JSON — fork, edit, open a pull request. Full details in CONTRIBUTING.md, but the short version:
- New skill → add it under
skills/<skill-name>/SKILL.mdwith the frontmatter the existing skills use (name,description). Keep the description tight — it's the trigger signal the model uses to decide when to invoke the skill. - New agent → add
agents/<name>.mdwith scheduling frontmatter and the system prompt describing what it watches and what it does when triggered. - Nothing goes live without allNeurons review. Unlike a local fork, a pull request into this repo only ships in the installable marketplace once an allNeurons maintainer has reviewed and approved it. Branch protection +
CODEOWNERSonmainenforce this — there's no self-merge and no automatic publish path for outside contributors. Open the PR, and a maintainer will review, request changes if needed, and merge when it's ready.
- It does not replace a lawyer reading the contract. Every extracted cell is a citation-backed lead, not a finding — verify against the source before it informs a rep, schedule, or memo.
- It does not yet have a practice profile or cold-start interview — every run asks its setup questions fresh (default vs. custom key terms, etc.) rather than remembering your answer from last time. That's the top roadmap item.
Early stage — v0.1.0. First skill pair (mm-tabular-review parent + mm-coc-tabular-review child) is live.
Apache License 2.0 — see LICENSE.