CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

55%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 efficient, well-linked index with genuinely good progressive disclosure into the reference file, but it contains no example requests or payloads and no workflow guidance, leaving destructive operations (DELETE, apply) without any validation steps.

Suggestions

Add a brief workflow section (e.g., GET /detect or GET /status to inspect -> configure settings -> POST /apply -> re-check status to verify), especially since apply and DELETE operations are destructive and currently lack any validation guidance.

Include one or two concrete example requests (e.g., a curl call with the Bearer token and a sample JSON body for POST /api/cli-tools/claude-settings) so the skill is executable without consulting an external spec.

Resolve the dangling reference: either bundle a payloads reference file or point the Payloads section at sections within references/endpoints.md instead of the absent docs/openapi.yaml.

DimensionReasoningScore

Conciseness

The body is a lean index with no explanatory padding and assumes Claude's competence, with only minor redundancy: the Overview sentence duplicates the frontmatter description and the 75-link index partially duplicates the reference file's own table of contents. Not a 5 because those duplications are tokens that could be trimmed or repurposed.

4 / 5

Actionability

Concrete elements exist (specific endpoint paths, auth via Bearer token, POST /api/auth/login, REQUIRE_API_KEY=false), but there are no example requests or responses, and the Payloads section punts entirely to an OpenAPI spec outside the bundle. Not a 4 because key executable details (a sample request/response) are missing from the body.

3 / 5

Workflow Clarity

No workflow sequence is present (nothing like detect -> inspect status -> configure -> apply -> verify), and destructive/batch endpoints (DELETE operations, POST /apply) carry no validation guidance, which the rubric caps at 3 and this content sits below. Not a 1 because a rough implied flow (authenticate, pick an endpoint, consult the payload spec) is discernible.

2 / 5

Progressive Disclosure

SKILL.md serves as an index with precise, one-level-deep anchor links into references/endpoints.md whose headers all resolve, enabling selective loading instead of the 825-line file. Not a 5 because the overview adds little beyond the description and the Payloads section references docs/openapi.yaml, which is not present in the bundle.

4 / 5

Total

13

/

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 clearly states what the skill does with several concrete verbs, but it entirely lacks "when to use it" guidance, capping completeness at 3. Trigger keyword coverage is adequate but misses natural variations and specific tool names.

Suggestions

Add an explicit trigger clause, e.g., "Use when managing CLI tool integrations, checking tool statuses, or applying tool configuration changes via the OmniRoute API."

Include natural keyword variations users would say, such as "command-line tools" or the specific managed tools (claude, codex, cline, etc.), to improve trigger term coverage.

Trim the jargon phrase "extend OmniRoute's automation surface" in favor of concrete capability detail (e.g., what invoking a tool plugin does).

DimensionReasoningScore

Specificity

"List, configure, and invoke CLI tool plugins" lists several concrete actions on a named object, matching the score-4 anchor's pattern. It is not a 5 because coverage is not comprehensive (no indication of what invoking does or which tools are covered), and not a 3 because more than 1-2 concrete actions are named.

4 / 5

Completeness

The "what" is clear ("List, configure, and invoke CLI tool plugins") but there is no "Use when..." clause or equivalent trigger guidance, which the rubric caps at 3. Not a 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant keywords exist ("CLI tool", "configure", "API", "plugins") but common variations users would naturally say are missing (e.g., "command-line tools", "tool settings", specific tool names like claude/codex). Not a 4 because keyword coverage has clear gaps; not a 2 because several genuinely relevant domain terms are present.

3 / 5

Distinctiveness Conflict Risk

The product-specific "OmniRoute" scope and the specific CLI-tool-integration domain give it a mostly distinct niche with only minor overlap risk against other API-management skills. Not a 5 because the generic "Manage ... integrations" framing could collide with sibling omni-* API skills.

4 / 5

Total

14

/

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

Reviewed

Table of Contents

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.