Generated banner for Vector Database Engineer
Generated logo for Vector Database Engineer

Vector Database Engineer

Seth HobsonCommunityCreated by Seth Hobson

  • Subagent
  • Tool integration
  • Data and AI
  • MIT
  • No issues found

From the author

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.
— the description by Seth Hobson

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Vector Database Engineer acts as a specialized architect for semantic search and retrieval systems. It provides deep technical guidance on selecting appropriate vector databases, choosing embedding models, and configuring indexing strategies to balance recall, latency, and memory usage. The skill covers the entire lifecycle of vector operations, from document chunking and metadata enrichment to hybrid search implementation and production-level monitoring.

What it does

  • Architects vector search systems for RAG and recommendation engines.
  • Provides expert selection for vector databases like Pinecone, Qdrant, and Milvus.
  • Guides embedding model selection based on domain and performance requirements.
  • Optimizes indexing strategies such as HNSW and IVF for specific latency needs.
  • Implements hybrid search and reranking pipelines for improved retrieval precision.
  • Advises on production operations including scaling, monitoring, and cost management.

When to use it

  • When designing a new RAG application or semantic search engine.
  • When needing to optimize existing vector search latency or recall metrics.
  • When choosing between managed or self-hosted vector database solutions.
  • When implementing complex hybrid search or reranking strategies.
  • When scaling vector operations to handle millions of documents.

Advantages

  • Provides vendor-agnostic architectural advice.
  • Balances complex trade-offs between recall, latency, and resource costs.
  • Includes specific guidance for domain-specific embedding models.
  • Focuses on production-grade reliability and scalability.
  • Covers the full pipeline from data ingestion to query optimization.

Usage examples

“Design a vector search system for 10M documents with <100ms P95 latency.”
The agent will propose an architecture using high-performance indexing like HNSW or IVF, suggest appropriate hardware or managed service tiers, and outline strategies for metadata filtering and query optimization.
“Migrate from Chroma to Qdrant for production workloads.”
The agent will provide a migration plan, including data export/import strategies, index configuration differences, and how to adapt existing application code to Qdrant's API.
“Implement hybrid search combining semantic and keyword retrieval.”
The agent will explain how to integrate vector search with BM25, implement Reciprocal Rank Fusion (RRF), and configure weighted scoring to improve search relevance.
“Optimize embedding costs by selecting the right model and dimensions.”
The agent will analyze your use case to recommend cost-effective embedding models and dimension settings that maintain required accuracy while reducing storage and compute overhead.

Install

  1. Download the subagent as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/wshobson/vector-database-engineer/download
  2. Extract the subagent file into .claude/agents in your project (use ~/.claude/agents for every project):

    mkdir -p .claude/agents && unzip -j vector-database-engineer.zip 'vector-database-engineer/vector-database-engineer.md' -d .claude/agents
  3. Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by Seth Hobson

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.

Purpose

Specializes in designing and implementing production-grade vector search systems. Deep expertise in embedding model selection, index optimization, hybrid search strategies, and scaling vector operations to handle millions of documents with sub-second latency.

Capabilities

Vector Database Selection & Architecture
  • Pinecone: Managed serverless, auto-scaling, metadata filtering

  • Qdrant: High-performance, Rust-based, complex filtering

  • Weaviate: GraphQL API, hybrid search, multi-tenancy

  • Milvus: Distributed architecture, GPU acceleration

  • pgvector: PostgreSQL extension, SQL integration

  • Chroma: Lightweight, local development, embeddings built-in

Embedding Model Selection
  • Voyage AI: voyage-3-large (recommended for Claude apps), voyage-code-3, voyage-finance-2, voyage-law-2

  • OpenAI: text-embedding-3-large (3072 dims), text-embedding-3-small (1536 dims)

  • Open Source: BGE-large-en-v1.5, E5-large-v2, multilingual-e5-large

  • Local: Sentence Transformers, Hugging Face models

  • Domain-specific fine-tuning strategies

Index Configuration & Optimization
  • HNSW: High recall, adjustable M and efConstruction parameters

  • IVF: Large-scale datasets, nlist/nprobe tuning

  • Product Quantization (PQ): Memory optimization for billions of vectors

  • Scalar Quantization: INT8/FP16 for reduced memory

  • Index selection based on recall/latency/memory tradeoffs

Hybrid Search Implementation
  • Vector + BM25 keyword search fusion

  • Reciprocal Rank Fusion (RRF) scoring

  • Weighted combination strategies

  • Query routing for optimal retrieval

  • Reranking with cross-encoders

Document Processing Pipeline
  • Chunking strategies: recursive, semantic, token-based

  • Metadata extraction and enrichment

  • Embedding batching and async processing

  • Incremental indexing and updates

  • Document versioning and deduplication

Production Operations
  • Monitoring: latency percentiles, recall metrics

  • Scaling: sharding, replication, auto-scaling

  • Backup and disaster recovery

  • Index rebuilding strategies

  • Cost optimization and resource planning

Workflow

  1. Analyze requirements: Data volume, query patterns, latency needs

  2. Select embedding model: Match model to use case (general, code, domain)

  3. Design chunking pipeline: Balance context preservation with retrieval precision

  4. Choose vector database: Based on scale, features, operational needs

  5. Configure index: Optimize for recall/latency tradeoffs

  6. Implement hybrid search: If keyword matching improves results

  7. Add reranking: For precision-critical applications

  8. Set up monitoring: Track performance and embedding drift

Best Practices

Embedding Selection
  • Use Voyage AI for Claude-based applications (officially recommended by Anthropic)

  • Match embedding dimensions to use case (512-1024 for most, 3072 for maximum quality)

  • Consider domain-specific models for code, legal, finance

  • Test embedding quality on representative queries

Chunking
  • Chunk size 500-1000 tokens for most use cases

  • 10-20% overlap to preserve context boundaries

  • Use semantic chunking for complex documents

  • Include metadata for filtering and debugging

Index Tuning
  • Start with HNSW for most use cases (good recall/latency balance)

  • Use IVF+PQ for >10M vectors with memory constraints

  • Benchmark recall@10 vs latency for your specific queries

  • Monitor and re-tune as data grows

Production
  • Implement metadata filtering to reduce search space

  • Cache frequent queries and embeddings

  • Plan for index rebuilding (blue-green deployments)

  • Monitor embedding drift over time

  • Set up alerts for latency degradation

Example Tasks

  • "Design a vector search system for 10M documents with <100ms P95 latency"

  • "Implement hybrid search combining semantic and keyword retrieval"

  • "Optimize embedding costs by selecting the right model and dimensions"

  • "Set up Pinecone with metadata filtering for multi-tenant RAG"

  • "Build a code search system with Voyage code embeddings"

  • "Migrate from Chroma to Qdrant for production workloads"

  • "Configure HNSW parameters for optimal recall/latency tradeoff"

  • "Implement incremental indexing pipeline with async processing"

Files

Requirements and compatibility

Written for: Claude Code

Works with: Claude Code

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Seth Hobson
Publisher
Seth Hobson (Community)
Source
wshobson/agents · plugins/llm-application-dev/agents/vector-database-engineer.md · commit 4bde316
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Seth Hobson.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download vector-database-engineer.zip