dex-skill

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Dex Personal CRM

Dex个人CRM

Dex is a personal CRM that helps users maintain and nurture their professional relationships. It tracks contacts, interaction history, reminders, and organizational structures (groups, tags, custom fields).

Dex是一款个人CRM，帮助用户维护和培养职业人脉关系。它可以跟踪联系人、互动历史、提醒事项以及组织结构（群组、标签、自定义字段）。

Setup — Detect Access Method

设置——检测访问方式

Check which access method is available, in this order:

MCP tools available? If
```
dex_search_contacts
```
and other
```
dex_*
```
tools are in the tool list, use MCP tools directly. This is the preferred method — skip CLI setup entirely.
CLI installed? Check if
```
dex
```
command exists (run
```
which dex
```
or
```
dex auth status
```
). If authenticated, use CLI commands.
Neither? Guide the user through setup.

按以下顺序检查可用的访问方式：

是否有MCP工具？ 如果工具列表中包含
```
dex_search_contacts
```
及其他
```
dex_*
```
工具，直接使用MCP工具。这是首选方式——完全跳过CLI设置。
是否安装了CLI？ 检查是否存在
```
dex
```
命令（运行
```
which dex
```
或
```
dex auth status
```
）。如果已认证，使用CLI命令。
都没有？ 引导用户完成设置。

First-Time Setup

首次设置

Path A — Platform supports MCP (Claude Desktop, Cursor, VS Code, Gemini CLI, etc.):

If the user already has the Dex MCP server configured, or their platform can add MCP servers:

bash

npx -y add-mcp https://mcp.getdex.com/mcp -y

This auto-detects installed AI clients and configures the Dex MCP server for all of them. User authenticates via browser on first MCP connection.

Path B — Install CLI:

bash

npm install -g @getdex/cli

Works with npm, pnpm, and yarn. No postinstall scripts — the binary is bundled in a platform-specific package.

Path C — No Node.js:

Direct the user to follow the setup guide at https://getdex.com/docs/ai/mcp-server — it has client-specific instructions for Claude Desktop, Claude Code, Cursor, VS Code, and other MCP-capable clients.

路径A——平台支持MCP（Claude Desktop、Cursor、VS Code、Gemini CLI等）：

如果用户已配置Dex MCP服务器，或其平台可添加MCP服务器：

bash

npx -y add-mcp https://mcp.getdex.com/mcp -y

这会自动检测已安装的AI客户端，并为所有客户端配置Dex MCP服务器。用户在首次连接MCP时通过浏览器完成认证。

路径B——安装CLI：

bash

npm install -g @getdex/cli

支持npm、pnpm和yarn。无安装后脚本——二进制文件捆绑在特定平台的包中。

路径C——无Node.js环境：

引导用户遵循**https://getdex.com/docs/ai/mcp-server**上的设置指南——其中包含针对Claude Desktop、Claude Code、Cursor、VS Code及其他支持MCP的客户端的专属说明。

Authentication

身份验证

Triggered by

/dex-login

or on first use when not authenticated. Ask the user which method they prefer:

Option 1 — API Key:

User generates a key at Dex Settings > Integrations (requires Professional plan)
For CLI:
```
dex auth --token dex_your_key_here
```
Key is saved to
```
~/.dex/api-key
```
(chmod 600)

Option 2 — Device Code Flow (works on remote/headless machines):

Drive this flow directly via HTTP — no browser needed on the machine:

Request a device code:

bash

curl -s -X POST https://mcp.getdex.com/device/code -H "Content-Type: application/json"

Response:

{ "device_code": "...", "user_code": "ABCD-EFGH", "verification_uri": "https://...", "expires_in": 600, "interval": 5 }

Show the user the
```
user_code
```
and
```
verification_uri
```
. They open the URL on any device with a browser, log in to Dex, and enter the code.

Poll for approval every 5 seconds:

bash

curl -s -X POST https://mcp.getdex.com/device/token \
  -H "Content-Type: application/json" \
  -d '{"device_code": "<device_code>"}'

```
{"error": "authorization_pending"}
```
→ keep polling
```
{"api_key": "dex_..."}
```
→ done, save the key

Save the API key:

bash

mkdir -p ~/.dex && echo "<api_key>" > ~/.dex/api-key && chmod 600 ~/.dex/api-key

For CLI:

dex auth --token <api_key>

For CI/automation with no human present, use the API key method with

DEX_API_KEY

environment variable.

当用户输入

/dex-login

或首次使用未认证时触发。询问用户偏好的认证方式：

选项1——API密钥：

用户在Dex设置>集成生成密钥（需专业版计划）
对于CLI：
```
dex auth --token dex_your_key_here
```
密钥将保存至
```
~/.dex/api-key
```
（权限设置为chmod 600）

选项2——设备码流程（适用于远程/无头机器）：

直接通过HTTP完成此流程——机器上无需浏览器：

请求设备码：

bash

curl -s -X POST https://mcp.getdex.com/device/code -H "Content-Type: application/json"

响应：

{ "device_code": "...", "user_code": "ABCD-EFGH", "verification_uri": "https://...", "expires_in": 600, "interval": 5 }

向用户展示
```
user_code
```
和
```
verification_uri
```
。用户在任何带浏览器的设备上打开该URL，登录Dex并输入代码。

每5秒轮询一次审批状态：

bash

curl -s -X POST https://mcp.getdex.com/device/token \
  -H "Content-Type: application/json" \
  -d '{"device_code": "<device_code>"}'

```
{"error": "authorization_pending"}
```
→ 继续轮询
```
{"api_key": "dex_..."}
```
→ 完成，保存密钥

保存API密钥：

bash

mkdir -p ~/.dex && echo "<api_key>" > ~/.dex/api-key && chmod 600 ~/.dex/api-key

对于CLI：

dex auth --token <api_key>

对于无人工参与的CI/自动化场景，使用API密钥方法并设置

DEX_API_KEY

环境变量。

Data Model

数据模型

Contact
├── Emails, Phone Numbers, Social Profiles
├── Company, Job Title, Birthday, Website
├── Description (rich text notes about the person)
├── Tags (flat labels: "Investor", "College Friend")
├── Groups (collections with emoji + description: "🏢 Acme Team")
├── Custom Fields (user-defined: input, dropdown, datepicker)
├── Notes/Timeline (interaction log: meetings, calls, coffees)
├── Reminders (follow-up tasks with optional recurrence)
└── Starred / Archived status

Contact
├── Emails, Phone Numbers, Social Profiles
├── Company, Job Title, Birthday, Website
├── Description (rich text notes about the person)
├── Tags (flat labels: "Investor", "College Friend")
├── Groups (collections with emoji + description: "🏢 Acme Team")
├── Custom Fields (user-defined: input, dropdown, datepicker)
├── Notes/Timeline (interaction log: meetings, calls, coffees)
├── Reminders (follow-up tasks with optional recurrence)
└── Starred / Archived status

Using Tools

使用工具

MCP Mode

MCP模式

Call

dex_*

tools directly. All tools accept and return JSON.

直接调用

dex_*

工具。所有工具均接受并返回JSON格式数据。

CLI Mode

CLI模式

Use the

dex

command. CLIHub generates subcommands from MCP tool names (replacing

with

bash

dex dex-search-contacts --query "John"
dex dex-list-contacts --limit 100
dex dex-create-contact --first-name "Jane" --last-name "Doe"
dex dex-list-tags
dex dex-create-reminder --text "Follow up" --due-at-date "2026-03-15"

Use

--output json

for machine-readable output,

--output text

(default) for human-readable.

Run

dex --help

for all commands, or

dex <command> --help

for command-specific help.

See CLI Command Reference for the full mapping table of all 38 tools to CLI commands.

使用

dex

命令。CLIHub会根据MCP工具名称生成子命令（将

替换为

）：

bash

dex dex-search-contacts --query "John"
dex dex-list-contacts --limit 100
dex dex-create-contact --first-name "Jane" --last-name "Doe"
dex dex-list-tags
dex dex-create-reminder --text "Follow up" --due-at-date "2026-03-15"

使用

--output json

获取机器可读输出，

--output text

（默认）获取人类可读输出。

运行

dex --help

查看所有命令，或

dex <command> --help

查看特定命令的帮助信息。

查看**CLI命令参考**获取全部38个工具到CLI命令的完整映射表。

Core Workflows

核心工作流

1. Find a Contact

1. 查找联系人

search → get details (with notes if needed)

Search by name, email, company, or any keyword
Use empty query to browse recent contacts (sorted by last interaction)
Use
```
dex_list_contacts
```
for bulk iteration (up to 500 per page, cursor-paginated)
Include
```
include_notes: true
```
when user needs interaction history

搜索 → 获取详情（如需可包含笔记）

按姓名、邮箱、公司或任意关键词搜索
使用空查询浏览最近联系人（按最后互动时间排序）
使用
```
dex_list_contacts
```
进行批量遍历（每页最多500条，默认100条）
当用户需要互动历史时，设置
```
include_notes: true
```

2. Add a New Contact

2. 添加新联系人

create contact → (optionally) add to groups → apply tags → set reminder

Create with whatever info is available (no fields are strictly required)
Immediately organize: add relevant tags and groups
Set a follow-up reminder if the user just met this person

创建联系人 →（可选）添加到群组 → 添加标签 → 设置提醒

可使用已有信息创建联系人（无必填字段）
立即整理：添加相关标签和群组
如果用户刚结识此人，设置跟进提醒

3. Log an Interaction

3. 记录互动

(optional) list note types → create note on contact timeline

Discover note types first with
```
dex_list_note_types
```
to pick the right one (Meeting, Call, Coffee, Note, etc.)
Set
```
event_time
```
to when the interaction happened, not when logging it
Keep notes concise but capture key details, action items, and personal context

（可选）列出笔记类型 → 在联系人时间线创建笔记

先使用
```
dex_list_note_types
```
查看笔记类型，选择合适的类型（会议、通话、咖啡、普通笔记等）
将
```
event_time
```
设置为互动发生的时间，而非记录时间
笔记应简洁但需包含关键细节、行动项和个人背景信息

4. Set a Reminder

4. 设置提醒

create reminder → (link to contact if applicable)

Always require
```
due_at_date
```
(ISO format: "2026-03-15")
Use
```
text
```
for the reminder description — there is no separate title field

Recurrence options:

weekly

biweekly

monthly

quarterly

biannually

yearly

创建提醒 →（如适用）关联到联系人

必须指定
```
due_at_date
```
（ISO格式："2026-03-15"）
使用
```
text
```
字段作为提醒描述——无单独标题字段
重复选项：
```
weekly
```
（每周）、
```
biweekly
```
（每两周）、
```
monthly
```
（每月）、
```
quarterly
```
（每季度）、
```
biannually
```
（每半年）、
```
yearly
```
（每年）

5. Organize Contacts

5. 整理联系人

Tags — flat labels for cross-cutting categories:

create tag → add to contacts (bulk)

Groups — named collections with emoji and description:

create group → add contacts (bulk)

Best practice: Use tags for attributes ("Investor", "Engineer", "Met at Conference X") and groups for relationship clusters ("Startup Advisors", "Book Club", "Acme Corp Team").

标签——用于跨类别分类的扁平标签：

创建标签 →（批量）添加到联系人

群组——带表情和描述的命名集合：

创建群组 →（批量）添加联系人

最佳实践：使用标签表示属性（如“投资者”、“工程师”、“在X会议结识”），使用群组表示关系集群（如“创业顾问”、“读书俱乐部”、“Acme公司团队”）。

6. Manage Custom Fields

6. 管理自定义字段

list fields → create field definition → batch set values on contacts

Three field types:
```
input
```
(free text),
```
autocomplete
```
(dropdown with options),
```
datepicker
```
Use
```
dex_set_custom_field_values
```
to set values on multiple contacts at once
For autocomplete fields, provide
```
categories
```
array with the allowed options

列出字段 → 创建字段定义 → 批量为联系人设置值

三种字段类型：
```
input
```
（自由文本）、
```
autocomplete
```
（带选项的下拉菜单）、
```
datepicker
```
（日期选择器）
使用
```
dex_set_custom_field_values
```
为多个联系人批量设置值
对于autocomplete字段，提供包含允许选项的
```
categories
```
数组

7. Meeting Prep

7. 会议准备

When a user says "I have a meeting with X":

Search for the contact
Get full details with
```
include_notes: true
```
Check recent reminders for pending items
Summarize: last interaction, key notes, pending follow-ups, shared context
See CRM Workflows for detailed meeting prep guidance

当用户说“我要和X开会”时：

搜索该联系人
设置
```
include_notes: true
```
获取完整详情
检查最近的提醒事项
总结：上次互动内容、关键笔记、待办跟进事项、共享背景
查看CRM工作流获取详细的会议准备指南

8. Merge Duplicates

8. 合并重复联系人

search for potential duplicates → confirm with user → merge

First ID in each group becomes the primary — all other data merges into it
Always confirm with the user before merging (destructive operation)
Can merge multiple groups in a single call

搜索潜在重复联系人 → 与用户确认 → 合并

每组中的第一个ID将成为主ID——所有其他数据合并到该联系人中
合并前务必与用户确认（此操作不可撤销）
可在单次调用中合并多组重复联系人

Important Patterns

重要模式

Pagination

分页

List operations use cursor-based pagination:

```
dex_list_contacts
```
: default 100 per page, max 500
```
dex_search_contacts
```
: default 50 per page, max 200
Other list tools: default 10 per page
Check
```
has_more
```
in response
Pass
```
next_cursor
```
from previous response to get next page
Iterate until
```
has_more: false
```
to get all results

列表操作使用基于游标（cursor）的分页：

```
dex_list_contacts
```
：默认每页100条，最多500条
```
dex_search_contacts
```
：默认每页50条，最多200条
其他列表工具：默认每页10条
检查响应中的
```
has_more
```
字段
传递上一次响应中的
```
next_cursor
```
获取下一页
循环直到
```
has_more: false
```
获取所有结果

Destructive Operations

破坏性操作

Always confirm with the user before:

Deleting contacts (
```
dex_delete_contacts
```
)
Merging contacts (
```
dex_merge_contacts
```
)
Deleting tags, groups, notes, reminders, or custom fields

执行以下操作前务必与用户确认：

删除联系人（
```
dex_delete_contacts
```
）
合并联系人（
```
dex_merge_contacts
```
）
删除标签、群组、笔记、提醒或自定义字段

Response Truncation

响应截断

Responses are capped at 25,000 characters. If truncated, the response preserves pagination metadata (

next_cursor

has_more

) so you can fetch the next page. Use smaller

limit

values if responses are being truncated.

响应上限为25000字符。如果被截断，响应会保留分页元数据（

next_cursor

、

has_more

），以便获取下一页。如果响应被截断，使用更小的

limit

值。

Date Formats

日期格式

All dates: ISO 8601 strings (e.g.,
```
"2026-03-15"
```
,
```
"2026-03-15T14:30:00Z"
```
)
Birthdays:
```
YYYY-MM-DD
```
Reminder due dates:
```
YYYY-MM-DD
```

所有日期：ISO 8601字符串（例如
```
"2026-03-15"
```
、
```
"2026-03-15T14:30:00Z"
```
）
生日：
```
YYYY-MM-DD
```
提醒截止日期：
```
YYYY-MM-DD
```

Detailed References

详细参考

Tool Reference — Complete parameter documentation for every tool, with examples
CLI Command Reference — Full MCP tool → CLI command mapping table (only needed for CLI mode)
CRM Workflows — Relationship management best practices, follow-up cadences, and strategies for being an effective CRM assistant

工具参考——所有工具的完整参数文档及示例
CLI命令参考——MCP工具到CLI命令的完整映射表（仅CLI模式需要）
CRM工作流——人脉管理最佳实践、跟进节奏，以及成为高效CRM助手的策略