CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vexor

Vector-powered CLI for semantic file search with a Claude/Codex skill

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/vexor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

18%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.

The body is a boilerplate skeleton: every section either repeats the description or states circularly that the skill provides guidance, with no commands, examples, or workflow. It is well-sectioned but substantively empty, so the skill cannot actually be used from this file alone.

Suggestions

Replace the circular Instructions section with concrete, executable guidance: installation (e.g. `npm i -g vexor` or equivalent), indexing a directory, and 1-2 query examples with expected output.

Delete the verbatim Overview restatement and the "Use this skill when you need to work with..." sentence, which repeat the description without adding information.

If detailed usage exists, add a short workflow (index → query → review matches) and move extended material into a references/ file linked one level deep from the body.

DimensionReasoningScore

Conciseness

The body is short but almost entirely padded: the Overview restates the frontmatter description verbatim, and "Use this skill when you need to work with vector-powered cli..." and "This skill provides guidance and patterns for..." are circular sentences that convey nothing new. This matches the anchor for noticeable verbosity with several unnecessary padded sections rather than lean, earning-its-place content.

2 / 5

Actionability

There is no concrete guidance anywhere in the body — no CLI command, installation step, code example, or usage pattern; the only substance is a link to the source repository. This matches the anchor for entirely vague content that describes rather than instructs.

1 / 5

Workflow Clarity

No steps or sequence of any kind are present, not even for the single task of running the CLI, so the simple-skill exception cannot apply — the one action is not unambiguous. This matches the anchor for steps missing and no validation, and nothing is present to justify level 2's rough sequence.

1 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (no references/, scripts/, or assets/ exist), and the body has clear sections (Overview, When to Use, Instructions) plus one clearly signaled external link, which per the guidelines can support a high score. It falls short of 5 because the Instructions section promises guidance that is not there, leaving a minor organization gap.

4 / 5

Total

8

/

20

Passed

Description

53%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.

The description is a concrete one-line "what" for a niche tool, but it has no "use when" trigger guidance and only a single action, leaving it at the midpoint of the rubric. It avoids vague fluff yet stops just short of the explicit, trigger-rich style of the top examples.

Suggestions

Add an explicit trigger clause, e.g. "Use when you need to find files or code by meaning rather than keywords, or when the user mentions semantic search or vector search."

List 2-3 concrete capabilities of the CLI (e.g. indexing a directory, querying by natural language, returning ranked file matches) instead of the single "semantic file search" action.

Drop the filler phrase "with a Claude/Codex skill" and replace it with natural synonyms users would say ("find files by meaning", "semantic code search").

DimensionReasoningScore

Specificity

"Vector-powered CLI for semantic file search" names the domain and one concrete action (semantic file search), matching the anchor for 1-2 concrete actions without comprehensive coverage. The trailing phrase "with a Claude/Codex skill" adds no action, so it does not reach the several-actions level of 4.

3 / 5

Completeness

The description gives a reasonably clear "what" (a vector-powered CLI for semantic file search) but contains no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the "what" is concrete rather than vague.

3 / 5

Trigger Term Quality

Terms like "semantic file search", "vector", and "CLI" are relevant keywords, but common user phrasings ("find files by meaning", "search codebase") and synonyms/extensions are absent, matching the anchor for some relevant keywords but missing variations. It is above level 2 because the keywords are domain-specific rather than generic filler.

3 / 5

Distinctiveness Conflict Risk

The niche (vector/semantic file search CLI) is fairly distinct and unlikely to trigger for unrelated skills, giving minor overlap risk only with closely related search skills — matching the anchor for "mostly distinct". It falls short of 5 because no explicit triggers are stated to fully separate it from similar search/retrieval skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/vexor/SKILL.md

Reviewed

Table of Contents

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.