CtrlK
BlogDocsLog inGet started
Tessl Logo

blender-mcp

Drive Blender via the catalog blender MCP, with bpy recipes.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/creative/blender-mcp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-organized, actionable overview: executable bpy recipes and concrete commands, a sequenced workflow with validation checkpoints, and clean progressive disclosure into three real reference files.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains basics like what Blender or bpy is, and every section (prerequisites, quick reference, procedure, bpy patterns, pitfalls, verification) earns its place with tight, task-relevant content, matching 'lean and efficient; assumes competence'.

3 / 3

Actionability

It provides fully executable, copy-paste-ready bpy code (clear scene, add meshes, create/assign materials, keyframes, render) plus concrete shell commands ('hermes mcp install blender', 'xvfb-run blender'), matching 'fully executable code/commands; specific examples; copy-paste ready'.

3 / 3

Workflow Clarity

The Procedure gives a clear 4-step sequence with explicit validation checkpoints ('Verify visually with get_viewport_screenshot between major steps', a dedicated Verification section) and error-recovery feedback in Pitfalls ('Connection refused' means Blender isn't running — fix that, don't retry), matching 'clear sequence with explicit validation steps; feedback loops'.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview with a well-signaled reference table pointing one level deep to real files (references/bpy-api.md, references/recipes.md, references/pitfalls.md, all present), with content appropriately split and easy navigation, matching 'clear overview with well-signaled one-level-deep references'.

3 / 3

Total

12

/

12

Passed

Description

57%

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 is specific and distinctive but terse, covering the 'what' well while omitting explicit 'when to use it' guidance and broader natural trigger terms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to create or modify meshes, materials, animations, lighting, or renders in a running Blender instance.'

Expand trigger coverage with natural variations users would say — '3D', 'modeling', 'rendering', 'animation' — alongside 'Blender' and 'bpy'.

Enumerate a few concrete capabilities in the description (e.g. 'model, texture, animate, and render scenes') to lift specificity from domain-level to multi-action.

DimensionReasoningScore

Specificity

The phrase 'Drive Blender via the catalog blender MCP, with bpy recipes' names the domain and the high-level action (drive) but does not list multiple specific concrete actions (e.g. create meshes, materials, animations, renders), so it sits at 'names domain and some actions, but not comprehensive' rather than the multi-action level 3.

2 / 3

Completeness

It clearly answers 'what does this do' (drive Blender via MCP with bpy recipes) but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline a missing trigger clause caps completeness at 2 rather than 3.

2 / 3

Trigger Term Quality

It includes relevant natural terms a user would say ('Blender', 'bpy') plus the technical 'MCP', but lacks common variations users might actually say ('3D', 'modeling', 'rendering', 'animation'), matching 'some relevant keywords but missing common variations' rather than the broad coverage of level 3.

2 / 3

Distinctiveness Conflict Risk

'Blender via the catalog blender MCP, with bpy recipes' carves out a clear, narrow niche tied to a specific tool and API, making it unlikely to trigger for unrelated skills; it matches 'clear niche with distinct triggers; unlikely to conflict'.

3 / 3

Total

9

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
NousResearch/hermes-agent
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.