plugins/agent-memory/skills/vector-db-ingest/SKILL.md
Ingests repository files into the ChromaDB vector store. Builds or updates the vector index from a manifest or directory scan using ingest.py. Use when new files need to be indexed or the vector store is out of date. <example> user: "Index these new plugin files into the vector database" assistant: "I'll use vector-db-ingest to add them to the vector store." </example> <example> user: "The vector store is missing recent files -- update it" assistant: "I'll use vector-db-ingest to re-index the changes." </example>
npx skillsauth add richfrem/agent-plugins-skills vector-db-ingestInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill requires the chromadb and langchain packages defined in the plugin root.
You ingest (index) repository files into the ChromaDB vector store so they can be semantically searched. You build or update the parent-child chunk structure that query.py searches against.
High-Performance Mode: This skill uses a configurable batch processing engine (default 1,000 files) defined in .agent/learning/vector_profiles.json.
If vector_profiles.json is missing, run the init skill first:
python ./scripts/init.py
This plugin defaults to In-Process mode for zero-latency direct disk access. No background server is required unless explicitly configured in the profile.
Note: The --profile flag is mandatory to load the correct manifest and batch settings.
python ./scripts/ingest.py --profile wiki --full
python ./scripts/ingest.py --profile wiki --since 24
python ./scripts/ingest.py --profile wiki --file path/to/file.md
python ./scripts/ingest.py --profile wiki --folder path/to/folder
Run a quick semantic search to confirm the new content is retrievable:
python ./scripts/query.py "search query" --profile wiki --limit 3
--profile to ensure the correct batch size and manifest are used.data-ai
Removes stale and orphaned chunks from the ChromaDB vector store for files that have been deleted or renamed. Use after files are removed or moved to keep the vector index in sync with the filesystem. <example> user: "Clean up the vector store after I deleted some files" assistant: "I'll use vector-db-cleanup to remove orphaned chunks." </example> <example> user: "The vector database has chunks for files that no longer exist" assistant: "I'll run vector-db-cleanup to prune them." </example>
testing
Audit Vector DB coverage -- compares the live filesystem manifest against the ChromaDB index to identify coverage gaps.
development
3-Phase Knowledge Search strategy for the RLM Factory ecosystem. Auto-invoked when tasks involve finding code, documentation, or architecture context in the repository. Enforces the optimal search order: RLM Summary Scan (O(1)) -> Vector DB Semantic Search -> Grep/Exact Match. Never skip phases.
tools
Interactive RLM cache initialization. Use when: setting up a new project's semantic cache for the first time, or adding a new cache profile. Walks the user through folder selection, extension config, manifest creation, and first distillation pass.