emdb-namespaces

List, create, and isolate vectors across EmergentDB namespaces.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/justrach/emergent-sdk --skill emdb-namespaces
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emdb-namespaces
Source: https://github.com/justrach/emergent-sdk/tree/main/skills/emdb-namespaces
Command: npx skills add https://github.com/justrach/emergent-sdk --skill emdb-namespaces

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Namespaces in EmergentDB help organize vectors into isolated groups and provide clear boundaries between environments and tenants, reducing cross-dataset leakage and simplifying access control.

Core Features & Use Cases

  • List existing namespaces and inspect their scope and quotas.
  • Auto-create namespaces on first insert and default to a "default" namespace when unspecified.
  • Apply per-namespace isolation so searches and inserts are namespace-scoped.
  • Move vectors between namespaces by re-inserting with a different namespace and auditing cross-namespace activity.

Quick Start

List all namespaces and insert a sample item into a chosen namespace to demonstrate isolation.

Frequently Asked Questions about emdb-namespaces

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

FAQPage Schema
How do I isolate vectors for multi-tenant environments in a vector database?

Vector isolation for multi-tenant environments is achieved by using namespaces to organize vectors into isolated groups, providing clear boundaries between tenants and reducing cross-dataset leakage. EmergentDB supports per-namespace isolation during searches and inserts.

How do I create a new namespace in EmergentDB?

To create a namespace in EmergentDB, you can perform a first insert with a specified namespace parameter. If no namespace is specified, the system automatically defaults to a predefined "default" namespace to store your vectors.

Can I move vectors between different namespaces after they have been inserted?

Yes, you can move vectors between namespaces by re-inserting the data with a different namespace parameter. This allows you to transfer vectors across environments while auditing any cross-namespace activity.

How does listing namespaces help with managing staging and production data?

Listing namespaces helps manage staging and production data by letting you inspect the scope and quotas of each isolated group. This ensures environments remain separated and simplifies access control across your datasets.

What happens to vector searches if I don't specify a namespace?

If you do not specify a namespace, EmergentDB defaults to the "default" namespace for both inserts and searches. This ensures your operations remain namespace-scoped and prevents unintended cross-dataset leakage.

Does namespace management in EmergentDB require any external dependencies?

No, namespace management in EmergentDB does not require external dependencies. It natively supports listing, creating, and using namespaces to isolate datasets across default, staging, and production environments.