CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-macrocli

Use when the agent wants to define, list, inspect, or execute GUI macros via the MacroCLI CLI. Macros are parameterized, CLI-callable workflows — the agent invokes `macro run <name>` and the system handles backend routing (plugin, file transform, accessibility, compiled GUI replay).

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./macrocli/agent-harness/cli_anything/macrocli/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable content: executable CLI commands, a defined JSON output contract, a complete macro schema, and a dry-run-first workflow. The main cost is token redundancy — the duplicated Quick Start/Example Workflow sections and the restated concept section could be cut — and the ~40-line schema could move to a reference file.

Suggestions

Merge 'Quick Start' and 'Example Workflow' into one section — they demonstrate the identical list → info → dry-run → run sequence and cost ~18 redundant lines.

Drop or shrink 'What It Is'; it repeats the frontmatter description, and the one non-duplicated fact ('agents never touch the GUI directly') can open the Quick Start.

Move the full macro YAML schema (~40 lines) to a references/ file (e.g. references/macro-schema.md), keeping only the scaffold command and a pointer in SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly lean command tables and code, but 'Quick Start' and 'Example Workflow' are near-duplicate demonstrations of the same list → info → dry-run → run sequence (~18 redundant lines), and 'What It Is' restates the frontmatter description. This is more than 'minor instances of over-explanation', so it sits at 'mostly efficient but could be tightened'.

3 / 5

Actionability

Every section gives copy-paste-ready commands ('cli-anything-macrocli macro run export_file --param output=/tmp/result.txt --json'), a fully specified JSON output shape, and a complete minimal macro YAML schema with params, preconditions, postconditions, and agent_hints — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

The Example Workflow sequences discovery → inspect → dry-run validation → execution ('Step 3: Test safely', 'Step 4: Execute for real'), and failure handling is addressed ('Read error field when success is false'). It falls short of a 5 because there is no explicit fix-and-retry feedback loop after a failed run.

4 / 5

Progressive Disclosure

A single-file skill (no bundle files exist) with clear, navigable sections (Command Reference, Parameters, Output Format, Backends, Writing Macros, Usage Rules) and nothing buried or nested. Not a 5: at ~210 lines, the full macro YAML schema and complete command tables are inlined where a references/ file could carry them; not a 3 since the structure is well-organized and easy to navigate.

4 / 5

Total

16

/

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 description with an explicit and specific trigger clause and a distinct niche. Its main weaknesses are jargon-heavy trigger terms missing natural synonyms, and a 'what' statement that describes the mechanism rather than the concrete capability.

Suggestions

Add natural trigger synonyms users would actually say, e.g. 'Use when the user wants to automate repetitive GUI tasks, record or replay GUI actions, or run GUI workflows from the command line.'

State the concrete capability in the 'what' portion: converting valuable GUI workflows into parameterized CLI calls so agents never touch the GUI directly.

Trim internal jargon ('backend routing (plugin, file transform, accessibility, compiled GUI replay)') — it belongs in the body, not the description.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("define, list, inspect, or execute GUI macros") plus the concrete invocation form "macro run <name>", but omits parts of the surface (session commands, validate), matching the 'several specific actions; minor gaps' anchor rather than comprehensive coverage.

4 / 5

Completeness

It has an explicit 'Use when the agent wants to define, list, inspect, or execute GUI macros' clause and a what-statement ("Macros are parameterized, CLI-callable workflows... system handles backend routing"), but the 'what' describes mechanism rather than the concrete capability (converting GUI workflows into CLI calls without touching the GUI), which only appears in the body.

4 / 5

Trigger Term Quality

"GUI macros" and "MacroCLI" are relevant keywords, but the description leans on technical jargon ("backend routing", "compiled GUI replay", "accessibility") and misses natural synonyms like "GUI automation", "automate", or "macro replay", fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

"GUI macros via the MacroCLI CLI" carves out a clear niche with distinct triggers ("macro run <name>", MacroCLI) and minimal overlap risk with any other plausible skill.

5 / 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

HKUDS/CLI-Anything

Path

macrocli/agent-harness/cli_anything/macrocli/skills/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.