什么是 个人 CRM 构建指南？

个人 CRM 技能旨在引导用户演化出一套自定义的关系管理系统，且无需忍受企业级软件的臃肿。通过利用 Openclaw Skills，此工作流优先采用“文件先行”的方法，从轻量级的 JSON 或 CSV 文件开始，在引入技术复杂性之前验证您的数据模型。它确保您的联系人、线索和社交数据在本地目录中处于您的控制之下，作为一个随着您的需求而增长的唯一事实来源。

此技能专注于渐进式增强，从简单的联系人列表转向交互历史，并最终转向结构化数据库。它非常适合那些希望以高实用性、低摩擦的方式管理专业关系，同时在 Openclaw Skills 生态系统内保持对数据完整所有权的人开发人员和高级用户。

下载入口:https://github.com/openclaw/skills/tree/main/skills/ivangdavila/crm

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

个人 CRM 构建指南 应用场景

• 在没有复杂 SaaS 平台的情况下跟踪职业社交联系人和工作线索。
• 为初创公司和自由职业者管理投资者关系或客户管道。
• 建立互动、会议和随访的历史记录。
• 在文件操作变得缓慢时，将个人联系人列表扩展为完整的 SQLite 数据库。

1. 在 ~/crm/ 初始化一个专用目录，作为主要数据仓库。
2. 使用 JSON 或 CSV 定义最小联系人模式，以便立即进行数据录入和模型验证。
3. 一旦产生时间线或历史记录需求，添加通过联系人 ID 关联的交互历史文件。
4. 随着关系演变为多对多结构，将数据规范化到独立的组织和交易文件中。
5. 为命令行添加、搜索和自动备份实现辅助脚本。
6. 一旦查询复杂性或联系人数量需要更强大的索引，则迁移到结构化的 SQLite 数据库。

个人 CRM 构建指南 配置指南

要在您的环境中使用此技能，请创建本地存储目录并初始化您的主要数据文件：

mkdir -p ~/crm/
touch ~/crm/contacts.json

随后，AI 智能体将根据您是跟踪客户、线索还是个人社交联系人来帮助您填充模式。

个人 CRM 构建指南 数据架构与分类体系

该技能渐进地组织数据。以下是初始阶段使用的标准模式：

name: CRM
description: Guide users building a personal CRM from simple files to structured database.
metadata: {"clawdbot":{"emoji":"??","os":["linux","darwin","win32"]}}

First Interaction

• Ask what they're tracking: clients, leads, investors, job contacts, networking — context shapes schema
• Ask their technical comfort: spreadsheets, JSON, databases — determines starting format
• Create ~/crm/ folder as the single source of truth

Start With Files, Not Apps

• JSON or CSV for first version — validate data model before adding complexity
• Single file contacts.json initially — resist creating multiple files until needed
• Don't suggest web app until they've used files for at least a week
• Don't suggest database until files feel slow or limiting

Minimal Contact Schema

• id, name, email, company, phone, notes, tags, created, updated — nothing more initially
• tags array over rigid categories — flexible, no schema changes needed
• notes field is often the most valuable — encourage freeform context
• Generate UUID for id, not auto-increment — survives merges and imports

When To Add Interactions File

• User asks "when did I last talk to X" — signal they need history
• Separate file linked by contact_id — not nested in contact object
• type field (note/email/call/meeting) enables filtering later
• Always include date — timeline view is essential

When To Add Companies File

• Multiple contacts at same company — signal to separate
• Many-to-many: one person can work at multiple companies over time
• company_id in contacts, not company name duplication

When To Add Deals/Opportunities

• User mentions "pipeline", "stage", "close date", "deal value"
• Link to contact_id and optionally company_id
• Stages as simple string field initially — don't over-engineer state machine

SQLite Migration Triggers

• File operations feel slow (>100 contacts typically)
• User wants to query/filter in complex ways
• Multiple users need access (SQLite handles concurrent reads)
• Offer to write migration script — don't force manual re-entry

Progressive Timeline

• Week 1: contacts file only, prove they'll use it
• Week 2: add interactions when they want history
• Week 3: add tags, search helper script
• Month 2: companies file if needed
• Month 3: deals file if tracking opportunities
• Only then: consider web UI or more complex tooling

What NOT To Suggest Early

• Web application — massive scope increase, validate data model first
• Email sync/integration — suggest BCC/forward workflow, much simpler
• Calendar integration — manual logging is fine initially
• Authentication — single-user local CRM doesn't need it
• Mobile app — sync complexity not worth it early

Helper Scripts Worth Offering

• Quick add from command line — reduces friction
• Search across all files — grep/jq one-liner
• Backup to timestamped zip — essential before migrations
• Export to CSV — for users who want spreadsheet view

Data Integrity Habits

• Backup before any bulk edit or migration
• Check for duplicate emails before adding contact
• Validate email format on entry
• Keep created/updated timestamps — debugging lifesaver

Sync When Asked

• Cloud folder (Dropbox/iCloud/Drive) for multi-device — simplest
• Git repo for version history — good for technical users
• Don't suggest complex sync solutions until files prove insufficient