cli-anything-blender

Command-line interface for Blender - A stateful command-line interface for 3D scene editing, following the same patterns as the GIMP CLI ...

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./blender/agent-harness/cli_anything/blender/skills/SKILL.md

Quality

Content

71%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 highly actionable with executable CLI examples and clear agent-oriented workflow guidance, including verification steps. It is moderately concise and relies on a single monolithic file with external pointers rather than in-bundle progressive disclosure.

Suggestions

Move the per-command-group reference tables into a bundle reference file (e.g. references/commands.md) and keep SKILL.md as a concise overview with a clearly signaled pointer, to improve progressive disclosure.

Remove the duplicated 'Examples' section or fold it into 'Usage' to tighten conciseness.

Replace or supplement the external 'See README.md/TEST.md/HARNESS.md in the package' pointers with in-bundle references so navigation stays one level deep.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command tables and code blocks, but the 'Examples' section duplicates 'Usage' (e.g. `scene new`, REPL) and the 'State Management'/'Version' sections add minor padding that could be trimmed.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (`cli-anything-blender --json --project ... preview capture --recipe quick`) and concrete numbered agent guidance covering common cases.	5 / 5
Workflow Clarity	The Preview Workflow shows a clear sequence (recipes → capture → live start → live status) with checkpoints present ('Check return codes', 'Use preview capture for visual verification'), leaving only minor validation gaps.	4 / 5
Progressive Disclosure	Sections are organized, but the full command reference is inlined in one ~290-line file with no bundle references; the only pointers (README.md, TEST.md, HARNESS.md) go to external package docs rather than in-bundle files.	3 / 5
	Total	15 / 20 Passed

Description

58%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 clearly states what the skill does with concrete, domain-specific actions, but omits any 'when to use' trigger guidance. It is distinctive enough for the Blender niche yet relies on somewhat technical phrasing.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g. 'Use when editing or rendering 3D scenes in Blender via command line, or when the user mentions Blender, .blend files, or bpy scripting').

Broaden trigger-term coverage with natural synonyms and file extensions users actually say, such as '3D modeling', 'Blender scene', and '.blend'.

Drop the 'following the same patterns as the GIMP CLI harness' qualifier from the description (move it into the body) to reduce overlap cues with the GIMP CLI skill.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'stateful command-line interface for 3D scene editing', 'JSON scene description format', 'bpy script generation for actual Blender rendering' — with only minor gaps in coverage.	4 / 5
Completeness	The 'what' is clear (stateful CLI for 3D scene editing with JSON/bpy), but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Relevant terms like 'Blender', '3D scene editing', and 'rendering' appear, but common variations/synonyms (e.g. '3D modeling', '.blend') are absent and technical phrasing ('bpy script generation') dominates.	3 / 5
Distinctiveness Conflict Risk	The Blender-specific niche is mostly distinct with minimal conflict risk, though 'following the same patterns as the GIMP CLI harness' creates minor overlap with that related skill family.	4 / 5
	Total	14 / 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: blender/agent-harness/cli_anything/blender/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.