CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-plugins-skills

Manage Omni Skills (list, install, test, remove), plugins (create, configure), and persistent memory (search, add, clear) from the CLI.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/cli-plugins-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

43%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 an auto-generated CLI reference with genuine syntax and flags, but it contains duplicated sections, placeholder-only examples, junk generator artifacts, and no workflow or validation guidance for destructive commands. It reads as raw generator output rather than a curated skill.

Suggestions

Add validation and confirmation guidance for destructive operations (`memory clear`, `skills delete`, `plugin remove`), e.g. list affected items first, then require `--yes`, and verify the result afterward.

Move the bulk command/flag reference to a `references/cli.md` file and keep only a quick-start and common-use examples in SKILL.md.

Fix generator artifacts: remove the `PLUGIN_NAME`, `plugin plugin`, `skills skills`, and `skills skillssh` sections and the duplicate `skills list` / `skills install` sections, and make examples show realistic values instead of repeating the heading.

DimensionReasoningScore

Conciseness

No concept over-explanation, but roughly 40% of tokens are redundant: every "Example:" block repeats its heading verbatim, and `skills list` and `skills install` sections appear twice each. Could be tightened substantially.

3 / 5

Actionability

Commands and flags are concrete and syntactically real, but examples are bare placeholders (`omniroute skills install <packageId>`) with no realistic values, and generator-junk entries (`PLUGIN_NAME`, `plugin plugin`, `skills skills`, `skills skillssh`) are not executable.

3 / 5

Workflow Clarity

The body is a flat command catalog with no sequencing or usage guidance, and destructive operations (`memory clear`, `skills delete`, `plugin remove`) appear with a `--yes` flag but no validation or warning. More organized than incoherent, so not 1, but there is no sequence or checkpoint at all.

2 / 5

Progressive Disclosure

No bundle files exist, and ~380 lines of API reference are inlined in SKILL.md where they belong in a separate reference file. Section headers provide real structure, so not 2, but the bulk content is not split out, so not 4.

3 / 5

Total

11

/

20

Passed

Description

66%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 concrete, third-person, and well-structured across its three domains, but it has no explicit "when to use" guidance and its action list doesn't fully match the skill's actual subcommands. Adding a trigger clause and aligning the action list with the real command surface would raise it.

Suggestions

Add an explicit trigger clause, e.g. "Use when managing omniroute skills, plugins, or persistent memory from the command line."

Align the listed actions with the actual subcommands: drop "test"/"configure" and include marketplace, enable/disable, and execute operations.

DimensionReasoningScore

Specificity

Lists several concrete actions across three domains ("list, install, test, remove", "create, configure", "search, add, clear"), but coverage has minor gaps: it claims "test" and "configure" which have no corresponding subcommands in the body, and omits marketplace, enable/disable, execute, and update.

4 / 5

Completeness

The "what" is clear (manage skills, plugins, and memory from the CLI), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural-keyword coverage ("Omni Skills", "plugins", "persistent memory", "install", "search"), but misses common variations users might say such as "omniroute", "marketplace", "add memory", or "remove/delete a skill".

4 / 5

Distinctiveness Conflict Risk

"Omni Skills" and "from the CLI" scope the skill to a distinct niche, but the generic terms "skills", "plugins", and "memory" create minor overlap risk with other tooling or memory-management skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

diegosouzapw/OmniRoute

Path

skills/cli-plugins-skills/SKILL.md

Revision

5b3be70

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill