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

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The curated workflow is highly actionable and well-sequenced with verification, but the file is bloated by an auto-generated, partly-broken CLI reference that mixes unrelated subcommands inline with no progressive disclosure into separate files. Splitting the reference out and de-duplicating entries would meaningfully improve token efficiency.

Suggestions

Move the auto-generated CLI command reference into a separate references/ file (e.g. CLI_REFERENCE.md) and keep SKILL.md focused on the detect/search/install workflow, fixing the broken 'config opencode' description and removing duplicated config get/config list entries.

Trim subcommands not relevant to skill collection (autostart, env, setup, update) from the skill body or relocate them so the skill stays on-purpose.

Add a brief navigational pointer at the top (e.g. 'For full CLI command reference, see CLI_REFERENCE.md') so progressive disclosure is explicit and one level deep.

Dimension	Reasoning	Score
Conciseness	The curated workflow section is lean and useful, but the generated CLI reference is padded with redundant/duplicated entries (config get and config list appear twice) and a broken 'config opencode' description, plus many subcommands unrelated to skill collection, so it could be tightened considerably.	2 / 3
Actionability	Provides fully executable, copy-paste-ready curl commands with concrete example JSON responses, install target paths, verification ls commands, and a complete end-to-end quick-start bash script.	3 / 3
Workflow Clarity	The curated section sequences the process clearly as Detect → Review → Install → Verify, with an explicit Step 4 verification checkpoint and re-detection feedback loop covering the batch install operation.	3 / 3
Progressive Disclosure	Content is organized into sections but everything is inline in one ~420-line file with no bundle files; the long CLI command reference is content that could be split into a separate reference file rather than inline.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 distinct, naming concrete actions and tools, but it reads as a capability list rather than trigger-oriented guidance and lacks an explicit 'Use when' clause. Adding trigger phrasing would raise completeness and trigger_term_quality.

Suggestions

Append a 'Use when...' clause with natural user triggers, e.g. 'Use when the user wants to find, search, or install agent skills for their coding CLI tools (Claude Code, Codex, Cursor, etc.).'

Reframe capability verbs as natural user phrasing ('find and install agent skills') to improve trigger-term quality beyond the feature-list style.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions in third person — 'Detect installed CLI coding tools', 'search GitHub for matching agent skills', and 'install them to the detected tools' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Clearly answers 'what' (detect, search, install) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant natural terms ('agent skills', 'GitHub', 'coding tools', 'install') and names specific tools (Claude Code, Codex, Cursor, Copilot, Cline), but is framed as a feature list rather than user-facing triggers and misses common variations a user would actually say.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche — detecting coding CLIs and installing matching GitHub agent skills via OmniRoute's APIs — with specific tool names, making it unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 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-skill-collector/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.