chromadb

Audit, search, back up, and delete ChromaDB memory storage entries.

110|14|Updated May 12, 2026
One-click install
npx skills add https://github.com/EliasOulkadi/shokunin --skill chromadb-eliasoulkadi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chromadb
Source: https://github.com/EliasOulkadi/shokunin/tree/main/.pack/skills/chromadb
Command: npx skills add https://github.com/EliasOulkadi/shokunin --skill chromadb-eliasoulkadi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you troubleshoot and control Shokunin’s persistent memory storage in ChromaDB, so your agent’s long-term knowledge stays safe and recoverable.

Core Features & Use Cases

  • Memory status & storage auditing: Check entry counts, collection sizes, and last-write timestamps to confirm memory is being saved correctly.
  • Semantic search over stored entries: Find past decisions, files, commands, and session-related records using hybrid vector + keyword retrieval.
  • Backup, delete, and reset with guardrails: Create timestamped backups, remove stale entries by session/project, and perform full resets only when necessary.

Quick Start

Ask your agent to back up the ChromaDB database so you can safely make destructive changes later.

Frequently Asked Questions about chromadb

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

FAQPage Schema
How do I back up a ChromaDB vector database before making destructive changes?

You can back up a ChromaDB vector database by running the chroma-helper.py backup command, which creates a timestamped backup of your persistent memory storage to ensure long-term knowledge stays safe and recoverable.

How does semantic retrieval work for persistent memory stored in ChromaDB?

Semantic retrieval over ChromaDB persistent memory uses hybrid vector and keyword search to locate past decisions, files, commands, and session records stored within the vector database collections.

What is the best way to audit persistent memory storage and check if entries are being saved correctly?

Auditing persistent memory storage involves checking entry counts, collection sizes, and last-write timestamps using the status command to confirm that vector database records are being saved correctly.

Can I filter and delete specific stale entries from ChromaDB by session or project?

Yes, you can perform filtered deletions to remove stale entries from ChromaDB by session or project using the chroma-helper.py script, which includes guardrails to safely manage persistent memory.

When should I perform a full database reset on ChromaDB persistent memory?

A full database reset on ChromaDB persistent memory should only be performed when necessary, such as during memory corruption or migration, and must be preceded by a timestamped backup to prevent data loss.

How do I rebuild ChromaDB memory storage after corruption or migration?

To rebuild ChromaDB memory storage after corruption or migration, use the chroma-helper.py rebuild workflow, which ensures the persistent memory store is safely recovered and verified.