add-memory-kind
Add a new business memory kind end-to-end. Pick the storage combination (Markdown / SQLite / LanceDB), pick the markdown strategy (daily-log / skill-named / single-file), then wire up the schema(s), repo(s), and writer(s).
npx skills add EverMind-AI/EverOS --skill add-memory-kind --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /add-memory-kind — Add a new business memory kind ## When to invoke Adding a new persisted business entity (Episode, Case, Skill, AtomicFact, Foresight, Profile, or something custom). Multiple storage layers may be involved; this skill walks the decision then the wiring. ## 1. Decide the storage combination A memory kind **does not have to use all three** layers. Pick by what the kind actually needs: | Need | Markdown | SQLite | LanceDB | |---|:-:|:-:|:-:| | Human-readable / agent-editable source-of-truth text | ✅ | | | | Structured state, ACID transactions, joins, predicates | | ✅ | | | Vector / BM25 / hybrid retrieval | | | ✅ | Common combinations seen in EverOS: | Combo | Example | Rationale | |---|---|---| | **md only** | scratch notes / dump bins | text-of-truth, no index needed | | **md + lancedb** | episode / memcell / case | text-of-truth + semantic retrieval | | **md + sqlite** | profile / playbook / soul.md state | text-of-truth + structured state to query | | **md + sqlite + lancedb** | full-blown business records | when you need *both* transactional state AND retrieval | | **sqlite only** | audit log / task queue / LSN watermark | system state, never user-facing | | *
- When to invoke
- 1. Decide the storage combination
- 2. Pick the markdown storage strategy (if md is in your combo)
- 3. Markdown daily-log: 4 steps
- 3.1 Frontmatter schema — infra/persistence/markdown/mds/<name>.py
- 3.2 Re-export — mds/init.py
- 3.3 Business writer — infra/persistence/markdown/writers/<name>.py
- 3.4 Re-export — writers/init.py
- Done — usage
- 4. (Optional) SQLite table — 4 steps
- 4.1 Schema — infra/persistence/sqlite/tables/<name>.py
- 4.2 Re-export — tables/init.py
- 4.3 Repo — infra/persistence/sqlite/repos/<name>.py
- 4.4 Re-export — repos/init.py
What does the add-memory-kind skill do?
Add a new business memory kind end-to-end. Pick the storage combination (Markdown / SQLite / LanceDB), pick the markdown strategy (daily-log / skill-named / single-file), then wire up the schema(s), repo(s), and writer(s).
How do I install it?
Run `npx skills add EverMind-AI/EverOS --skill add-memory-kind --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From EverMind-AI/EverOS, a repository with 11,801 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
