vector-database-engineer▌
sickn33/antigravity-awesome-skills · updated Apr 8, 2026
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.
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
- Analyze data characteristics and query patterns
- Select appropriate embedding model
- Design chunking and preprocessing pipeline
- Choose vector database and index type
- Configure metadata schema for filtering
- Implement hybrid search if needed
- Optimize for latency/recall tradeoffs
- Set up monitoring and reindexing strategies
Best Practices
- Choose embedding dimensions based on use case (384-1536)
- 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
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★43 reviews- ★★★★★James Taylor· Dec 28, 2024
I recommend vector-database-engineer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Shikha Mishra· Dec 20, 2024
vector-database-engineer reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Jin Iyer· Dec 16, 2024
vector-database-engineer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Nikhil Patel· Dec 4, 2024
vector-database-engineer reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★James Kapoor· Nov 19, 2024
Keeps context tight: vector-database-engineer is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Carlos Tandon· Nov 7, 2024
Useful defaults in vector-database-engineer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Alexander Malhotra· Oct 26, 2024
I recommend vector-database-engineer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Nikhil Rao· Oct 10, 2024
vector-database-engineer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Oshnikdeep· Sep 25, 2024
vector-database-engineer has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Sofia Kapoor· Sep 17, 2024
vector-database-engineer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 43