Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Content Creation
CRM
Guide users building a personal CRM from simple files to structured database.
skill openclawclawhub Free
Guide users building a personal CRM from simple files to structured database.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
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. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
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
Category context
Writing, remixing, publishing, visual generation, and marketing content production.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md