CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-skill-collector

Detect installed CLI coding tools (Claude Code, Codex, Cursor, Copilot, Cline and more), search GitHub for matching agent skills, and install them to the detected tools via OmniRoute's built-in APIs.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

56%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 curated second half is a genuinely good skill: concrete API commands, a score-based triage table, an explicit verification step, and a full quick-start script. It is undermined by the auto-generated first half — an irrelevant, partially duplicated omniroute CLI manual with at least one truncated sentence — which wastes most of the token budget and buries the actual workflow. Removing or extracting that reference and adding the missing clone/copy commands would make this a strong skill.

Suggestions

Delete the generated 'Subcommands' reference (or move it to a `references/cli-reference.md` linked from a short 'CLI basics' section) — it documents `autostart`, `env`, `setup`, and `update` commands unrelated to skill collection and duplicates `config get`/`set`/`list`, which is the main driver of the low conciseness score.

Fix the broken generated content: the truncated 'Generate OpenCode config (alias for ' sentence and the duplicate `config get`, `config set`, and `config list` sections.

Make the final install step fully executable by showing the actual GitHub clone + `cp SKILL.md` commands the agent must run after the install-planning POST, and add a short error-recovery note for failed API calls or unwritable target directories.

DimensionReasoningScore

Conciseness

Roughly the first 60% of the body is an auto-generated omniroute CLI subcommand reference (`autostart`, `config`, `env`, `setup`, `update`) that is unrelated to the skill's stated purpose, with duplicated sections (`config get`, `config set`, `config list` each documented twice) and a truncated sentence ('Generate OpenCode config (alias for ' — nothing follows). This is noticeably verbose padding beyond the genuinely lean curated workflow section. Not 3 because the irrelevant bulk is far more than 'some unnecessary explanation'; not 1 because the curated half is efficient and free of concept over-explanation.

2 / 5

Actionability

The curated section provides executable curl commands with headers and JSON payloads, a realistic example response, a copy-paste-ready quick-start bash script, and verification `ls` commands — concrete and mostly complete. Not 5 because the actual file sync ('cloning from GitHub and copying SKILL.md... done by the agent using standard `curl` + `cp` commands') is described but never shown as executable commands, leaving the final install step to be improvised.

4 / 5

Workflow Clarity

The curated workflow is clearly sequenced as Step 1 Detect → Step 2 Review (with a score-prioritization table) → Step 3 Install (with target paths) → Step 4 Verify (explicit `ls` checks and re-running detection), so most checkpoints are present. Not 5 because there is no error-recovery feedback loop (e.g., what to do when the API call fails or a target tool is not writable) and no checkpoint between install planning and execution; not 3 because explicit verification does exist.

4 / 5

Progressive Disclosure

The body has section headers and a well-organized curated half, but the ~265-line generated CLI subcommand reference is bulk content that clearly belongs in a separate reference file and is inlined in SKILL.md (with duplicated entries), matching 'content that should be separate is inline'. The only external pointer (`docs/frameworks/SKILLS.md`) is a passing mention rather than a clearly signaled reference. Not 2 because there is real structure and navigation is possible; not 4 because the largest block of content is misplaced rather than having only minor organization gaps.

3 / 5

Total

13

/

20

Passed

Description

71%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 strong, specific description that names concrete actions, tools, and the mechanism (OmniRoute's APIs) in third-person voice without fluff. Its main weakness is the complete absence of any 'when to use this' trigger guidance, which caps completeness and slightly raises conflict risk. Adding a 'Use when...' clause referencing user intents (e.g., wanting to find, add, or install agent skills/plugins for a coding CLI) would lift it substantially.

Suggestions

Append an explicit trigger clause such as 'Use when the user wants to find, add, or install agent skills (plugins) for their coding CLI tools' — this addresses completeness (currently 3, capped by the missing 'when' guidance).

Add natural synonyms to broaden trigger coverage, e.g., 'plugins', 'extensions', or 'SKILL.md repos', which users may say instead of 'agent skills' (addresses trigger_term_quality).

Make the differentiation sharper by stating what OmniRoute specifically enables (e.g., 'no separate collector app needed') to reduce overlap with generic GitHub-search or skill-marketplace skills (addresses distinctiveness_conflict_risk).

DimensionReasoningScore

Specificity

Lists three concrete, specific actions — 'Detect installed CLI coding tools', 'search GitHub for matching agent skills', 'install them to the detected tools via OmniRoute's built-in APIs' — and names concrete tools (Claude Code, Codex, Cursor, Copilot, Cline), comprehensively covering the described workflow. Not 4 because there are no meaningful gaps in coverage of the detect→search→install pipeline it claims.

5 / 5

Completeness

Clearly answers 'what' (detect tools, search GitHub for skills, install them) but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent, not merely under-specified.

3 / 5

Trigger Term Quality

Includes natural, user-sayable terms — the tool names plus 'agent skills', 'GitHub', 'install skills' — which are strong triggers. Not 5 because it omits common variations and synonyms users might say (e.g., 'plugins', 'extensions', 'skill marketplace', 'SKILL.md repos'); not 3 because the keywords present are specific and natural rather than generic.

4 / 5

Distinctiveness Conflict Risk

The OmniRoute API framing and the specific tool list give it a fairly distinct niche ('install them to the detected tools via OmniRoute's built-in APIs'), so it is mostly distinguishable from other skills. Not 5 because generic phrases like 'search GitHub for matching agent skills' could overlap with other skill-discovery or GitHub-search skills, and the missing 'when' guidance leaves some wrong-trigger risk.

4 / 5

Total

16

/

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-skill-collector/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.