Claude Cursor Skill

vector-index-tuning

Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.

LLM Mart · 0 points · 17 views 0 listing impressions 0 install-command copies
Download wshobson-agents-plugins_llm-application-dev_skills_vector-index-tuning-554237f.zip · 4 KB

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/llm-application-dev/skills/vector-index-tuning
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Vector Index Tuning

Guide to optimizing vector indexes for production performance.

When to Use This Skill

  • Tuning HNSW parameters
  • Implementing quantization
  • Optimizing memory usage
  • Reducing search latency
  • Balancing recall vs speed
  • Scaling to billions of vectors

Core Concepts

1. Index Type Selection

Data Size           Recommended Index
────────────────────────────────────────
< 10K vectors  →    Flat (exact search)
10K - 1M       →    HNSW
1M - 100M      →    HNSW + Quantization
> 100M         →    IVF + PQ or DiskANN

2. HNSW Parameters

Parameter Default Effect
M 16 Connections per node, ↑ = better recall, more memory
efConstruction 100 Build quality, ↑ = better index, slower build
efSearch 50 Search quality, ↑ = better recall, slower search

3. Quantization Types

Full Precision (FP32): 4 bytes × dimensions
Half Precision (FP16): 2 bytes × dimensions
INT8 Scalar:           1 byte × dimensions
Product Quantization:  ~32-64 bytes total
Binary:                dimensions/8 bytes

Templates and detailed worked examples

Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.

Best Practices

Do's

  • Benchmark with real queries - Synthetic may not represent production
  • Monitor recall continuously - Can degrade with data drift
  • Start with defaults - Tune only when needed
  • Use quantization - Significant memory savings
  • Consider tiered storage - Hot/cold data separation

Don'ts

  • Don't over-optimize early - Profile first
  • Don't ignore build time - Index updates have cost
  • Don't forget reindexing - Plan for maintenance
  • Don't skip warming - Cold indexes are slow
Files (agents)
  • references
    • details.md 12.9 KB
      Loading…
  • SKILL.md 2.3 KB
    ---
    name: vector-index-tuning
    description: Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.
    ---
    
    # Vector Index Tuning
    
    Guide to optimizing vector indexes for production performance.
    
    ## When to Use This Skill
    
    - Tuning HNSW parameters
    - Implementing quantization
    - Optimizing memory usage
    - Reducing search latency
    - Balancing recall vs speed
    - Scaling to billions of vectors
    
    ## Core Concepts
    
    ### 1. Index Type Selection
    
    ```
    Data Size           Recommended Index
    ────────────────────────────────────────
    < 10K vectors  →    Flat (exact search)
    10K - 1M       →    HNSW
    1M - 100M      →    HNSW + Quantization
    > 100M         →    IVF + PQ or DiskANN
    ```
    
    ### 2. HNSW Parameters
    
    | Parameter          | Default | Effect                                               |
    | ------------------ | ------- | ---------------------------------------------------- |
    | **M**              | 16      | Connections per node, ↑ = better recall, more memory |
    | **efConstruction** | 100     | Build quality, ↑ = better index, slower build        |
    | **efSearch**       | 50      | Search quality, ↑ = better recall, slower search     |
    
    ### 3. Quantization Types
    
    ```
    Full Precision (FP32): 4 bytes × dimensions
    Half Precision (FP16): 2 bytes × dimensions
    INT8 Scalar:           1 byte × dimensions
    Product Quantization:  ~32-64 bytes total
    Binary:                dimensions/8 bytes
    ```
    
    ## Templates and detailed worked examples
    
    Full template library and detailed worked examples live in `references/details.md`. Read that file when you need the concrete templates.
    
    ## Best Practices
    
    ### Do's
    
    - **Benchmark with real queries** - Synthetic may not represent production
    - **Monitor recall continuously** - Can degrade with data drift
    - **Start with defaults** - Tune only when needed
    - **Use quantization** - Significant memory savings
    - **Consider tiered storage** - Hot/cold data separation
    
    ### Don'ts
    
    - **Don't over-optimize early** - Profile first
    - **Don't ignore build time** - Index updates have cost
    - **Don't forget reindexing** - Plan for maintenance
    - **Don't skip warming** - Cold indexes are slow
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.