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.
Call nodetool.collections from a code action: index text chunks into the vector store, search them semantically or with hybrid keyword search, and query a named knowledge collection.
Install API Collections
$ npx skills add nodetool-ai/nodetool --skill api-collections -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nodetool-ai/nodetool api-collections --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/api-collections .claude/skills/api-collections && 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 "api-collections" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-collections into .claude/skills/api-collections/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-collections", 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/api-collectionsType 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 api-collections -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nodetool-ai/nodetool api-collections --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/api-collections .agents/skills/api-collections && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "api-collections" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-collections into .agents/skills/api-collections/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-collections", 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 api-collections -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nodetool-ai/nodetool api-collections --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/api-collections .cursor/skills/api-collections && 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 "api-collections" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-collections into .cursor/skills/api-collections/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-collections", 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/api-collections--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 api-collections -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nodetool-ai/nodetool api-collections --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/api-collections .gemini/skills/api-collections && 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 "api-collections" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-collections into .gemini/skills/api-collections/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-collections", 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 api-collectionsInstalls 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 api-collections -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/api-collections .github/skills/api-collections && 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 "api-collections" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-collections into .github/skills/api-collections/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-collections", 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 api-collections -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 api-collections --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/api-collections .opencode/skills/api-collections && 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 "api-collections" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/system-skills/api-collections into .opencode/skills/api-collections/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-collections", 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.
Facts
- Skill name
api-collections- GitHub stars
- 556
- Token cost
- ~531 tokens
- SKILL.md length
- 198 words
- Files
- 1
- Skills in repo
- 127
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Call nodetool.collections from a code action: index text chunks into the vector store, search them semantically or with hybrid keyword search, and query a named knowledge collection.
- Tasks that involve Vector databases
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
API Collections is an agent skill from nodetool-ai/nodetool. Call nodetool.collections from a code action: index text chunks into the vector store, search them semantically or with hybrid keyword search, and query a named knowledge collection. Load before the first call into nodetool.collections.
Its SKILL.md is about 530 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 Vector databases. The repository describes itself as: Agent-first Creative Workspace. The licence is AGPL-3.0.
When your agent uses it
- Tasks that involve Vector databases
Example prompts
- “/api-collections”
What it can do on your machine
Read from SKILL.md and the folder at commit 515bd28. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
API Collections loads about 531 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 198 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from nodetool-ai/nodetool at commit 515bd28, republished under its AGPL-3.0 licence (© nodetool-ai). 198 words, ~531 tokens.
Download SKILL.mdSave it as
.claude/skills/api-collections/SKILL.md (or your agent's skills folder).- name
- api-collections
- description
- Call nodetool.collections from a code action: index text chunks into the vector store, search them semantically or with hybrid keyword search, and query a named knowledge collection. Load before the first call into nodetool.collections.
nodetool.collections
The vector store behind retrieval. A collection indexes document chunks with
embeddings for semantic or hybrid search. It is not an asset folder. How to
chunk, what metadata to keep and how to build a RAG workflow is
nodetool-rag-indexing.
| Call | Does |
|---|---|
list() | Lists the collections the user has. |
query(collection, query, {n_results}) | Semantic search in one named collection. n_results defaults to 5. |
index(text, sourceId, {metadata}) | Indexes one chunk. Indexing the same sourceId again updates it. |
indexBatch(chunks, {base_metadata}) | Indexes many chunks: [{text, source_id, metadata?}]. base_metadata is added to each. |
search(text, {n_results}) | Semantic search across all collections. n_results defaults to 10. |
hybridSearch(text, {n_results, k_constant, min_keyword_length}) | Semantic plus keyword search, fused by reciprocal rank. n_results is per collection, default 5. k_constant defaults to 60. |
Rules
- Call
list()first when you do not know the collection name. - Give each chunk a stable
source_id, such as"<file>#<chunk-number>", so a second indexing pass updates chunks instead of adding copies. - Put what you filter or cite by in
metadata: the source file, the page, the title, the URL. - Use
hybridSearchwhen the query has exact names, codes or rare words that embeddings miss. - Index in batches with
indexBatch, not oneindexcall for each chunk.
const text = (await nodetool.documents.extractText("manual.pdf")).text;
const chunks = text.match(/[\s\S]{1,1200}/g).map((t, i) => ({
text: t, source_id: `manual.pdf#${i}`, metadata: { file: "manual.pdf" }
}));
await nodetool.collections.indexBatch(chunks);
const hits = await nodetool.collections.hybridSearch("reset the device");© 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
Files
Just SKILL.md in packages/system-skills/api-collections of nodetool-ai/nodetool.
Open the folder on GitHubat commit 515bd28
Compare with similar skills
API Collections 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 |
|---|---|---|---|---|---|---|
| API Collections this skillnodetool-ai/nodetool | 556 | — | ~531 | Automated safety check: Pass | AGPL-3.0 | |
| Chroma Vector DatabaseOrchestra-Research/AI-Research-SKILLs | 13k | 8 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Codebase Managementgiancarloerra/SocratiCode | 3.3k | 1 repos | ~1.8k | Automated safety check: Pass | AGPL-3.0 | |
| Pgvector Semantic Searchtimescale/pg-aiguide | 1.9k | 1 repos | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Hermes Memory Providersmnemosyne-oss/mnemosyne | 3.4k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Flowflow Spacesmirkobozzetto/flowflow | 171 | — | ~1k | Automated safety check: Pass | EUPL-1.2 |
Similar skills
Codebase Management
giancarloerra/SocratiCode
Set up, index, and manage SocratiCode codebase indexing. An agent skill from giancarloerra/SocratiCode.
Pgvector Semantic Search
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.
Hermes Memory Providers
mnemosyne-oss/mnemosyne
Install and configure Mnemosyne as a Hermes Agent memory provider — local SQLite with vector search, episodic consolidation, and temporal knowledge graphs.
Flowflow Spaces
mirkobozzetto/flowflow
Use FlowFlow spaces safely through their scoped MCP server. An agent skill from mirkobozzetto/flowflow.
Postgres Hybrid Text 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).
More from nodetool-ai/nodetool
All 127 skills in this repoBeat Sync Editing
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.
Caption Titles
nodetool-ai/nodetool
Add and animate a consistent text layer on an existing NodeTool timeline.
Color Motion
nodetool-ai/nodetool
Choose and animate colour on a NodeTool timeline, including shape and text gradients, colour grades, 3D LUTs, and dither.
Commercial Beat Sheet
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.
Elevenlabs Audio Prompting
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…
Frame Composition
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.
Related
Categories
Questions about API Collections
What does API Collections do?
Call nodetool.collections from a code action: index text chunks into the vector store, search them semantically or with hybrid keyword search, and query a named knowledge collection. API Collections is an agent skill from nodetool-ai/nodetool.collections from a code action: index text chunks into the vector store, search them semantically or with hybrid keyword search, and query a named knowledge collection.
When should I use API Collections?
API Collections fits situations like: tasks that involve Vector databases.
How do I install API Collections in Claude Code?
Run `npx skills add nodetool-ai/nodetool --skill api-collections -a claude-code`. Or copy the skill folder (packages/system-skills/api-collections in nodetool-ai/nodetool) into .claude/skills/api-collections in your project. Claude Code loads it when a task matches its description.
How do I install API Collections in Codex?
Run `npx skills add nodetool-ai/nodetool --skill api-collections -a codex`. Or copy the skill folder (packages/system-skills/api-collections in nodetool-ai/nodetool) into .agents/skills/api-collections in your project. Codex loads it when a task matches its description.
Can I use API Collections in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nodetool-ai/nodetool --skill api-collections -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-collections, .gemini/skills/api-collections, .github/skills/api-collections and .opencode/skills/api-collections in your project.
What does API Collections need to run?
SKILL.md names no scripts, command-line tools or credentials: API Collections is instructions for the agent only.
Does API Collections access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is API Collections safe to install?
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.
What licence does API Collections use?
API Collections 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.
How many tokens does API Collections use?
About 531 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to API Collections?
Skills that share tags, products or a category with API Collections: Chroma Vector Database (Orchestra-Research/AI-Research-SKILLs, 13k stars), Codebase Management (giancarloerra/SocratiCode, 3.3k stars), Pgvector Semantic Search (timescale/pg-aiguide, 1.9k stars) and Hermes Memory Providers (mnemosyne-oss/mnemosyne, 3.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains API Collections?
nodetool-ai (a GitHub organization) maintains it in nodetool-ai/nodetool, which has 556 GitHub stars. The repository holds 127 skills in this directory. The repository was last updated on October 8, 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.