multiAI Summary Pending
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.
28,273 stars
bysickn33
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/vector-index-tuning/SKILL.md --create-dirs "https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/plugins/antigravity-awesome-skills-claude/skills/vector-index-tuning/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/vector-index-tuning/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How vector-index-tuning Compares
| Feature / Agent | vector-index-tuning | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Vector Index Tuning Guide to optimizing vector indexes for production performance. ## Use this skill when - Tuning HNSW parameters - Implementing quantization - Optimizing memory usage - Reducing search latency - Balancing recall vs speed - Scaling to billions of vectors ## Do not use this skill when - You only need exact search on small datasets (use a flat index) - You lack workload metrics or ground truth to validate recall - You need end-to-end retrieval system design beyond index tuning ## Instructions 1. Gather workload targets (latency, recall, QPS), data size, and memory budget. 2. Choose an index type and establish a baseline with default parameters. 3. Benchmark parameter sweeps using real queries and track recall, latency, and memory. 4. Validate changes on a staging dataset before rolling out to production. Refer to `resources/implementation-playbook.md` for detailed patterns, checklists, and templates. ## Safety - Avoid reindexing in production without a rollback plan. - Validate changes under realistic load before applying globally. - Track recall regressions and revert if quality drops. ## Resources - `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.