vexor-cli
Semantic file discovery via `vexor`. Use whenever locating where something is implemented/loaded/defined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing.
Best use case
vexor-cli is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Semantic file discovery via `vexor`. Use whenever locating where something is implemented/loaded/defined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing.
Semantic file discovery via `vexor`. Use whenever locating where something is implemented/loaded/defined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "vexor-cli" skill to help with this workflow task. Context: Semantic file discovery via `vexor`. Use whenever locating where something is implemented/loaded/defined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/vexor-cli/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How vexor-cli Compares
| Feature / Agent | vexor-cli | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Semantic file discovery via `vexor`. Use whenever locating where something is implemented/loaded/defined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing.
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.
Related Guides
AI Agent for Product Research
Browse AI agent skills for product research, competitive analysis, customer discovery, and structured product decision support.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
SKILL.md Source
# Vexor CLI Skill ## When to Use - You need to locate files by intent rather than exact filename or text match. - The repository is large enough that manual browsing or naive grep is too slow or ambiguous. - You want semantic discovery of where something is implemented, loaded, defined, or documented. ## Goal Find files by intent (what they do), not exact text. ## Use It Like This - Use `vexor` first for intent-based file discovery. - If `vexor` is missing, follow references/install-vexor.md. ## Command ```bash vexor "<QUERY>" [--path <ROOT>] [--mode <MODE>] [--ext .py,.md] [--exclude-pattern <PATTERN>] [--top 5] [--format rich|porcelain|porcelain-z] ``` ## Common Flags - `--path/-p`: root directory (default: current dir) - `--mode/-m`: indexing/search strategy - `--ext/-e`: limit file extensions (e.g., `.py,.md`) - `--exclude-pattern`: exclude paths by gitignore-style pattern (repeatable; `.js` → `**/*.js`) - `--top/-k`: number of results - `--include-hidden`: include dotfiles - `--no-respect-gitignore`: include ignored files - `--no-recursive`: only the top directory - `--format`: `rich` (default) or `porcelain`/`porcelain-z` for scripts - `--no-cache`: in-memory only, do not read/write index cache ## Modes (pick the cheapest that works) - `auto`: routes by file type (default) - `name`: filename-only (fastest) - `head`: first lines only (fast) - `brief`: keyword summary (good for PRDs) - `code`: code-aware chunking for `.py/.js/.ts` (best default for codebases) - `outline`: Markdown headings/sections (best for docs) - `full`: chunk full file contents (slowest, highest recall) ## Troubleshooting - Need ignored or hidden files: add `--include-hidden` and/or `--no-respect-gitignore`. - Scriptable output: use `--format porcelain` (TSV) or `--format porcelain-z` (NUL-delimited). - Get detailed help: `vexor search --help`. - Config issues: `vexor doctor` or `vexor config --show` diagnoses API, cache, and connectivity (tell the user to set up). ## Examples ```bash # Find CLI entrypoints / commands vexor search "typer app commands" --top 5 ``` ```bash # Search docs by headings/sections vexor search "user authentication flow" --path docs --mode outline --ext .md --format porcelain ``` ```bash # Locate config loading/validation logic vexor search "config loader" --path . --mode code --ext .py ``` ```bash # Exclude tests and JavaScript files vexor search "config loader" --path . --exclude-pattern tests/** --exclude-pattern .js ``` ## Tips - First time search will index files (may take a minute). Subsequent searches are fast. Use longer timeouts if needed. - Results return similarity ranking, exact file location, line numbers, and matching snippet preview. - Combine `--ext` with `--exclude-pattern` to focus on a subset (exclude rules apply on top). ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
vexor
Vector-powered CLI for semantic file search with a Claude/Codex skill
nextjs-best-practices
Next.js App Router principles. Server Components, data fetching, routing patterns.
network-101
Configure and test common network services (HTTP, HTTPS, SNMP, SMB) for penetration testing lab environments. Enable hands-on practice with service enumeration, log analysis, and security testing against properly configured target systems.
neon-postgres
Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration
nanobanana-ppt-skills
AI-powered PPT generation with document analysis and styled images
multi-agent-patterns
This skill should be used when the user asks to "design multi-agent system", "implement supervisor pattern", "create swarm architecture", "coordinate multiple agents", or mentions multi-agent patterns, context isolation, agent handoffs, sub-agents, or parallel agent execution.
monorepo-management
Build efficient, scalable monorepos that enable code sharing, consistent tooling, and atomic changes across multiple packages and applications.
monetization
Estrategia e implementacao de monetizacao para produtos digitais - Stripe, subscriptions, pricing experiments, freemium, upgrade flows, churn prevention, revenue optimization e modelos de negocio SaaS.
modern-javascript-patterns
Comprehensive guide for mastering modern JavaScript (ES6+) features, functional programming patterns, and best practices for writing clean, maintainable, and performant code.
microservices-patterns
Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.
mcp-builder
Create MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. The quality of an MCP server is measured by how well it enables LLMs to accomplish real-world tasks.
makepad-skills
Makepad UI development skills for Rust apps: setup, patterns, shaders, packaging, and troubleshooting.