Skill

Search Files Semantically with Vector CLI

Vector-powered CLI tool for semantic file search, packaged as a Claude/Codex skill.

Works with claudecodex

65
Spark score
out of 100
Updated last month
Version 13.3.0
Models
claude

Add to Favorites

Why it matters

Leverage a vector-powered CLI for semantic file search, enhanced by Claude and Codex capabilities. This skill provides guidance for building and using such a tool.

Outcomes

What it gets done

01

Perform semantic file searches using a vector-powered CLI.

02

Integrate Claude and Codex for enhanced search functionality.

03

Understand patterns and guidance for vector-based file searching.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-vexor | bash

Overview

Vexor

A minimal pointer to Vexor, a vector-powered CLI for semantic file search packaged as a Claude/Codex skill, without enumerating specific commands in this description. Use for semantic/conceptual file search tasks where exact keyword matching (grep-style) isn't sufficient; consult the linked source repository for CLI specifics.

What it does

This skill wraps Vexor, a vector-powered CLI tool for semantic file search, as a Claude/Codex-compatible skill. The source material is a minimal repository pointer rather than a detailed specification: it names the tool's purpose - semantic search over files using vector embeddings rather than plain keyword matching - and links to the source repository for the actual CLI commands, installation steps, and configuration details, without itself enumerating specific flags or usage patterns. Its own metadata marks the risk level as "safe."

When to use - and when NOT to

Use this skill when a task calls for finding files by meaning or concept rather than exact filename or keyword match - semantic search over a codebase or document set where a vector-based CLI tool would surface more relevant results than grep-style text search.

Because the grounding material here doesn't itself detail Vexor's specific commands or configuration, this skill should be paired with a look at the linked source repository before relying on specifics for a task. It is not a general-purpose file search or grep replacement for exact-match lookups where a vector-based semantic approach adds no value.

Inputs and outputs

Input is a file-search task where semantic or conceptual matching is more useful than exact keyword matching. Output is search results produced by the Vexor CLI, with the concrete command syntax and configuration to consult in the linked repository rather than fully specified here.

Integrations

Points to its own source repository (github.com/scarletkc/vexor) as the canonical reference for CLI usage, and is designed to integrate as a skill within Claude or Codex sessions.

Who it's for

Developers using Claude or Codex who want semantic, vector-based file search available as a CLI tool inside their coding sessions, rather than relying solely on exact-match grep-style search.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.