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

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Risky

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

50%

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 lean, mostly-executable CLI command reference, but it is undermined by duplicate subcommand entries, a truncated description, missing descriptions, and a lack of validation guidance for destructive operations like update --apply. It is a flat single-file reference with no progressive disclosure.

Suggestions

Deduplicate the repeated subcommands (config list, config get, config set) and merge their flag sets into single authoritative entries.

Complete the truncated "config opencode" description and add missing one-line descriptions for subcommands that currently have none (autostart, config, config opencode, config lang, setup, update).

Add brief validation/verification guidance for destructive operations, e.g. run "omniroute update --check" or "--dry-run" before "--apply", and "config validate <tool>" before "config set".

Dimension	Reasoning	Score
Conciseness	The style is lean with no concept over-explanation, but it wastes tokens on duplicate entries ("config list" appears twice, "config get" twice, "config set <tool>" vs "config set <code>") and several empty-description subcommands; it is not a 3 because of this redundancy and not a 1 because no padding of known concepts.	2 / 3
Actionability	Concrete executable commands and flag lists are provided per subcommand, but guidance is incomplete: the "config opencode" description is truncated mid-sentence ("Generate OpenCode config (alias for"), descriptions are missing for several subcommands, and duplicate entries give inconsistent flag sets; not a 1 because real commands are present, not a 3 because of the gaps.	2 / 3
Workflow Clarity	This is a command reference rather than a multi-step workflow, but destructive/batch operations like "update --apply" and "--no-backup" and the config-writing "config set" lack any validation or verification guidance, capping workflow clarity at 2 per the guidelines; it is not a 1 because commands are individually clear.	2 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the body is a single ~265-line monolithic listing with no external references or "see X.md" navigation; sections are organized per subcommand, but content that could be split (full flag references for setup/update) is all inline, so it is not a 3 and not a 1 because organization is present.	2 / 3
	Total	8 / 12 Passed

Description

82%

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 action-oriented with natural trigger terms and a clear CLI-config niche, but it omits an explicit "Use when..." trigger clause, which caps its completeness. Adding a usage-trigger sentence would raise the completeness and overall score.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user needs to set up or configure the CLI, manage environment variables, enable autostart, or check for updates."

Consider adding common phrasing variations (e.g. "env vars", "update check") to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — "Run initial setup, configure global CLI settings, manage environment variables, check for updates, and configure autostart" — matching the anchor for several named concrete actions rather than vague language.	3 / 3
Completeness	It clearly answers "what" (setup, config, env vars, updates, autostart) but has no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the guidelines; it is not a 1 because the what-side is concrete.	2 / 3
Trigger Term Quality	Covers natural terms a user would say ("initial setup", "configure CLI settings", "environment variables", "check for updates", "autostart"), giving good coverage of likely trigger phrasing; not merely technical jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped to "the CLI setup and config commands" with distinct triggers (autostart, env management, update checks), carving a clear niche unlikely to fire for unrelated skills; it is not a 2 because the framing is tool-specific rather than generic.	3 / 3
	Total	11 / 12 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-setup/SKILL.md
Commit: 3070925

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