Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Bootstrap and manage an open, file-based CRM using the CRM-in-a-Box protocol (contacts, pipeline, interactions as NDJSON). Use when setting up a new CRM for...
Bootstrap and manage an open, file-based CRM using the CRM-in-a-Box protocol (contacts, pipeline, interactions as NDJSON). Use when setting up a new CRM for...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
An open, agent-native CRM protocol. One directory = one CRM. No vendor lock-in.
contacts.ndjson โ one JSON object per line, each a contact/company record pipeline.ndjson โ deal/opportunity tracking with stages interactions.ndjson โ append-only log of emails, calls, notes, meetings config.yaml โ pipeline stages and labels
Copy the baseline files into a company directory: mkdir -p ./mycompany/crm cp /path/to/crm-in-a-box/{config.yaml,contacts.ndjson,pipeline.ndjson,interactions.ndjson} ./mycompany/crm/ Or start fresh with empty NDJSON files and the default config.
{ "id": "c001", "name": "Jane Smith", "email": "jane@example.com", "company": "Acme Corp", "phone": "+1-555-0100", "stage": "new", "labels": ["hot-lead"], "notes": "Referred by John.", "created_at": "2026-01-01T00:00:00Z" }
{ "id": "p001", "contact_id": "c001", "stage": "proposal_sent", "deal": "Enterprise License", "value": 12000, "updated_at": "2026-01-15T00:00:00Z" }
{ "id": "i001", "contact_id": "c001", "type": "email", "summary": "Sent intro email about Denver market sale.", "at": "2026-01-15T10:00:00Z" }
new โ contacted โ meeting_scheduled โ proposal_sent โ negotiating โ won / lost
hot-lead, warm-lead, cold-lead, referral, conference, inbound, outbound
Log a contact: append a JSON line to contacts.ndjson Update a stage: append an updated entry to pipeline.ndjson (keep old entries โ append-only) Log an interaction: append to interactions.ndjson Search contacts: grep -i "name" contacts.ndjson | python3 -m json.tool List pipeline: cat pipeline.ndjson | python3 -c "import sys,json; [print(json.dumps(json.loads(l), indent=2)) for l in sys.stdin]"
Fork config.yaml to customize stages and labels for your vertical: pm-crm โ Property management (tenants, owners, vendors) saas-crm โ SaaS sales realestate-crm โ Buyers, sellers, listings recruiting-crm โ Candidates, jobs, placements Part of the biz-in-a-box family of open protocols.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.