CtrlK
BlogDocsLog inGet started
Tessl Logo

cli-anything-drawio

Command-line interface for Drawio - A CLI harness for **Draw.io** — create, edit, and export diagrams from the command line....

51

Quality

55%

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 ./drawio/agent-harness/cli_anything/drawio/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well organized with concrete, runnable commands and useful agent-facing guidance (JSON output, return codes, output verification). However, it repeats example commands across three sections, never demonstrates the core shape/connector syntax, omits an end-to-end workflow with validation, and inlines what is essentially full API reference material.

Suggestions

Add one end-to-end example (project new, shape add, connect add, export render) with explicit validation steps — check the JSON return code and verify the exported file exists — instead of repeating basic commands in three sections.

Show actual syntax for 'shape add' and 'connect add' (arguments, shape types, IDs) since these are the skill's core operations but currently have only one-line descriptions.

Move the full command tables into a references file (e.g. COMMANDS.md) and keep a quick-start in SKILL.md, replacing the vague 'See README.md in the package' pointers with concrete bundle paths.

DimensionReasoningScore

Conciseness

The command tables are lean, but 'Basic Commands', 'Examples', and 'Output Formats' repeat the same invocations (project new, REPL, --json project info) three times, leaving clear tightening opportunities.

3 / 5

Actionability

Commands are concrete and executable (e.g. 'cli-anything-drawio --project myproject.json export render output.pdf --overwrite'), but the core shape and connector operations get only one-line table descriptions with no syntax example showing arguments or shape IDs.

4 / 5

Workflow Clarity

Command groups are listed but no end-to-end sequence (create project, add shapes, connect, export) is shown, and destructive/batch operations (remove, --overwrite) lack validation checkpoints — only the 'For AI Agents' tips ('Check return codes', 'Verify outputs exist') gesture at validation.

3 / 5

Progressive Disclosure

Sections and tables are well organized, but ~150 lines of inline command reference could live in a separate file, and the 'More Information' pointers ('See README.md in the package', 'HARNESS.md in the cli-anything-plugin') reference external, non-linkable paths rather than bundle files.

3 / 5

Total

13

/

20

Passed

Description

53%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 names a clear niche and a few broad capabilities but lacks any 'Use when...' trigger guidance, natural synonyms, and detail on the CLI's actual command coverage. It also shows quality issues — a duplicated prefix, markdown bold, and a trailing ellipsis suggesting truncation.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating or editing Draw.io diagrams, flowcharts, or .drawio files, or exporting diagrams to PNG/PDF/SVG from the command line.'

Remove the redundant 'Command-line interface for Drawio - ' prefix, the markdown bold, and the trailing ellipsis; write a single clean third-person sentence.

Enumerate more concrete capabilities (add/label shapes and connectors, manage pages, undo/redo, JSON output for agents) instead of the generic 'create, edit, and export'.

DimensionReasoningScore

Specificity

Names the Draw.io domain and broad actions ('create, edit, and export diagrams from the command line') but misses the skill's actual coverage such as shapes, connectors, pages, and PNG/PDF/SVG rendering, so it is not comprehensive.

3 / 5

Completeness

The 'what' is clear ('A CLI harness for Draw.io — create, edit, and export diagrams') but there is no 'when' clause at all, which caps completeness at 3; the text is also truncated with '....' and a redundant duplicated prefix.

3 / 5

Trigger Term Quality

Relevant keywords like 'Draw.io', 'diagrams', and 'command line' are present, but natural variations users would say — 'flowchart', '.drawio files', 'diagramming', 'export to PNG' — are missing.

3 / 5

Distinctiveness Conflict Risk

'CLI harness for Draw.io' carves out a clear niche with low overlap risk against other skills, but the thin trigger phrasing keeps it from reliably distinct triggering, so it falls just below the anchor-5 example.

4 / 5

Total

13

/

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