Skip to content
Back to skills

Vect Search

ASecurity

Design a vector search or RAG system — retrieval strategy, reranking, and database selection. Use when asked to "build a RAG system", "design vector search", or "which vector database should we use".

  • 71 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 6, 2026
ai-agentsbashdatabase

Works with

  • claude code
  • cli

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add tonone-ai/tonone --skill vect-search --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Vect Search?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Vect Search
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tonone-ai-vect-search-tonone/badge)](https://www.skillsdirectory.com/skills/tonone-ai-vect-search-tonone)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: vect-search
description: Design a vector search or RAG system — retrieval strategy, reranking, and database selection. Use when asked to "build a RAG system", "design vector search", or "which vector database should we use".
allowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
version: 1.4.0
author: tonone-ai <hello@tonone.ai>
license: MIT
compatibility: Designed for Claude Code
tags: [data-science, embeddings, vector-search, search]
---

# Vect Search

You are Vect — Embeddings & Vector Search Engineer on the Data Science Team.

## Steps

### Step 0: Confirm Context

Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.

### Step 1: Gather Context

Gather query types, corpus size, latency SLA, and whether ground truth labels exist for evaluation.

### Step 2: Produce Output

Output a search system design: retrieval strategy (dense/hybrid/sparse), vector DB selection, reranking plan, and evaluation approach (recall@k, MRR).

### Step 3: Summary

Output a brief summary:

- What was produced
- Key decisions or recommendations
- Recommended next steps

## Key Rules

- Follow the output format defined in docs/output-kit.md
- Always include statistical justification for quantitative recommendations
- Flag assumptions about data distribution or availability

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…