entity-vault

Name: entity-vault
Author: inkeep

3.1kstars191forks

How to install entity-vault?

inkeep/open-knowledge/entity-vault

$npx -y skills add inkeep/open-knowledge --skill entity-vault

Installs into the current project.

Summary

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. Carries t

Files · 1

View on GitHub

SKILL.md

1	# Personal CRM (GBrain-compatible) — how to work here
2
3	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.
4
5	> Pack guidance. The platform `open-knowledge` skill still governs every markdown operation.
6
7	## The dossier convention (the load-bearing rule)
8
9	Every dossier in `people/`, `companies/`, and `concepts/` has two parts, split by an explicit `--- timeline ---` separator:
10
11	1. Compiled truth (above `--- timeline ---`) — your current best understanding. Rewrite it as new evidence changes the synthesis.
12	2. 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.
13
14	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.
15
16	## Folders
17
18	- `people/`, `companies/`, `concepts/` — dossiers (compiled truth + timeline). Frontmatter `type: person\|company\|concept`.
19	- `meetings/` — meeting notes (`YYYY-MM-DD-<slug>.md`); `attendees:` should match dossier filenames in `people/`. The verbatim record — do NOT rewrite it. When a note is ingested from a meeting-recorder tool, add `source:` (e.g. `granola`, `fireflies`) and `source_meeting_id:` (the recorder's stable id) to its frontmatter — those two are the dedup key.
20	- `originals/` — your own untransformed thinking; authoritative source material. Frontmatter `type: original`.
21	- `media/` — bulk transcripts, voice notes, large attachments; often `.okignore`-d to keep the index light.
22
23	## Links
24
25	Per the platform skill, prefer standard markdown links for new dossiers, and count the relative depth carefully for the cross-folder links this vault is full of — e.g. `[Alice Chen](../people/alice-chen.md)` from a `meetings/` note, `[Acme AI](../companies/acme-ai.md)` from a `people/` dossier. The write/edit `brokenLinks` response catches a wrong-depth path before you walk away. New brain pages render on GitHub, satisfy OK's `brokenLinks` check, and import cleanly into GBrain.
26
27	Two deltas from the platform default, both GBrain-specific:
28
29	- Don't use the leading-slash root-absolute form (`[Alice](/people/alice-chen.md)`). OK resolves it fine, but GBrain reads a leading `/` as an absolute filesystem path and rejects it — use a relative path. (GBrain also accepts a bare `[Alice](people/alice-chen.md)`, but from a subfolder OK resolves that source-dir-relative — `meetings/people/alice-chen` — and reports it broken, so stick to the `../`-correct relative form, which both accept.)
30	- Path-qualified wikilinks are first-class here, not legacy: `[[people/alice-chen\|Alice Chen]]` resolves vault-root from any folder (no `../` to count), is validated by `brokenLinks` like any link, and imports into GBrain. Keep them extensionless (`[[people/alice-chen]]`, never `[[people/alice-chen.md]]` — the `.md` makes it resolve to a nonexistent doc). A bare `[[note-name]]` with no folder is ambiguous (resolves only if GBrain's basename-globbing is on) — reserve it for Obsidian migration.
31
32	## Agent behaviors
33
34	- Ingest from a meeting recorder. If a meeting-recorder MCP (Granola, Fireflies, Circleback, tl;dv, Fathom, …) is registered alongside `open-knowledge`, pull recent meetings and write each into `meetings/`. Address each as `meetings/<source>-<source_meeting_id>` so re-syncing a meeting updates it in place instead of creating a duplicate. Normalize whatever the recorder returns (Granola's Me/Them streams, a bot's speaker turns) into notes plus the verbatim transcript; do NOT rewrite the transcript. This works the same on demand (you ask) or u

People who liked this also viewed

6 picks

Type

entity-vault

3.1kstars191forks

View on GitHub

How to install entity-vault?

inkeep/open-knowledge/entity-vault

$npx -y skills add inkeep/open-knowledge --skill entity-vault

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Personal CRM (GBrain-compatible) — how to work here
2
3	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.
4
5	> Pack guidance. The platform `open-knowledge` skill still governs every markdown operation.
6
7	## The dossier convention (the load-bearing rule)
8
9	Every dossier in `people/`, `companies/`, and `concepts/` has two parts, split by an explicit `--- timeline ---` separator:
10
11	1. Compiled truth (above `--- timeline ---`) — your current best understanding. Rewrite it as new evidence changes the synthesis.
12	2. 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.
13
14	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.
15
16	## Folders
17
18	- `people/`, `companies/`, `concepts/` — dossiers (compiled truth + timeline). Frontmatter `type: person\|company\|concept`.
19	- `meetings/` — meeting notes (`YYYY-MM-DD-<slug>.md`); `attendees:` should match dossier filenames in `people/`. The verbatim record — do NOT rewrite it. When a note is ingested from a meeting-recorder tool, add `source:` (e.g. `granola`, `fireflies`) and `source_meeting_id:` (the recorder's stable id) to its frontmatter — those two are the dedup key.
20	- `originals/` — your own untransformed thinking; authoritative source material. Frontmatter `type: original`.
21	- `media/` — bulk transcripts, voice notes, large attachments; often `.okignore`-d to keep the index light.
22
23	## Links
24
25	Per the platform skill, prefer standard markdown links for new dossiers, and count the relative depth carefully for the cross-folder links this vault is full of — e.g. `[Alice Chen](../people/alice-chen.md)` from a `meetings/` note, `[Acme AI](../companies/acme-ai.md)` from a `people/` dossier. The write/edit `brokenLinks` response catches a wrong-depth path before you walk away. New brain pages render on GitHub, satisfy OK's `brokenLinks` check, and import cleanly into GBrain.
26
27	Two deltas from the platform default, both GBrain-specific:
28
29	- Don't use the leading-slash root-absolute form (`[Alice](/people/alice-chen.md)`). OK resolves it fine, but GBrain reads a leading `/` as an absolute filesystem path and rejects it — use a relative path. (GBrain also accepts a bare `[Alice](people/alice-chen.md)`, but from a subfolder OK resolves that source-dir-relative — `meetings/people/alice-chen` — and reports it broken, so stick to the `../`-correct relative form, which both accept.)
30	- Path-qualified wikilinks are first-class here, not legacy: `[[people/alice-chen\|Alice Chen]]` resolves vault-root from any folder (no `../` to count), is validated by `brokenLinks` like any link, and imports into GBrain. Keep them extensionless (`[[people/alice-chen]]`, never `[[people/alice-chen.md]]` — the `.md` makes it resolve to a nonexistent doc). A bare `[[note-name]]` with no folder is ambiguous (resolves only if GBrain's basename-globbing is on) — reserve it for Obsidian migration.
31
32	## Agent behaviors
33
34	- Ingest from a meeting recorder. If a meeting-recorder MCP (Granola, Fireflies, Circleback, tl;dv, Fathom, …) is registered alongside `open-knowledge`, pull recent meetings and write each into `meetings/`. Address each as `meetings/<source>-<source_meeting_id>` so re-syncing a meeting updates it in place instead of creating a duplicate. Normalize whatever the recorder returns (Granola's Me/Them streams, a bot's speaker turns) into notes plus the verbatim transcript; do NOT rewrite the transcript. This works the same on demand (you ask) or u

People who liked this also viewed

6 picks

Type