CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-inkscape

Command-line interface for Inkscape - A stateful command-line interface for vector graphics editing, following the same patterns as the GI...

Quality

65%

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

Quality

Content

65%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 an efficient, well-organized command reference with executable examples and useful agent-oriented output guidance, but it functions as an inlined API catalog rather than a workflow guide: no explicit end-to-end sequence or validate→fix→retry loop for SVG/XML manipulation, and no progressive-disclosure layer despite its length.

Suggestions

Add an explicit end-to-end workflow section (create project → add/edit content → validate → export) with a feedback loop, e.g. run 'document info'/'shape list' after edits and re-check output files after export failures.

Move the ten command-group tables into a references/COMMANDS.md file, keeping only a quick-start and representative examples in SKILL.md.

Show argument syntax for the remaining command groups (transforms, gradients, path booleans, layers) at least once each, since only the document/text commands have full flag-level examples.

DimensionReasoningScore

Conciseness

The body is dominated by terse command tables and flag-level examples with no explanation of concepts Claude already knows. Minor trims exist: the REPL example and the 'document new' example each appear twice (Usage and Examples sections), and the 'More Information'/'Version' pointers add little. This fits 'efficient; minor instances that could be trimmed' rather than 'every token earns its place' because of that duplication.

4 / 5

Actionability

Commands are concrete and copy-paste ready for the shown cases (pip install, 'document new -o project.json', 'export pdf output.pdf --overwrite', full wrapped-text invocation with all flags). It falls short of 'fully executable... specific examples cover the common cases' because argument syntax for many table-listed commands ('rotate', 'gradient add-linear', 'layer reorder', 'path union') is never shown, leaving minor gaps.

4 / 5

Workflow Clarity

As a command catalog, the create→edit→export sequence is only implicit in scattered examples, and validation exists only as agent tips ('Check return codes', 'Verify outputs exist after export operations') with no explicit validate→fix→retry feedback loop despite this being XML/SVG document manipulation. This matches 'steps listed but validation gaps; checkpoints missing or implicit' rather than 4, where a clear sequenced workflow with most checkpoints would be present.

3 / 5

Progressive Disclosure

The body is well-sectioned with headers and tables, but roughly 100 lines of full command-group API reference are inlined in SKILL.md rather than split into a reference file — matching the anchor example of '[200 lines of API reference that could be in a separate file]'. It is not 4 because there are no one-level-deep bundle reference files at all (references/, scripts/, assets/ are absent), and pointers go to files outside the skill ('See README.md in the package').

3 / 5

Total

14

/

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 has a clear, third-person 'what' anchored to a specific tool, but it is literally truncated mid-word ('...as the GI...'), provides no 'when to use' guidance, and lists no concrete operations beyond generic 'vector graphics editing'. Trigger terms cover Inkscape and vector graphics but omit SVG and file extensions.

Suggestions

Complete the truncated sentence and replace the redundant restatement with 2-3 concrete actions (e.g., 'Create and edit SVG shapes, text, layers, and gradients; export to PNG, PDF, and SVG').

Add an explicit trigger clause: 'Use when working with Inkscape, SVG files, or vector graphics creation/editing tasks.'

Include natural keyword variations such as 'SVG', '.svg', 'drawing', and 'vector illustration' for stronger trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Inkscape', 'vector graphics editing') but the only action stated is generic 'editing', restated redundantly ('Command-line interface for Inkscape - A stateful command-line interface for vector graphics editing'). It matches the anchor 'names the domain but actions are minimal or generic' — no concrete operations (shapes, gradients, export) are stated, and the sentence truncates mid-word ('following the same patterns as the GI...') before any specifics could follow.

2 / 5

Completeness

There is a clear 'what' ('A stateful command-line interface for vector graphics editing') but absolutely no 'when' — no 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 3 per the rubric guidelines. It is not a 2 because the 'what' is stated clearly, not vaguely.

3 / 5

Trigger Term Quality

'Inkscape', 'vector graphics', and 'command-line' are natural terms a user would say, but common variations and synonyms are missing: no 'SVG', '.svg', 'drawing', or 'shapes'. This fits 'some relevant keywords but missing common variations or synonyms' rather than 'good keyword coverage' because a core format term users say (SVG) is absent.

3 / 5

Distinctiveness Conflict Risk

'Command-line interface for Inkscape' carves a clear niche distinct from sibling GIMP/Blender CLI harnesses it references, with only minor overlap risk from the generic 'vector graphics editing' phrase and the (truncated) mention of related harnesses. Fits 'mostly distinct; minor overlap risk with closely related skills'.

4 / 5

Total

12

/

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

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