chroma-integration
Chroma local vector database setup and operations for development and production
npx skills add a5c-ai/babysitter --skill chroma-integration --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.
# Chroma Integration Skill ## Capabilities - Set up Chroma (ephemeral, persistent, client-server) - Create and manage collections - Implement document ingestion with embeddings - Configure metadata filtering - Set up multi-tenant collections - Implement where and where_document filters ## Target Processes - vector-database-setup - rag-pipeline-implementation ## Implementation Details ### Deployment Modes 1. **Ephemeral**: In-memory for testing 2. **Persistent**: Local file-based storage 3. **Client-Server**: Chroma server deployment ### Core Operations - Collection creation with embedding functions - Add/update/delete documents - Query with filters - Metadata management ### Configuration Options - Embedding function selection - Persistence directory - Distance metric (l2, ip, cosine) - Collection metadata - Server configuration ### Best Practices - Use persistent mode for development - Deploy server mode for production - Design metadata schema upfront - Implement proper ID strategies ### Dependencies - chromadb - langchain-chroma
- Capabilities
- Target Processes
- Implementation Details
- Deployment Modes
- Core Operations
- Configuration Options
- Best Practices
- Dependencies
What does the chroma-integration skill do?
Chroma local vector database setup and operations for development and production
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill chroma-integration --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 a5c-ai/babysitter, a repository with 1,642 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.