cli-anything-ccswitch

CLI interface for CC Switch — manage AI coding tool configurations from the terminal

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./cc-switch/agent-harness/cli_anything/ccswitch/skills/SKILL.md

Quality

Content

80%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 lean, highly actionable CLI command reference with excellent progressive disclosure through clear sectioning. Its main gap is the absence of validation/verification steps for the write operations that modify the database, which caps workflow clarity.

Suggestions

Add a verification step after write operations, e.g. 'After `providers set-current`, run `providers get <id>` or `--json providers list` to confirm the active provider changed.'

Trim the opening framing ('Built with Click and the CLI-Anything methodology') which adds no actionable value for Claude.

Consider adding a brief validate→fix→retry note for `mcp enable` and `settings set` since these mutate the live database.

Dimension	Reasoning	Score
Conciseness	The body is efficient — mostly a command-group table and copy-paste examples — with only minor trimmable framing such as 'Built with Click and the CLI-Anything methodology'; this fits the 'efficient; minor instances of over-explanation' anchor rather than a fully lean 5.	4 / 5
Actionability	Every example is a concrete, copy-paste-ready command with real flags covering all command groups (providers, proxy, mcp, skills, usage, settings, sessions, status), matching the 'fully executable; copy-paste ready; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	It is a well-organized command catalog, but write operations that 'modify the database directly' (providers set-current, proxy config, mcp enable, settings set) lack any validate/verify feedback loop, and the rubric caps workflow_clarity at 3 for destructive or database operations missing validation.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed for a single-file CLI reference; the content is well-organized into clear sections (Prerequisites, Command Groups, Examples, etc.), so the simple-skill exception allows a 5 for well-organized sections without external references.	5 / 5
	Total	17 / 20 Passed

Description

48%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 clearly identifies the niche (CC Switch CLI) and what it does, but relies on a single generic verb and omits any explicit 'Use when…' trigger guidance, which caps completeness and weakens trigger-term quality. Adding concrete actions and natural trigger phrases would lift specificity and completeness.

Suggestions

Replace the generic verb 'manage' with concrete actions, e.g. 'list, switch, and configure AI coding tool providers (Claude Code, Codex, Gemini CLI)'.

Add an explicit 'Use when…' clause with natural trigger phrases, e.g. 'Use when the user wants to switch or inspect AI coding tool configs from the terminal'.

Include synonyms and the app name as triggers (e.g. 'CC Switch', 'cc-switch', 'provider config') to improve distinctiveness and trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('AI coding tool configurations') but offers only the single generic verb 'manage', matching the anchor 'Names the domain but actions are minimal or generic'; it does not list concrete actions like 'list', 'switch', or 'enable' that would warrant a 3.	2 / 5
Completeness	It clearly states what the skill does but provides no 'when' trigger guidance, and the rubric caps completeness at 3 when an explicit 'Use when…' clause is missing; it cannot reach 4 without both what and when.	3 / 5
Trigger Term Quality	Relevant keywords are present ('CC Switch', 'AI coding tool', 'configurations', 'terminal', 'CLI') but there are no natural 'Use when…' phrases, synonyms, or variations a user would naturally say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app 'CC Switch' gives a clear niche with minimal conflict risk, but the absence of explicit trigger phrases leaves minor overlap with other config-management skills, fitting the 'mostly distinct; minor overlap risk' anchor rather than a 5.	4 / 5
	Total	12 / 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: HKUDS/CLI-Anything
Path: cc-switch/agent-harness/cli_anything/ccswitch/skills/SKILL.md
Commit: 34f5195

Reviewed: 1 day 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.