Name: vexor-cli
Rating: 62.4 (1 reviews)
Author: administrakt0r

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

75%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/vexor-cli/SKILL.md

The canonical home for this skill is vexor-cli in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

71%Weight 40%Scale 1-5

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

A mostly executable, well-structured reference for a simple single-purpose CLI skill, with concise command documentation and useful examples. Its main weakness is a broken external reference (the install-vexor.md file is cited but absent) and a minor command-syntax inconsistency.

Suggestions

Add the missing references/install-vexor.md file (or remove the reference and inline a one-line install command) so the 'if vexor is missing' fallback resolves.

Reconcile the base command syntax: the Command block shows 'vexor "<QUERY>"' but every example uses 'vexor search "<QUERY>"' — pick one and use it consistently.

Trim the Tips section's restatement of flag behavior already covered in Common Flags to tighten token use.

Dimension	Reasoning	Score
Conciseness	Lean command/flags/modes/examples with little padding and no over-explanation of concepts Claude already knows; minor redundancy between the Common Flags list and Tips. Not 5 because the Tips section restates flag behavior already covered; not 3 because it is clearly efficient overall.	4 / 5
Actionability	Provides copy-paste-ready bash examples covering common cases (entrypoints, docs, config loader, exclusions) with real flags. Not 5 because the documented base command 'vexor "<QUERY>"' conflicts with examples that use 'vexor search "..."', leaving a small executable gap; not 3 because guidance is mostly concrete and runnable.	4 / 5
Workflow Clarity	Primary action (run vexor search) is unambiguous and a small fallback branch exists ('If vexor is missing, follow references/install-vexor.md'). Not 5 because the fallback recovery path points to an underspecified install reference rather than concrete steps; not 3 because the sequence is clear with no destructive/batch validation concerns.	4 / 5
Progressive Disclosure	Sections are well-organized (Goal, Command, Flags, Modes, Troubleshooting, Examples, Tips) and content is appropriately inline for a simple skill, but the sole external reference 'references/install-vexor.md' is referenced and does not exist, breaking navigation. Not 4 because the one signaled reference is dead; not 2 because the in-body structure itself is good rather than minimal.	3 / 5
	Total	15 / 20 Passed

Description

78%Weight 40%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.

A strong, concise description that clearly states both capability and explicit use-when triggers in third person. It is largely distinct from other skills, with only minor overlap risk against general code-search tools.

Dimension	Reasoning	Score
Specificity	Names the domain ('Semantic file discovery via vexor') and one concrete action family ('locating where something is implemented/loaded/defined'), but coverage is not comprehensive. Not 2 because a concrete action is stated; not 4 because only a single action family is given.	3 / 5
Completeness	Explicitly answers 'what' (semantic file discovery via vexor) and 'when' ('Use whenever locating where something is implemented/loaded/defined... or when the file location is unclear') with concrete trigger phrases. Not 4 because the 'when' is already explicit and specific rather than merely adequate.	5 / 5
Trigger Term Quality	Includes natural phrasings users would say ('where something is implemented/loaded/defined', 'file location is unclear'), with only a few synonyms missing. Not 5 because it lacks broader synonyms and file/extension terms; not 3 because keyword coverage is clearly good rather than partial.	4 / 5
Distinctiveness Conflict Risk	Clear niche (intent-based file discovery via a named tool) with distinct triggers, but minor overlap risk with general code-search/grep skills. Not 5 because file-location search is a crowded skill area; not 3 because the semantic/intent framing and tool name make it largely distinct.	4 / 5
	Total	16 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

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

Reviewed: 6 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.