cli-plugins-skills

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

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

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 command catalog that is lean on concept explanations but suffers from garbage/duplicate entries, non-executable placeholder examples, and no validation guidance for destructive operations. It also keeps the full reference inline rather than splitting it into bundled files.

Suggestions

Remove generator artifacts and duplicates: 'PLUGIN_NAME', 'plugin plugin', 'skills skills', 'skills skillssh', and the repeated 'skills list' / 'skills install' entries.

Add at least one fully runnable, real-value example per destructive command and a validation/confirmation step (e.g. run 'memory list' before 'memory delete', confirm the targeted id).

Move the bulk command reference into a bundled reference file (e.g. references/commands.md) and keep SKILL.md as a concise overview with a clearly signaled link, so progressive disclosure improves.

Dimension	Reasoning	Score
Conciseness	The reference avoids concept-explanation fluff, but it carries clear bloat from generator artifacts and duplicates ('PLUGIN_NAME', 'plugin plugin', 'skills skills', 'skills skillssh', repeated 'skills list' and 'skills install') that should be trimmed; not 2 because no concepts are over-explained.	3 / 5
Actionability	Real commands and flags are listed, but every example is a non-executable template using placeholders like '<query>', '<id>', and '[query]', so examples are not copy-paste runnable; not 4 because the placeholders are pervasive rather than minor gaps.	3 / 5
Workflow Clarity	The body is a flat command catalog with no sequencing, and destructive/batch commands ('memory clear', 'memory delete', 'skills delete', 'skills disable', 'plugin remove') have no validation or feedback steps; the destructive-operations cap allows at most 3, and the absent sequence/validation pulls it to 2.	2 / 5
Progressive Disclosure	Section headers per subcommand give some structure, but the entire ~380-line command reference is inlined in SKILL.md with no external reference files (none of references/scripts/assets exist); the simple-skill exception does not apply at this length, so content that should be split out stays inline.	3 / 5
	Total	11 / 20 Passed

Description

71%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 specific and concrete with good trigger keywords, but it lacks any explicit 'when to use' guidance, which caps its completeness. It is a strong what-statement weakened by the missing trigger clause.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to manage Omni skills, plugins, or persistent memory from the command line.'

Add common synonyms / file extensions (e.g. 'search memories', '.skill packages') to broaden natural keyword coverage.

Consider whether bundling skills, plugins, and memory into one skill risks overlap with dedicated skills; if so, sharpen the niche in the description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across three domains ('list, install, test, remove', 'create, configure', 'search, add, clear'), matching the comprehensive-coverage anchor; not 4 because coverage is broad rather than having minor gaps.	5 / 5
Completeness	The 'what' is explicit and concrete, but there is no 'Use when...' clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural action terms users would say ('search', 'add', 'clear', 'install', 'list') plus nouns ('skills', 'plugins', 'memory'), but 'persistent memory' and 'Omni Skills' are product-jargon and synonyms/file extensions are missing, so it falls short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific CLI product and its three subsystems, giving a clear niche with minimal conflict risk; not 5 because bundling skills, plugins, and memory into one description creates minor overlap with single-purpose variants.	4 / 5
	Total	16 / 20 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: ea0cdc5

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