cli-plugins-skills

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

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Risky

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/cli-plugins-skills/SKILL.md

Quality

Content

50%

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 that lists subcommands and flags but provides only stub examples with placeholder arguments, no workflow sequencing, and no validation guidance for destructive operations. It is organized but redundant and not genuinely actionable.

Suggestions

Replace placeholder stub examples ('omniroute memory add') with complete, copy-paste-ready invocations using realistic argument values.

Add validation/confirmation guidance for destructive and batch operations (e.g., show what 'skills delete --yes' confirms before removing).

De-duplicate repeated subcommand sections ('skills list', 'skills install') and group memory/plugin/skills commands into clearly separated sections for better navigation.

Dimension	Reasoning	Score
Conciseness	The body avoids concept padding, but bare 'Example:' stubs that merely restate the heading (e.g., 'omniroute memory add') and duplicated subcommand sections ('skills list', 'skills install' each appear twice) waste tokens, matching 'mostly efficient but could be tightened' rather than the lean level-3 anchor.	2 / 3
Actionability	Flags are listed, but every example uses placeholder arguments ('<query>', '<id>', '<name>') with no complete executable invocation including real values, matching 'some concrete guidance but incomplete; missing key details' rather than copy-paste-ready level-3 examples.	2 / 3
Workflow Clarity	Commands are presented as a flat catalog with no multi-step sequencing, and destructive/batch operations ('skills delete', 'memory clear') list only a bare '--yes' flag with no validation or confirmation guidance; per the scoring notes, missing feedback loops for destructive ops caps this at 2.	2 / 3
Progressive Disclosure	It is a single ~380-line monolithic command catalog with sections, but groupings are interleaved and duplicated (skills/memory/plugin mixed) with content that could be split or grouped better, matching 'some structure but could be better organized' rather than the cleanly navigated level-3 anchor.	2 / 3
	Total	8 / 12 Passed

Description

67%

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 specific and distinctive, clearly scoping a CLI tool across skills, plugins, and memory subsystems with concrete verbs. Its main weakness is the absence of explicit trigger guidance telling Claude when to use it.

Suggestions

Add an explicit 'Use when…' clause naming natural trigger phrases (e.g., 'Use when the user wants to manage Omni Skills, plugins, or persistent memory from the command line').

Include common user-facing term variations beyond CLI jargon so trigger matching is broader.

Clarify the triggering context (e.g., operating the omniroute CLI) to make the when-to-use condition unambiguous.

Dimension	Reasoning	Score
Specificity	Enumerates concrete actions across three domains ('list, install, test, remove', 'create, configure', 'search, add, clear'), matching the 'lists multiple specific concrete actions' anchor rather than the partial level-2 anchor.	3 / 3
Completeness	Clearly answers what the skill does, but lacks any 'Use when…' or equivalent explicit trigger guidance for when to invoke it; per the judging guideline, missing explicit trigger guidance caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant keywords ('Skills', 'plugins', 'memory', 'install', 'CLI') but is framed as technical CLI jargon with no natural user phrasing, matching 'some relevant keywords but missing common variations' rather than full level-3 coverage.	2 / 3
Distinctiveness Conflict Risk	Scoped to a named CLI tool with three distinct subsystems, giving it a clear niche unlikely to trigger for the wrong skill, matching the 'clear niche with distinct triggers' anchor rather than a generic level-1 or level-2 description.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: diegosouzapw/OmniRoute
Path: skills/cli-plugins-skills/SKILL.md
Commit: 3070925

Reviewed: 2 days 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.