omni-cli-tools

Manage CLI tool integrations exposed via the API. List, configure, and invoke CLI tool plugins that extend OmniRoute's automation surface.

Quality

45%

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 ./skills/omni-cli-tools/SKILL.md

Quality

Content

32%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 SKILL.md is an auto-generated API catalog: executable curl examples give it some actionability, but it is highly repetitive, lacks any workflow/validation guidance for destructive and batch endpoints, and inlines a large endpoint reference that belongs in a separate file.

Suggestions

Move the bulk endpoint catalog into a separate references file (e.g. references/endpoints.md) and keep SKILL.md as a concise overview that links to it and to the OpenAPI spec.

Replace boilerplate titles like "GET cli tools › all statuses" with real descriptions, and factor the repeated Authorization/Content-Type headers into a shared snippet so the curl blocks shrink.

Add a short workflow with validation for the destructive DELETE and batch POST /apply operations (e.g. GET status -> confirm -> mutate -> re-GET to verify), and inline at least one real request payload per POST/PUT instead of `-d '{}'`.

Dimension	Reasoning	Score
Conciseness	The body repeats ~60 near-identical curl header blocks and pads many sections with meaningless auto-generated one-liners like "GET cli tools › all statuses", fitting the 'noticeably verbose; padded sections' anchor rather than the mostly-efficient anchor 3.	2 / 5
Actionability	Each endpoint ships an executable curl command, but POST/PUT bodies are uniformly `-d '{}'` with no real payload schema inlined, leaving concrete guidance incomplete per the 'some concrete guidance but incomplete' anchor.	3 / 5
Workflow Clarity	The content is a flat endpoint catalog with no sequencing and no validation checkpoints for destructive DELETE and batch 'apply' operations, matching the 'rough sequence/gaps; validation absent' anchor; the destructive-operation cap also blocks scoring above 3.	2 / 5
Progressive Disclosure	With no references/scripts/assets bundle present, ~60 endpoints are inlined as a monolithic block that clearly belongs in a separate reference file, matching the 'content that belongs in separate files is inlined' anchor despite per-endpoint headers and the OpenAPI pointer.	2 / 5
	Total	9 / 20 Passed

Description

58%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 states concrete capabilities and is tied to a distinct OmniRoute niche, but it lacks any 'when to use' trigger guidance and relies on fairly technical keywords without natural user synonyms.

Suggestions

Add an explicit 'Use when ...' clause naming the natural triggers (e.g. 'Use when the user asks to list, configure, or invoke OmniRoute CLI tool plugins via the API').

Include common-synonym trigger terms users would actually say (e.g. 'CLI plugins', 'tool settings', 'backups', 'runtime status') to raise trigger-term coverage.

Tighten the second sentence so it reinforces distinctiveness rather than restating 'automation surface' abstractly.

Dimension	Reasoning	Score
Specificity	"List, configure, and invoke CLI tool plugins" names several concrete actions beyond a single verb, fitting the 'lists several specific actions; minor gaps' anchor rather than the 1-2-action anchor 3.	4 / 5
Completeness	The description gives a clear 'what' (manage/list/configure/invoke CLI tool integrations via the API) but omits any 'when/Use when' trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Terms like "CLI tool integrations", "configure", and "invoke" are relevant but there are no natural user-phrase variations or synonyms, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to "OmniRoute's automation surface" and CLI-tool integrations via the API gives it a mostly-distinct niche with only minor overlap risk, just above the broad-anchor 3.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (757 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: diegosouzapw/OmniRoute
Path: skills/omni-cli-tools/SKILL.md
Commit: c3945a7

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.