chroma

Store document embeddings and metadata in Chroma for semantic retrieval.

Updated May 4, 2026
One-click install
npx skills add https://github.com/JamesFincher/gengar --skill chroma-jamesfincher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chroma
Source: https://github.com/JamesFincher/gengar/tree/main/optional-skills/mlops/chroma
Command: npx skills add https://github.com/JamesFincher/gengar --skill chroma-jamesfincher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chromadb, sentence-transformers, and includes references (resource) components.

What problem does it solve?

Chroma removes the friction of building fast semantic search and retrieval by letting you store embeddings alongside metadata and then query them efficiently.

Core Features & Use Cases

  • Vector similarity search: Retrieve the most relevant documents for a natural-language query using embeddings.
  • Metadata-filtered retrieval: Narrow results by fields like source, category, tags, timestamps, or numeric ranges.
  • Persistence for memory and RAG: Save and reload your embedding store to support repeatable workflows and long-running knowledge bases.

Use case example: Build a self-hosted RAG knowledge base where you embed wiki pages, store metadata like team and topic, and then retrieve only “onboarding” documents for a specific department.

Quick Start

Use Chroma to create a collection, add documents with metadata, and run a similarity query for a question like “machine learning tutorial”.

Frequently Asked Questions about chroma

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

FAQPage Schema
How do I store embeddings and metadata for semantic search in a persistent vector database?

You can store embeddings and metadata for semantic search by creating a Chroma collection, inserting documents with their metadata, and running similarity queries to retrieve the most relevant matches. This enables persistent vector database workflows.

Can I filter semantic search results by metadata fields like source, category, or tags?

Yes, you can filter semantic search results by metadata fields like source, category, tags, timestamps, or numeric ranges. The vector database supports query-time where-clause filtering to narrow down retrieved documents based on specific metadata conditions.

What is the best way to build a self-hosted RAG knowledge base using a vector database?

The best way to build a self-hosted RAG knowledge base is to embed documents like wiki pages, store them with metadata such as team and topic, and retrieve filtered results using Chroma for persistent, metadata-aware semantic retrieval across your production services.

Do I need sentence-transformers to generate embeddings for Chroma?

Yes, you need sentence-transformers to generate the document embeddings required by the Chroma vector database. The Skill explicitly depends on sentence-transformers alongside chromadb to enable semantic retrieval and metadata-filtered search workflows.

Does this vector database approach work for both notebooks and production services?

Yes, this vector database approach works for both notebooks and production services. It enables persistent storage and reloading of your embedding store to support repeatable workflows and long-running knowledge bases across different environments.