memesis reindex --vec

Recompute stored memory embeddings to match a new embedding model.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/emmahyde/memesis --skill memesis-reindex-vec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memesis reindex --vec
Source: https://github.com/emmahyde/memesis/tree/main/skills/reindex
Command: npx skills add https://github.com/emmahyde/memesis --skill memesis-reindex-vec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires core.embeddings, core.vec, core.database, core.models, and includes scripts (resource) components.

What problem does it solve?

It enables updating all stored memory embeddings to match a new or changed embedding model, ensuring retrieval accuracy and consistency.

Core Features & Use Cases

  • Memory Re-embedding: Reads all existing memories and recalculates their embeddings using the current embedding model.
  • Atomic Table Swap: Performs an in-place update of the vector memories table to maintain database integrity.
  • Use Case: After switching to a different embedding model version, run this Skill to regenerate memory embeddings and keep retrieval relevant and precise.

Quick Start

Use the reindex --vec skill to refresh memory embeddings after changing your embedding configuration.

Frequently Asked Questions about memesis reindex --vec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I re-embed stored memories after updating my vector embedding model?

To re-embed stored memories after an embedding model update, you recalculate all existing memory vectors using the current model to maintain retrieval accuracy and consistency.

Why does memory retrieval accuracy drop when I change embedding parameters?

Memory retrieval accuracy drops after altering embedding parameters because existing stored vectors no longer match the new model's vector space, requiring a full re-indexing process.

What is the best way to update a vector database after switching embedding models?

The best way to update a vector database after switching embedding models is performing an atomic table swap, which executes an in-place update to maintain database integrity during re-embedding.

Do I need core.embeddings and core.database to reindex memory vectors?

Yes, you need the core.embeddings, core.vec, and core.database dependencies to execute memory re-indexing, as they handle embedding generation, vector storage, and database operations.

Can I update memory embeddings in-place without corrupting the vector database?

You can update memory embeddings in-place without database corruption by using an atomic table swap mechanism, which safely replaces the vector memories table during the re-indexing operation.