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

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

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 a serviceable command reference with concrete executable examples, but it lacks workflows with validation for destructive config/env operations, has a truncated 'config opencode' description, and deduplicates content poorly. Splitting detail into a reference file and adding verification steps would improve it.

Suggestions

Add explicit validation/verification steps for destructive or batch operations such as 'config set' and 'env set' (e.g. run 'config validate <tool>' after writing).

Fix the truncated 'config opencode' description ('Generate OpenCode config (alias for') and remove the duplicate 'config get'/'config list'/'config set <code>' sections that collide with earlier ones.

Consolidate repetitive 'Example:' blocks and move verbose flag tables into a references/ file, linking from SKILL.md for better progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command listings, but it repeats the full description verbatim in the Overview and pads many subcommand sections with near-empty 'Example:' blocks containing the bare command; this could be tightened further.	3 / 5
Actionability	Commands and flags are concrete and copy-pasteable (e.g. 'omniroute config set <tool>' with --model/--non-interactive flags), giving mostly executable guidance with minor gaps such as the truncated 'config opencode' alias line.	4 / 5
Workflow Clarity	The skill lists subcommands but exposes no multi-step workflow or validation checkpoints for risky/batch operations like 'config set' or 'env set', and the destructive-or-batch cap holds this at 3 per the rubric feedback-loop guidance.	3 / 5
Progressive Disclosure	Structure is reasonable with one section per subcommand, but there are no external reference files (references/ absent) and inline content like full flag tables that could live in a separate reference; references are not signaled and some content is duplicated across sections.	3 / 5
	Total	13 / 20 Passed

Description

57%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 is concrete and tool-specific, listing several real capabilities, but lacks an explicit trigger clause telling Claude when to invoke the skill. Adding a 'Use when...' phrase would lift completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when setting up or configuring the omniroute CLI, managing its environment variables, or checking for updates.'

Add natural user phrasings/synonyms like 'configure the CLI' or 'set environment variables' to broaden trigger coverage.

Clarify scope ownership relative to other omniroute skills to reduce any overlap ambiguity.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Run initial setup, configure global CLI settings, manage environment variables, check for updates, and configure autostart'), with only minor gaps such as omitted per-subcommand detail; matches the anchor listing several specific actions with minor coverage gaps.	4 / 5
Completeness	The description clearly answers 'what' the skill does but provides no explicit 'Use when...' or equivalent trigger clause stating when Claude should use it, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes relevant keywords like 'setup', 'config', 'environment variables', 'autostart', and 'update' that a user might say, but misses common natural phrasings and synonyms (e.g. 'configure the CLI', 'set env var'); some relevant keywords with variations missing.	3 / 5
Distinctiveness Conflict Risk	The focus on 'omniroute CLI setup and config commands' gives it a reasonably distinct niche tied to a specific tool, with only minor overlap risk against generic config-management skills.	4 / 5
	Total	14 / 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/cli-setup/SKILL.md
Commit: 6435f61

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