Personal Crm
How to work in a Personal CRM project (the `entity-vault` starter pack...
Install
npx skills add inkeep/open-knowledge --skill personal-crm -g -a claude-code -y- Repository
- inkeep/open-knowledge4.8k
- Category
- Writing
- Updated
- 4d ago
- License
- GPL-3.0
- Context cost
- Lightabout 1,412 tokens
- Runs scripts
- No, instructions only
What it does
How to work in a Personal CRM project (the `entity-vault` starter pack, GBrain-compatible): a typed-entity vault of people, companies, meetings, and concepts, each a dossier with a rewritable summary plus an append-only timeline. Read when the project has these folders, OR when asked to capture notes about a person or company, log a meeting, prep for an upcoming meeting, or answer who someone is and what was last said. Carries the dossier convention and entity-extraction behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.
Personal CRM (GBrain-compatible), how to work here
A Personal CRM built as a typed-entity vault, inspired by Garry Tan's gbrain. Each entity is a dossier; the agent keeps dossiers current by extracting entities from meeting notes and original thinking. This skill holds those behaviors so templates and folder descriptions stay clean. The Markdown shape is GBrain-compatible: if the external gbrain CLI is installed, it can import/sync the same vault.
This skill is pack guidance. The platform
/open-knowledgeskill (read/write/preview/linking/grounding rules) still governs every markdown operation, this layers the dossier conventions on top.
The dossier convention (the load-bearing rule)
Every dossier in people/, companies/, and concepts/ has two parts, split by an explicit --- timeline --- separator:
- Compiled truth (above
--- timeline ---), your current best understanding. Rewrite it as new evidence changes the synthesis. - Timeline (below
--- timeline ---), append-only dated bullets in the parseable form- **YYYY-MM-DD** | source | @author, evidence. Confidence: …. Never edit existing timeline entries; only append.
When a new fact arrives, route it: update compiled truth if it changes current understanding, or append a timeline bullet if it's raw evidence. The explicit separator and dated-bullet shape are what keep the vault parseable by GBrain's import/sync.
