Step 2 — Install the plugin
Pick a path. Both end with the same working engine.
Option A — Hands-free (recommended)
Paste this one-liner into Terminal. It downloads the latest zip, drops it into Claude Desktop's plugins dir, writes your key, and relaunches Desktop — no clicking through menus, safely re-runs if you already had an old version.
curl -fsSL https://raw.githubusercontent.com/mrdulasolutions/RevOps-RevAMfg/main/plugin/scripts/desktop-install.sh | REVA_API_KEY=<your nk_... key from Step 1> bash
Already inside Claude?
If you have the Control your Mac connector
enabled (Desktop → Settings → Connectors), just say
/heal in any chat and Claude runs the one-liner
for you — truly hands-free.
Option B — Manual upload
- Download
reva-turbo-<version>.zip(v2.1.3+) from GitHub Releases. Don't unzip. - If you already have RevAOps installed (v2.0.x or earlier), go to
Plugins → Installed → RevAOps → ⋯ → Remove,
then quit Desktop (
Cmd-Q) and relaunch. The uploader doesn't auto-upgrade — skipping this leaves you on a stale launcher and the engine won't load your key. - Claude Desktop → Plugins → Personal → Local uploads → + and drop in the zip. Click Enable. No settings to fill in — you'll paste your key in Step 3.
crm_* /
mem_* / reva_*). Duplicates show up as
raw search_contacts / memory_recall
names and break intent routing.
Step 3 — Run the engine & paste your key
In any Claude Desktop chat, type:
/reva-turbo:revmyengine
The engine greets you and notices it doesn't have a key yet. Reply with:
/connect <paste your nk_... key here>
The engine validates the key against the router, saves it to
your local config, and tells you to quit & reopen Claude
Desktop (Cmd-Q, relaunch). That one restart is the
only manual step — after it, say "let's go" and you're in.
Behind the scenes: the plugin is already connected to the shared Rev A workspace, so it asks exactly one question (what's your role?) and pulls company profile, partners, and pipelines from the router — no local setup.
Already using HubSpot, Salesforce, Attio, or Pipedrive?
You can keep your existing CRM as the system of record. After Step 3, run:
/integrate hubspot (or salesforce / attio / pipedrive)
Skills will then write to your CRM
first and shadow-write to Nakatomi + AutoMem so the shared Rev A
timeline stays complete. Reads prefer your CRM and fall back to
Nakatomi if it's unreachable. Revert any time with
/integrate nakatomi.
Need to do this from a terminal instead? CLI install flow →