CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-setup

Run initial setup, configure global CLI settings, manage environment variables, check for updates, and configure autostart via the CLI setup and config commands.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

65%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.

A terse, executable CLI command reference with concrete examples for every subcommand, weakened by duplicated config sections, a truncated description, absent flag semantics, and no workflow sequencing or validation guidance for multi-step operations like setup and config set. Organization is adequate but the entire reference is inlined with no progressive disclosure structure.

Suggestions

Deduplicate the repeated 'config get'/'config set'/'config list' sections and complete the truncated 'config opencode' description ('Generate OpenCode config (alias for' ends mid-sentence).

Add a short usage workflow that sequences the commands (e.g., 'omniroute setup' -> 'config list' -> 'config get <tool>' -> 'config set <tool> --model <model>' -> 'config validate <tool>') with a validation checkpoint before writing config.

Show at least one flag in action per complex subcommand (e.g., 'omniroute setup --add-provider --provider <id> --api-key <value>') and briefly annotate what key flags like '--tray' or '--allow-container-write' do.

DimensionReasoningScore

Conciseness

The body is a lean flag/example catalog with no concept explanations or padding, but the Overview repeats the description verbatim, the 'config get'/'config set'/'config list' subcommands each appear twice with conflicting flags, and 'config opencode' has a truncated description ('Generate OpenCode config (alias for'), all of which waste tokens.

4 / 5

Actionability

Every subcommand has a copy-paste-ready example command and a flag list, meeting the 'mostly executable' anchor. It falls short of 5 because flags lack descriptions, no example demonstrates flag usage (e.g., 'setup' shows a bare 'omniroute setup' despite ten flags), and placeholder values like '<tool>' are never instantiated.

4 / 5

Workflow Clarity

The content is a flat command catalog with no sequenced guidance for multi-step tasks (e.g., config list -> config get <tool> -> config set -> config validate), and validation exists only as an isolated command rather than a checkpoint. This is not a single-action simple skill, so the simple-skill exception does not apply.

3 / 5

Progressive Disclosure

Per-subcommand headers and a Quick install section give reasonable structure, but a ~280-line full command reference is inlined in SKILL.md with no bundle files, and duplicated config sections signal weak organization — matching 'some structure but could be better organized'.

3 / 5

Total

14

/

20

Passed

Description

62%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.

A solid auto-generated description that enumerates five concrete capabilities in third person with good natural trigger terms. Its main weaknesses are the complete absence of 'when to use this' guidance and the failure to name the specific CLI tool, which limits both completeness and distinctiveness.

Suggestions

Add an explicit trigger clause, e.g., 'Use when performing initial omniroute setup, changing CLI tool configuration, managing environment variables, or enabling autostart.'

Name the tool (omniroute) in the description to distinguish it from other CLI setup/config skills and reduce conflict risk.

Include common synonyms users might type, such as 'env vars' or 'config', to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Run initial setup, configure global CLI settings, manage environment variables, check for updates, and configure autostart'), matching the anchor for several specific actions with minor gaps. It is not 5 because the actions remain generic — no concrete operations, tools, or outcomes are named.

4 / 5

Completeness

It clearly answers 'what' (setup, config, env vars, updates, autostart) but has no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is specific and multi-part, not vague.

3 / 5

Trigger Term Quality

Contains multiple natural phrases users would say ('initial setup', 'environment variables', 'autostart', 'check for updates') with only a few natural terms missing, matching the 'good keyword coverage' anchor. It falls short of 5 because no synonyms or variations ('env vars', 'config', tool-specific names) are included.

4 / 5

Distinctiveness Conflict Risk

Scoping to 'the CLI setup and config commands' gives some specificity, but the tool is never named and the actions (setup, config, env vars, updates) overlap with virtually any CLI configuration skill. This matches 'somewhat specific but could still overlap with similar skills'.

3 / 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/cli-setup/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.