vector-database-engineer — Claude Code skill: what it does
vector-database-engineer picks a vector store and sets up embedding search for RAG, recommendations or similarity lookup. Comes in when recall and latency start to matter.
MIT ★ 50,109 updated 2026-10-29
npx skills add sickn33/agentic-awesome-skills --skill vector-database-engineer -a claude-codeWhat vector-database-engineer does
The skill walks through vector search piece by piece: picking a store among Pinecone, Weaviate, Qdrant, Milvus and pgvector, choosing an embedding model, setting up HNSW, IVF or PQ indexes, mixing keyword hits with vector results, cutting documents into overlapping chunks and filtering on metadata. Latency against recall gets its own pass.
It ships as instructions, not code. The agent asks for goals and inputs first, then follows a workflow that ends with monitoring and a plan for rebuilding the index. Longer examples live in resources/implementation-playbook.md, which the skill opens when needed.
Embedding dimensions are where things break. Match the model's output size to what the database and index accept, and rebuild after swapping in a model that does not fit. Treat the answer as a starting design: recall and latency still need measuring on your own queries.
What it helps with
- choose a vector database for your data and query shape
- match an embedding model's dimensions to what the index accepts
- tune HNSW or IVF for the recall and latency you need
- combine keyword search with vector hits in one query
- split documents into overlapping chunks and filter on metadata
Example prompts for the agent
- Set up RAG over the
docs/folder: which store fits, and how should I configure the index? - Add hybrid search on pgvector with metadata filters.
- Queries got slow as the index grew. What should I change in HNSW?
How to install vector-database-engineer
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill vector-database-engineer -a claude-code2Manually: put the files in place
~/.claude/skills/vector-database-engineer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vector-database-engineer/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill vector-database-engineer -a codex2Manually: put the files in place
.agents/skills/vector-database-engineer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill vector-database-engineer -a cursor2Manually: put the files in place
.cursor/skills/vector-database-engineer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills skills/vector-database-engineer2Manually: put the files in place
.github/skills/vector-database-engineer/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill vector-database-engineer -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/vector-database-engineerManually: put the files in place
.devin/skills/vector-database-engineer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill vector-database-engineer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vector-database-engineer
How to install vector-database-engineer in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill vector-database-engineer -a claude-code. The skill file then sits at ~/.claude/skills/vector-database-engineer/SKILL.md.
What does vector-database-engineer do?
It helps design vector search end to end: store and embedding model choice, index setup, hybrid retrieval, chunking and metadata filters.
Which vector databases does it cover?
Pinecone, Weaviate, Qdrant, Milvus and pgvector. Index types HNSW, IVF and PQ, plus hybrid vector and keyword search, are part of the scope.
Source text
SKILL.md · MIT
--- name: vector-database-engineer description: "Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similar" risk: critical source: community date_added: "2026-02-27" --- # Vector Database Engineer Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similarity search. Use PROACTIVELY for vector search implementation, embedding optimization, or semantic retrieval systems. ## Do not use this skill when - The task is unrelated to vector database engineer - You need a different domain or tool outside this scope ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Capabilities - Vector database selection and architecture - Embedding model selection and optimization - Index configuration (HNSW, IVF, PQ) - Hybrid search (vector + keyword) implementation - Chunking strategies for documents - Metadata filtering and pre/post-filtering - Performance tuning and scaling ## Use this skill when - Building RAG (Retrieval Augmented Generation) systems - Implementing semantic search over documents - Creating recommendation engines - Building image/audio similarity search - Optimizing vector search latency and recall - Scaling vector operations to millions of vectors ## Workflow 1. Analyze data characteristics and query patterns 2. Select appropriate embedding model 3. Design chunking and preprocessing pipeline 4. Choose vector database and index type 5. Configure metadata schema for filtering 6. Implement hybrid search if needed 7. Optimize for latency/recall tradeoffs 8. Set up monitoring and reindexing strategies ## Best Practices - Use the chosen model’s documented output dimensions; confirm database/index support and reindex on incompatible model changes - Implement proper chunking with overlap - Use metadata filtering to reduce search space - Monitor embedding drift over time - Plan for index rebuilding - Cache frequent queries - Test recall vs latency tradeoffs ## Example **User request:** > Build RAG (Retrieval Augmented Generation) systems. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
© sickn33 · MIT · sickn33/agentic-awesome-skills