CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-live2d

Inspect, validate, edit, lint, diff, batch-manage, and deploy Live2D Cubism models (.model3.json) from the command line.

Quality

80%

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

Quality

Content

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

A lean, highly actionable command reference with excellent token efficiency, weakened by the absence of any operational workflow guidance for its destructive and batch commands and by the total lack of bundle files to carry per-command detail.

Suggestions

Add a short safe-editing workflow with an explicit validation checkpoint, e.g. '1. backup is automatic on edit; 2. after any edit run `validate <model>`; 3. on failure run `undo <model>`' — this would lift workflow_clarity past the destructive/batch cap of 3.

Show '--dry-run' for every destructive or batch example (batch, flatten, find-replace, migrate, pack), not just the batch one.

Add a references file (e.g. COMMANDS.md) documenting flags and options for all 42 commands, keeping only the command tables inline in SKILL.md.

DimensionReasoningScore

Conciseness

The body is a lean command catalog: one line per command in dense tables, zero explanation of concepts Claude already knows, and the two trailing usage notes ('All read commands support --json. Edit commands auto-backup.') are load-bearing. This matches anchor 5 — every token earns its place.

5 / 5

Actionability

Each command row pairs a concrete invocation with its purpose, and the Examples section gives ten copy-paste-ready commands with realistic flags ('--target web-sdk', '--dry-run', '--embed', '--fade-in 0.3'), matching anchor 5's 'fully executable; copy-paste ready; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The skill exposes destructive and batch operations (edit commands, find-replace, batch, flatten, migrate, pack) but documents no edit-then-validate feedback loop or recovery sequence — the missing-validation cap for destructive/batch operations applies. Mitigating signals exist ('--dry-run' in a batch example, the undo command, the auto-backup note), which places it at anchor 3 rather than 2, but it cannot exceed 3 without an explicit validate/verify checkpoint.

3 / 5

Progressive Disclosure

Sections are well organized (Read/Edit/Generation/Analysis/Workflow/Other command groups plus Examples) and nothing inlined belongs in a separate file, but at ~100 lines with no bundle files at all, per-command flag/option documentation exists nowhere — the examples reveal flags for only 10 of 42 commands. This matches anchor 4 ('good structure; most content appropriately placed; minor organization gaps') rather than anchor 5's fully split, reference-backed structure.

4 / 5

Total

17

/

20

Passed

Description

70%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 specific, well-scoped description with a clear 'what' and strong distinctiveness, undermined only by the complete absence of a 'when to use' trigger clause and by keyword coverage that omits common domain phrasings like motions, expressions, or VTuber avatars.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with Live2D Cubism models, .model3.json files, or when the user mentions Live2D, VTuber avatars, motions, expressions, or model textures.'

Expand bare verbs with their objects to reach anchor-5 specificity, e.g. 'edit motion fade times and expressions, lint for best practices, diff model versions, package models for deployment'.

Include common domain synonyms and related file extensions (.motion3.json, .exp3.json, .cdi3.json) to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists seven concrete action verbs ('inspect, validate, edit, lint, diff, batch-manage, and deploy') plus the domain and file extension, but each is a bare verb without objects (e.g. 'edit' does not say what can be edited), matching anchor 4's 'several specific actions; minor gaps' rather than anchor 5's fully elaborated action list.

4 / 5

Completeness

The 'what' is clear and concrete (inspect/validate/edit/lint/diff/batch-manage/deploy Live2D Cubism models from the command line), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' half is specific and complete.

3 / 5

Trigger Term Quality

Good natural keywords — 'Live2D Cubism models', '.model3.json', 'command line' — that a user in this domain would actually say, but common variations and synonyms (motions, expressions, textures, physics, VTuber, avatar) are missing, matching anchor 4 rather than anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

'Live2D Cubism models (.model3.json)' is a clearly distinct niche with no meaningful overlap with other skills' triggers; the score-4 anchor (minor overlap with closely related skills) does not apply here.

5 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

HKUDS/CLI-Anything

Path

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