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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted skill that provides lean, actionable guidance for semantic file discovery using vexor. It excels at concrete examples, clear flag documentation, and mode selection guidance. The content is appropriately scoped for a single-purpose CLI tool with good organization and minimal unnecessary explanation.

Dimension	Reasoning	Score
Conciseness	The content is efficient and avoids explaining concepts Claude already knows. Minor verbosity in the Tips section (e.g., explaining that first-time indexing takes a minute) and some flag descriptions could be slightly tighter, but overall it respects token budget well.	4 / 5
Actionability	Provides fully executable, copy-paste ready commands with concrete examples covering multiple use cases (CLI entrypoints, docs search, config loading, exclusion patterns). Flag reference is specific and complete with defaults noted.	5 / 5
Workflow Clarity	This is a single-purpose, non-destructive tool (search/discovery). The workflow is unambiguous: run vexor with a query and flags. Troubleshooting section provides clear guidance for common issues. No destructive or batch operations requiring validation checkpoints.	5 / 5
Progressive Disclosure	Good structure with clear sections (Goal, Command, Flags, Modes, Troubleshooting, Examples, Tips). References install instructions to a separate file (references/install-vexor.md). Minor gap: the bundle has no files to verify the reference path, and the skill could benefit from a slightly clearer signaling of the install reference.	4 / 5
	Total	18 / 20 Passed

Description

78%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description that clearly communicates its purpose and when to use it, including a helpful preference directive. Its main weakness is that it could be more specific about the range of capabilities and include more natural trigger terms users might use when searching for code. The explicit tool name ('vexor') and clear 'when' guidance are strong points.

Suggestions

Add more natural trigger synonyms users might say, such as 'find', 'search', 'where is', 'look up', 'codebase', to improve discoverability.

List additional specific capabilities if they exist (e.g., 'find references', 'locate imports', 'discover dependencies') to strengthen specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (semantic file discovery) and the tool ('vexor'), and describes one concrete action (locating where something is implemented/loaded/defined), but doesn't list multiple specific actions or capabilities beyond that single use case.	3 / 5
Completeness	Clearly answers both 'what' (semantic file discovery via vexor) and 'when' (locating implementations/definitions in medium or large repos, when file location is unclear), with an explicit preference directive ('Prefer this over manual browsing').	5 / 5
Trigger Term Quality	Includes good natural trigger terms like 'locating', 'implemented', 'loaded', 'defined', 'file location', 'repo', and 'file discovery'. Missing some common synonyms users might say like 'find', 'search', 'where is', 'codebase', or 'source code'.	4 / 5
Distinctiveness Conflict Risk	The mention of a specific tool ('vexor') and the focus on semantic file discovery in repos makes it fairly distinct. Minor overlap risk with general code search or file browsing skills, but the semantic search angle and tool name help differentiate it.	4 / 5
	Total	16 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/vexor-cli/SKILL.md
Commit: 900c504

Reviewed: 5 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.