cli-anything-eez-studio

Use EEZ Studio from the command line: inspect and modify native .eez-project files, edit LVGL screens/widgets, manage SCPI commands, and invoke the real EEZ Studio backend for LVGL builds.

Quality

81%

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

Quality

Content

87%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.

An exceptionally concise and fully executable reference for the CLI: every section is a runnable command block with no filler. The gap is operational safety — mutating commands auto-save and simulator builds depend on a backend, yet no validation or dry-run-first checkpoint is prescribed in the workflow.

Suggestions

Add a validation checkpoint before mutations, e.g., "run `cli-anything-eez-studio --json backend status` first; if the backend is missing, run the Install steps before backend commands."

Recommend `--dry-run` as the default first pass for project-mutating commands, followed by inspecting the reported diff and re-running without `--dry-run` only when the change looks right.

Show how to verify a simulator build succeeded (e.g., check `build/sim` output or the JSON result field) before treating the build as complete.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-first — "Always use `--json` for agent-readable output" followed by short, labeled command blocks — with no concept explanations, no padding, and every line earning its place.	5 / 5
Actionability	Every section gives copy-paste-ready commands with concrete flags and arguments ("project new -o panel.eez-project --name Panel", "scpi parameter-add ... --type nr1 --optional"), covering the common cases for projects, LVGL widgets, SCPI, backend builds, and session state.	5 / 5
Workflow Clarity	Sections imply a rough order (install, backend source setup, usage, build), but there are no validation checkpoints anywhere, and one-shot commands "auto-save project mutations unless `--dry-run` is provided" — destructive project writes without a verify step, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed; the body is a short, single-purpose CLI skill organized into well-labeled sections (Install, Core Usage, SCPI Commands, Backend Commands, State) that satisfies the simple-skill exception for progressive disclosure.	5 / 5
	Total	18 / 20 Passed

Description

75%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 highly specific, distinct, third-person description that concretely enumerates the CLI's capabilities. Its main weakness is the absence of any explicit "Use when..." trigger clause, which both limits completeness and leaves natural-language trigger coverage thinner than it could be.

Suggestions

Append an explicit trigger clause, e.g., "Use when automating EEZ Studio projects, building LVGL UIs, or managing SCPI command definitions."

Add natural synonyms or file extensions (".eez", "instrument control", "GUI screens") so users phrasing requests differently still match the description.

Consider mentioning the LVGL simulator-build outcome explicitly as a trigger phrase (e.g., "use when you need to build the LVGL simulator") since that is a distinctive capability.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "inspect and modify native .eez-project files, edit LVGL screens/widgets, manage SCPI commands, and invoke the real EEZ Studio backend" — providing comprehensive coverage of the CLI's capabilities rather than generic domain language.	5 / 5
Completeness	The "what" is clearly and concretely stated, but the description contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness per the rubric guidelines.	3 / 5
Trigger Term Quality	Strong domain terms users of this tool would naturally say ("EEZ Studio", ".eez-project", "LVGL", "SCPI", "command line"), but there is no synonym variation or related phrasing (e.g., "GUI", "front panel", "instrument", ".eez") that would broaden natural trigger coverage.	4 / 5
Distinctiveness Conflict Risk	"EEZ Studio", ".eez-project", "LVGL", and "SCPI" name a clear niche with distinct triggers; virtually no other skill would match these terms, so conflict risk is minimal.	5 / 5
	Total	17 / 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: eez-studio/agent-harness/cli_anything/eez_studio/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.