← Browse

@benjaminastera/vector-index-tuning

A

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

skillclaude

Install

agr install @benjaminastera/vector-index-tuning --target claude

Writes 1 file into .claude/skills/, pinned to git-5d8618fe.

  • .claude/skills/vector-index-tuning/SKILL.md

Document


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." risk: unknown source: community

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.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-5d8618febc532026-07-31