vector-db-audit

Compares filesystem manifest to ChromaDB index to identify missing files.

5|3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/richfrem/agent-plugins-skills --skill vector-db-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vector-db-audit
Source: https://github.com/richfrem/agent-plugins-skills/tree/main/plugins/vector-db/skills/vector-db-audit
Command: npx skills add https://github.com/richfrem/agent-plugins-skills --skill vector-db-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Audit Vector DB coverage by comparing the live filesystem manifest against the ChromaDB index to identify coverage gaps.

Core Features & Use Cases

  • Gap identification: detect files in the manifest that are missing from the ChromaDB index.
  • Coverage reporting: compute the percentage of project docs vectorized.
  • Ingestion readiness: export missing files to a CSV for targeted ingestion.
  • Dynamic config: reads profile settings to adjust connections and collection parameters.

Quick Start

Run the audit_vector.py script with your chosen profile to generate the vector coverage report and a CSV of missing files.

Frequently Asked Questions about vector-db-audit

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

FAQPage Schema
How do I find missing files in my ChromaDB index?

Auditing vector database coverage compares your filesystem manifest against the ChromaDB index to identify missing files. It computes the percentage of documents vectorized and generates a gap report for targeted ingestion.

How do I check vector database coverage for my document collection?

Checking vector database coverage compares your project's filesystem manifest against the ChromaDB index. It calculates the percentage of vectorized documents and generates a report highlighting any missing files.

Do I need Python to run a ChromaDB vector audit?

Yes, a Python environment is required to run the vector database audit script. It reads profile-based configuration to connect to ChromaDB and generate the coverage report and missing-items CSV.

How do I generate a CSV of missing items for targeted ingestion?

Generating a CSV of missing items for targeted ingestion requires running the audit script with your chosen profile. It compares the filesystem manifest against the ChromaDB index and exports detected gaps to a CSV file.

Can I use profile-based configuration to adjust ChromaDB collection parameters?

Yes, the vector audit script uses dynamic config to read profile settings. This allows you to adjust ChromaDB connections and collection parameters before generating the coverage report and missing-items CSV.