Scarletkc Vexor
scarletkc-vexor is a Claude Code plugin for the Build phase that adds vector-powered semantic search over files and code in your project.
by scarletkc · github.com/scarletkc/vexor
Give Claude Code meaning-based search over your repo so agents pull the right files without exact keyword matches.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install scarletkc-vexor@scarletkc/vexorBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:scarletkc/vexor") and the paste-ready config with skillselion.get_install_config("plugin:scarletkc/vexor").
What it does
scarletkc-vexor is a Claude Code plugin that adds a semantic search engine for files and code, so you and your coding agent can locate relevant snippets by intent instead of relying only on exact strings or directory memory. Solo builders shipping in growing repos install it when grep and filename search stop scaling—refactors, unfamiliar modules, and “where did we handle X?” moments. The catalog lists one plugin in the bundle with developer-tools positioning and vector-powered search as the headline capability. It is agent-tooling for the Build phase: you register the plugin in Claude Code, then invoke search as part of normal implementation and debugging loops. Intermediate complexity is typical because semantic search assumes a working local project tree and comfort letting agents query embeddings-backed results. It is not a deployment, SEO, or analytics product; it is narrowly focused retrieval infrastructure that makes downstream build, ship, and operate work faster when the codebase is the bottleneck.
Highlights
- Vector-powered semantic search across files and code in the workspace
- Finds related implementations when you remember behavior, not symbol names
- Bundled as a single Claude Code plugin skill focused on search
- Keywords emphasize semantic, files, search, and vexor as the install identity
- Fits builder workflows that mix human navigation and agent-driven exploration
Why builders use it
You waste cycles grep-hunting and opening wrong files because you know what the code should do, not the exact names or paths.
After you add the plugin, Claude Code can surface semantically related files and code so implementation and fixes start from the right context.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 213 stars, 0 votes.
FAQ
Who is scarletkc-vexor for?
It is for solo builders and developers using Claude Code who need faster, meaning-based discovery of files and code in an existing repository.
When should I use scarletkc-vexor?
Use it during Build when you are exploring unfamiliar modules, tracing behavior across the tree, or feeding agents better context than keyword grep alone.
How do I add scarletkc-vexor to my agent?
Install or register the scarletkc/vexor Claude Code plugin bundle from the repo, then use the bundled search skill or commands according to that plugin’s README in your Claude Code environment.
Comments
Share how you use scarletkc-vexor, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.