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

48%

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

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 a well-structured but monolithic API dump: executable for reads, incomplete for writes, with no workflow/validation guidance around destructive operations and no progressive disclosure to offload the bulk reference.

Suggestions

Move the full endpoint catalog into a separate reference file (e.g., references/endpoints.md) and keep SKILL.md as a concise overview with a one-level-deep pointer, lifting progressive_disclosure.

Replace the empty `-d '{}'` bodies on POST/PUT examples with at least one representative real payload per operation, or explicitly label the required fields inline.

Add validation/verification guidance for the destructive DELETE/reset endpoints (e.g., confirm the target toolId, verify the resulting state) so workflow_clarity can exceed the destructive-operation cap.

Dimension	Reasoning	Score
Conciseness	Per-endpoint text is terse and free of concept over-explanation, but the same Authorization header is repeated across ~30 curl blocks and every POST/PUT ships an empty `-d '{}'` body, so the whole could be tightened substantially by stating auth once and consolidating.	3 / 5
Actionability	GET examples are copy-paste executable, but the write operations all use `-d '{}'` with no real request body and defer all payload detail to the external OpenAPI spec, leaving the common write cases incomplete.	3 / 5
Workflow Clarity	This is a flat endpoint catalog with no multi-step sequence, and the destructive DELETE operations (e.g., 'Delete Codex profile', 'Remove OmniRoute from config') carry no validation or verification guidance.	2 / 5
Progressive Disclosure	Section headers exist and endpoints are organized, but ~390 lines of API reference are inlined directly in SKILL.md — content that clearly belongs in a separate reference file — with only a passing pointer to the external OpenAPI spec.	3 / 5
	Total	11 / 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 conveys a clear what and a distinct niche, but it stops short of explicit trigger guidance and relies on generic verbs, so it lands around the midpoint of the scale.

Suggestions

Add an explicit 'Use when...' clause naming the trigger phrases (e.g., 'Use when managing or configuring OmniRoute CLI tool integrations such as Claude, Cline, or Codex settings').

Replace generic verbs with more concrete capabilities that reflect the actual surface (e.g., 'back up, configure MITM proxies, and apply per-tool settings').

Trim the fluff phrase 'that extend OmniRoute's automation surface' since it adds no actionable specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('CLI tool integrations exposed via the API') and lists three actions ('List, configure, and invoke'), but the verbs are generic and 'extend OmniRoute's automation surface' adds no concrete capability, leaving coverage well short of the actual endpoints (backups, MITM, per-tool settings).	3 / 5
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	'CLI tool integrations', 'CLI tool plugins', and 'API' are natural terms a user might say, but common variations and the specific tool names (Claude, Cline, Codex, etc.) that users would actually mention are missing.	3 / 5
Distinctiveness Conflict Risk	The OmniRoute-specific framing ('OmniRoute's automation surface', 'CLI tool integrations via the API') gives it a clear niche with only minor overlap risk against generic API or tooling skills.	4 / 5
	Total	13 / 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/omni-cli-tools/SKILL.md
Commit: ea0cdc5

Reviewed: about 6 hours 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.