Chroma Vector Database
Orchestra-Research/AI-Research-SKILLs
Shows how to store documents and embeddings in Chroma, query them by similarity with metadata filters, and persist them to disk for RAG and semantic search projects.
Build NodeTool document ingestion, vector indexing, retrieval, and RAG pipelines.
$ npx skills add nodetool-ai/nodetool --skill nodetool-rag-indexing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nodetool-ai/nodetool nodetool-rag-indexing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/system-skills/nodetool-rag-indexing .claude/skills/nodetool-rag-indexing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "nodetool-rag-indexing" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-rag-indexing into .claude/skills/nodetool-rag-indexing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-rag-indexing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-rag-indexingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nodetool-ai/nodetool --skill nodetool-rag-indexing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nodetool-ai/nodetool nodetool-rag-indexing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/system-skills/nodetool-rag-indexing .agents/skills/nodetool-rag-indexing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nodetool-rag-indexing" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-rag-indexing into .agents/skills/nodetool-rag-indexing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-rag-indexing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nodetool-ai/nodetool --skill nodetool-rag-indexing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nodetool-ai/nodetool nodetool-rag-indexing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/system-skills/nodetool-rag-indexing .cursor/skills/nodetool-rag-indexing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "nodetool-rag-indexing" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-rag-indexing into .cursor/skills/nodetool-rag-indexing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-rag-indexing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nodetool-ai/nodetool.git --path packages/system-skills/nodetool-rag-indexing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nodetool-ai/nodetool --skill nodetool-rag-indexing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nodetool-ai/nodetool nodetool-rag-indexing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/system-skills/nodetool-rag-indexing .gemini/skills/nodetool-rag-indexing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "nodetool-rag-indexing" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-rag-indexing into .gemini/skills/nodetool-rag-indexing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-rag-indexing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nodetool-ai/nodetool nodetool-rag-indexingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nodetool-ai/nodetool --skill nodetool-rag-indexing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/system-skills/nodetool-rag-indexing .github/skills/nodetool-rag-indexing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "nodetool-rag-indexing" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-rag-indexing into .github/skills/nodetool-rag-indexing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-rag-indexing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nodetool-ai/nodetool --skill nodetool-rag-indexing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nodetool-ai/nodetool nodetool-rag-indexing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/system-skills/nodetool-rag-indexing .opencode/skills/nodetool-rag-indexing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "nodetool-rag-indexing" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/nodetool-rag-indexing into .opencode/skills/nodetool-rag-indexing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nodetool-rag-indexing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
nodetool-rag-indexingBuild NodeTool document ingestion, vector indexing, retrieval, and RAG pipelines.
Nodetool RAG Indexing is an agent skill from nodetool-ai/nodetool. Build NodeTool document ingestion, vector indexing, retrieval, and RAG pipelines.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering, covering Retrieval-augmented generation and Vector databases. The repository describes itself as: Agent-first Creative Workspace. The licence is AGPL-3.0.
Read from SKILL.md and the folder at commit 339f069. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
curlFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
CHROMA_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Nodetool RAG Indexing loads about 1.4k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 440 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from nodetool-ai/nodetool at commit 339f069, republished under its AGPL-3.0 licence (© nodetool-ai). 440 words, ~1,426 tokens.
.claude/skills/nodetool-rag-indexing/SKILL.md (or your agent's skills folder).You help users build Retrieval-Augmented Generation (RAG) pipelines in NodeTool.
INDEXING: Documents → Load → Split → Embed → Store (vector collection)
QUERY: Question → Embed → Search → Format → LLM → AnswerNodeTool's vector store (@nodetool-ai/vectorstore) is backend-pluggable. The
workflow nodes are the same regardless of backend — you pick the backend via
configuration.
| Backend | Best for | Notes |
|---|---|---|
| SQLite-vec | Default, local, embedded | No external service |
| ChromaDB | Self-host / remote | CHROMA_URL, CHROMA_PATH, CHROMA_TOKEN |
| Pinecone | Managed cloud | API-key based |
| Supabase (pgvector) | Postgres-backed | Pairs with Supabase auth/storage |
There are no FAISS nodes; the backends above cover local and hosted use.
vector.*)All RAG nodes live under the single vector.* namespace (not vector.chroma.*
or vector.faiss.*).
| Node | Purpose |
|---|---|
vector.Collection | Reference/select a collection by name (the collection ref other nodes consume) |
vector.IndexTextChunk | Index a single text chunk with its embedding |
vector.IndexString | Index a string value |
vector.IndexAggregatedText | Index aggregated text |
vector.IndexEmbedding | Index a precomputed embedding |
vector.IndexImage | Index an image |
vector.QueryText | Vector similarity search over text |
vector.QueryImage | Vector similarity search over images |
vector.HybridSearch | Vector + keyword search (best accuracy) |
vector.GetDocuments | Retrieve specific documents |
vector.Count | Count documents in a collection |
vector.Peek | Preview collection contents |
vector.RemoveOverlap | De-duplicate overlapping chunks in results |
Query nodes (QueryText, QueryImage, HybridSearch) output ids,
documents, metadatas, and distances (HybridSearch also returns scores).
| Node | Namespace | Purpose |
|---|---|---|
Code | nodetool.code | Enumerate files with await workspace.list(dir) |
LoadDocumentFile | nodetool.document | Load a PDF/TXT/MD into a document |
Chunk | nodetool.text | Fixed-size word chunking with overlap (general purpose) |
RegexSplit | nodetool.text | Structure-aware splitting on a delimiter pattern |
| Content type | Chunk size | Overlap |
|---|---|---|
| Technical docs | 200-500 tokens | 50 tokens |
| Prose/articles | 300-600 tokens | 75 tokens |
| Code | 100-300 tokens | 25 tokens |
ListFiles → LoadDocumentFile → Chunk → IndexTextChunk(collection)Pair every index/query node with a vector.Collection node (or a collection
name) so they target the same store. Use the same embedding model for
indexing and querying.
# Index a file into a collection
curl -X POST http://localhost:7777/api/collections/<name>/index \
-H "Authorization: Bearer TOKEN" \
-H "Content-Type: application/json" \
-d '{"file_path": "/path/to/document.pdf"}'The server resolves the collection, runs its ingestion workflow if one is registered, otherwise falls back to split → embed → store.
ChatInput → HybridSearch(collection, top_k) → FormatText → Agent → Output| Node | Purpose |
|---|---|
ChatInput | User question |
vector.HybridSearch | Vector + keyword retrieval (best accuracy) |
vector.QueryText | Vector-only retrieval (faster) |
FormatText | Build the context string for the LLM |
Agent | Generate the answer from context + question |
Output | Return the answer |
ListFiles("/docs/") → LoadDocumentFile → Chunk(length=400, overlap=50)
↓
IndexTextChunk(collection="my-docs")ChatInput("What is...?") → HybridSearch(collection="my-docs", top_k=5)
↓
FormatText(template="Context:\n{documents}\n\nQuestion: {query}")
↓
Agent(model=gpt-5.4, system="Answer using only the context provided.")
↓
Output# ChromaDB backend (only when using Chroma — SQLite-vec needs no config)
CHROMA_URL= # Remote Chroma URL (empty = local)
CHROMA_PATH=~/.local/share/nodetool/chroma # Local storage path
CHROMA_TOKEN= # Optional auth tokenThe embedding model is chosen on the index/query nodes via model selection
(e.g. text-embedding-3-small, or a local sentence-transformers model).
vector.IndexTextChunk / vector.QueryText / vector.HybridSearch, not IndexTextChunks / TextSearch, and there is no vector.chroma.*/vector.faiss.* namespace.nodetool collections CLI: manage collections through the editor UI or the /api/collections/... endpoints.© nodetool-ai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in packages/system-skills/nodetool-rag-indexing of nodetool-ai/nodetool.
Open the folder on GitHubat commit 339f069
Nodetool RAG Indexing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Nodetool RAG Indexing this skillnodetool-ai/nodetool | 560 | — | ~1.4k | Automated safety check: Pass | AGPL-3.0 | |
| Chroma Vector DatabaseOrchestra-Research/AI-Research-SKILLs | 13k | 7 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Pgvector Semantic Searchtimescale/pg-aiguide | 1.9k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Postgres Hybrid Text Searchtimescale/pg-aiguide | 1.9k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| RAG Implementationwshobson/agents | 40k | 9 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Vector DBRightNow-AI/openfang | 18k | — | ~1k | Automated safety check: Pass | Apache-2.0 |
Orchestra-Research/AI-Research-SKILLs
Shows how to store documents and embeddings in Chroma, query them by similarity with metadata filters, and persist them to disk for RAG and semantic search projects.
timescale/pg-aiguide
A skill your agent uses for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search.
timescale/pg-aiguide
A skill your agent uses to implement hybrid search combining BM25 keyword search with semantic vector search using Reciprocal Rank Fusion (RRF).
wshobson/agents
Build retrieval-augmented generation systems: pick a vector database and embedding model, choose retrieval and reranking strategies, and start from a LangGraph pipeline.
RightNow-AI/openfang
Vector database expert for embeddings, similarity search, RAG patterns, and indexing strategies
elementalsouls/Claude-BugHunter
Hunt vector-store / embedding-layer weaknesses in RAG pipelines (OWASP LLM08 Vector and Embedding Weaknesses) — persistent corpus poisoning that survives across sessions and users (distinct from…
nodetool-ai/nodetool
Cut a NodeTool timeline to music and shape its pacing — detect the beat grid, place cuts on phrases, pick a cut type, build speed ramps with time remap, and give the piece an arc.
nodetool-ai/nodetool
Add and animate a consistent text layer on an existing NodeTool timeline.
nodetool-ai/nodetool
Choose and animate colour on a NodeTool timeline, including shape and text gradients, colour grades, 3D LUTs, and dither.
nodetool-ai/nodetool
Write a shootable, precisely timed commercial beat sheet and store it as a NodeTool storyboard, with a consistent entity roster behind every shot.
nodetool-ai/nodetool
Direct ElevenLabs speech, dialogue, sound effects and music — the bracketed audio tags v3 acts on and why the voice decides whether a tag lands, stability as the delivery dial, punctuation instead…
nodetool-ai/nodetool
Stage the frame on a NodeTool timeline — grids, focal placement, safe areas per aspect ratio, depth layers and parallax, camera moves, and where elements enter and leave.
Categories
Build NodeTool document ingestion, vector indexing, retrieval, and RAG pipelines. Nodetool RAG Indexing is an agent skill from nodetool-ai/nodetool. Build NodeTool document ingestion, vector indexing, retrieval, and RAG pipelines.
Nodetool RAG Indexing fits situations like: tasks that involve Retrieval-augmented generation; tasks that involve Vector databases.
Run `npx skills add nodetool-ai/nodetool --skill nodetool-rag-indexing -a claude-code`. Or copy the skill folder (packages/system-skills/nodetool-rag-indexing in nodetool-ai/nodetool) into .claude/skills/nodetool-rag-indexing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add nodetool-ai/nodetool --skill nodetool-rag-indexing -a codex`. Or copy the skill folder (packages/system-skills/nodetool-rag-indexing in nodetool-ai/nodetool) into .agents/skills/nodetool-rag-indexing in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nodetool-ai/nodetool --skill nodetool-rag-indexing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nodetool-rag-indexing, .gemini/skills/nodetool-rag-indexing, .github/skills/nodetool-rag-indexing and .opencode/skills/nodetool-rag-indexing in your project.
Going by SKILL.md and its folder, Nodetool RAG Indexing needs the command-line tools its instructions call (curl) and credentials named CHROMA_TOKEN. Our summary lists: A credential in CHROMA_TOKEN.
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Nodetool RAG Indexing is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Nodetool RAG Indexing: Chroma Vector Database (Orchestra-Research/AI-Research-SKILLs, 13k stars), Pgvector Semantic Search (timescale/pg-aiguide, 1.9k stars), Postgres Hybrid Text Search (timescale/pg-aiguide, 1.9k stars) and RAG Implementation (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
nodetool-ai (a GitHub organization) maintains it in nodetool-ai/nodetool, which has 560 GitHub stars. The repository holds 127 skills in this directory. The repository was last updated on October 10, 2026.
Source: nodetool-ai/nodetool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.