embedding-strategies

Select and optimize embedding models for semantic search and RAG applications.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill embedding-strategies-sanketadlak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: embedding-strategies
Source: https://github.com/SanketAdlak/PDMProjectDesign/tree/main/.agents/skills/embedding-strategies
Command: npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill embedding-strategies-sanketadlak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the right embedding model and chunking strategy for vector search is difficult, and poor choices lead to weak retrieval quality in RAG pipelines. This Skill provides model comparisons, ready-to-use embedding templates, and evaluation metrics to make informed decisions. ## Core Features & Use Cases - Model Selection Guidance: Compare Voyage AI, OpenAI, and open-source embedding models by dimensions, token limits, and domain fit. - Embedding Templates: Production-ready Python code for Voyage AI, OpenAI (with Matryoshka dimension reduction), and local sentence-transformers models. - Chunking Strategies: Token-based, sentence-based, semantic-section, and recursive character splitting implementations. - Quality Evaluation: Compute precision@k, recall@k, MRR, and NDCG to compare embedding models on retrieval tasks. - Use Case: When building a RAG system for legal documents, use this Skill to select voyage-law-2, implement token-based chunking with overlap, and validate retrieval quality with evaluation metrics. ## Quick Start Ask the AI to help you choose an embedding model and set up a chunking and embedding pipeline for your RAG application.

Frequently Asked Questions about embedding-strategies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose an embedding model for RAG?

Match the model to your use case: voyage-3-large is recommended for Claude applications, text-embedding-3-large for OpenAI stacks, and bge-large-en-v1.5 for local deployment. Consider dimensions, max token limits, and whether you need domain-specific models like voyage-code-3 or voyage-law-2.

What chunking strategy works best for embeddings?

Token-based chunking with overlap (e.g., 512 tokens with 50 overlap) works well for general text. Sentence-based chunking preserves semantic boundaries, while recursive character splitting handles mixed content. Avoid over-chunking, which loses important context.

Voyage AI vs OpenAI embeddings, which should I use?

Voyage AI is recommended by Anthropic for Claude applications and offers domain-specific models for code, finance, and legal content. OpenAI's text-embedding-3 models support Matryoshka dimension reduction, letting you trade accuracy for smaller vector sizes.

Can I reduce embedding dimensions to save storage?

Yes, OpenAI's text-embedding-3 models support Matryoshka dimensionality reduction via the dimensions parameter, letting you request smaller vectors like 512 dimensions. This reduces storage and speeds up similarity search with some accuracy trade-off.

How do I evaluate embedding model quality for retrieval?

Use retrieval metrics like precision@k, recall@k, MRR, and NDCG against a labeled set of queries with known relevant documents. Embed your corpus with each candidate model, run the queries, and compare the averaged metric scores.

Why do BGE and E5 models need query prefixes?

BGE and E5 models are trained with instruction prefixes that distinguish queries from documents. E5 requires 'query:' and 'passage:' prefixes, while BGE benefits from a retrieval instruction prefix on queries. Omitting them degrades retrieval accuracy.