Skip to content

docjacket-inc/docjacket

v0.9.2MIT

Connect your DocJacket transactions, tasks, deadlines, contacts, and contingencies to Codex and ChatGPT. Fourteen skills cover contract intake, inbox triage, document filing, morning briefings, closing prep, follow-ups, contacts, deal updates, Playbook building, workspace setup and compliance filing. Every email is shown to you in full and goes out only after you say yes (or after a team member approves it in DocJacket, if your organization reviews emails); tasks, dates and contacts update right away. Sign in to DocJacket over OAuth when you install; no token to paste. Call mcp_catalog after install for the live tool inventory.

closing-prep

Walks the standard pre-closing checks against a DocJacket transaction and reports what is done, what needs attention and what is missing, so the TC arrives at closing day with no surprises. Produces a pre-closing report grouped by status (complete / needs attention / overdue) and offers to send follow-ups or create tasks for any gaps. Use when the TC asks for a closing-prep check, a pre-closing review, or what is still open before a deal closes.

compliance-filing

Gets a DocJacket deal into the brokerage's compliance system (such as Dotloop, SkySlope or KW Command): finds which system the deal files in, prepares the deal's fields, parties and document names for that system, checks signed PDFs for blank signature, initials and date lines, and emails chosen documents to a Dotloop or SkySlope email-in address after the user approves a preview. Use when the TC asks to file, submit or set up a deal in Dotloop, SkySlope or another compliance system, or to check a document for missing signatures.

contact-management

Manages DocJacket contacts and links them to transactions: search, get, create and link. Use when the TC mentions contacts, parties, adding someone to a transaction, looking up an agent / lender / inspector / title company, or when a new party needs to be added during intake or email triage.

contract-intake

Walks a TC from a signed contract PDF to a fully set-up DocJacket transaction without leaving the chat: extract, review, apply, schedule, confirm. The result is a new transaction with parties, key dates, a checklist, intro emails previewed and confirmed (or waiting for a team member's approval), reminders scheduled, and a portal link the TC can share. Use when the TC has a new signed contract to intake or asks to build a deal from a contract.

daily-triage

Finds every DocJacket transaction that needs attention today and surfaces the next action per deal, as a bulleted list grouped by the urgency buckets the tool returns, most urgent first. Use when the TC asks what needs attention today, for a morning briefing, or for a triage of their active deals.

deal-updates

Keeps a live DocJacket deal accurate from chat: reads what is wrong with it, changes the deal record (price, financing, side, type, address, numbers, custom fields), manages key dates and their outcomes, records task outcomes with a 7-day undo, adds team notes and task or document comments, changes who holds a seat on the deal, restores an archived deal, and approves or rejects new deals waiting in the review queue. Use when the TC says something on a deal is wrong or changed, a deadline was met or waived, tasks are done or not needed, wants a note recorded, or asks what was said, sent or changed on a deal.

dj-cli

Reads DocJacket transactions, deadlines, tasks, documents and contacts through the dj command-line tool when the agent has a shell, answering from dj's JSON output and carrying transaction ids between commands. Use when the agent can run shell commands and the user asks about their DocJacket data. Chat clients without a shell use the DocJacket MCP tools instead.

document-filing

Helps the TC identify what each attachment is and which DocJacket transaction it belongs to. DocJacket's classifier suggests a document type; the TC decides where it is filed. Produces a "[filename] looks like [type] for [transaction]" prompt that notes when it fills a gap on the missing-documents list, with an optional follow-up task so the document gets uploaded. Use when the TC has attachments or documents to identify, classify or file to a deal.

email-triage

Cross-references the TC's Gmail or Outlook inbox against active DocJacket deals, groups matched email by transaction, and surfaces what needs the TC's attention as a per-transaction briefing of matched email, attachments and deadline proximity, with explicit asks for the TC's decisions. Use when the TC asks to triage their inbox, match emails to deals, or find which deal an email belongs to.

execution-workflow

Composes work in chat and carries it out in DocJacket. Emails are previewed to the user and sent only after an explicit yes via confirm_email_send (or wait in the DocJacket review queue for a team member); internal changes (tasks, key dates, reminders, contacts, Playbooks) run on call. Reports a status such as awaiting_confirmation, parked_for_review, queued, created or updated, plus a one-line summary of what was done or what is waiting; an email is never reported as on its way unless confirm_email_send returned status queued. Use when the TC asks to send an email, create or change tasks, update key dates, set reminders, add or update contacts, send calendar invites, or apply a Playbook.

follow-up-drafting

Composes chase emails for missing documents, approaching deadlines and unanswered communications, with tone calibrated to urgency and recipient. Shows the draft inline, asks for confirmation, calls the matching send_* tool for a preview, then calls confirm_email_send on the user's explicit yes; if the email was parked for review it reports that it is waiting for approval, not sent. Use when the TC asks to follow up, chase a document, nudge an agent or lender, or remind a party about a deadline.

playbook-builder

Builds a new DocJacket Playbook (a deal checklist of key dates, tasks, task emails and document lists) or changes one of the organization's own Playbooks, through the Playbook builder's draft tools. Everything is drafted first and saved only when the user approves the finished draft. Also explains why a Playbook task is or isn't on a deal. Use when the TC wants to set up their process, build or edit a checklist or Playbook, copy tasks between Playbooks, or asks why a task showed up on a deal.

tc-context

Grounds the agent in real-estate transaction-coordinator terminology, the DocJacket object model, and the safety rules that apply to every action taken on a transaction. Internal context that fires alongside other skills and produces no output of its own. Use whenever working with DocJacket transactions or when TC vocabulary comes up.

workspace-setup

Sets up and maintains a DocJacket organization from chat: the setup checklist, client agents and their TC fees and coordinators, organization settings, contact roles, document categories, custom fields, email templates and starter packs, online form templates, and the plan. Every change is confirmed with the user first, and most can be undone for 7 days. Use when the TC asks what to set up next, wants to set up their agents or fees, change a setting, manage templates or forms, or asks about their plan, limits or upgrading.