CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blender-motion-state-inspection

Use this skill when inspecting Blender characters, rigs, poses, animation retargeting, ground contact, facing direction, or model-vs-motion alignment where screenshots alone are not enough.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-structured, dense procedural skill: the inspection workflow is clearly sequenced with explicit validation gates, quantified thresholds, and worked examples with real measured facts. Main gaps are the redundancy between 'How It Works' and 'Inspection Workflow', and the absence of the actual Blender state-extraction script the workflow depends on.

Suggestions

Provide the actual Blender state exporter (or a reference collect_motion_state.py in scripts/) — the workflow's core extraction step currently tells the agent to write the tool itself instead of supplying it.

Merge 'How It Works' into the 'Inspection Workflow' section (or drop it) — its five steps restate the seven-step workflow and add token cost without new information.

Move the two worked Examples and/or the Report Shape template into a one-level-deep references/ file (e.g. references/examples.md) to slim the main SKILL.md and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and imperative with no filler — lines like 'Ground penetration: compare lowest foot or shoe vertices with floor height per frame' and the quantified 'Practical Thresholds' (1-2 cm, 5%, 30 degrees per frame) earn their tokens, and it never explains basics Claude already knows. It is not 5 because the 'How It Works' section substantially duplicates the 'Inspection Workflow' steps, and 'Core Principle' restates the description — trimmable redundancy.

4 / 5

Actionability

Concrete guidance is strong: a runnable command ('blender --background scene.blend --python collect_motion_state.py'), specific bone names, quantified thresholds, and worked examples with measured facts ('foot.L min_z = 0.004', 'foot.L x = 0.21 -> 0.28'). It is not 5 because the central extraction step — the Blender state exporter / collect_motion_state.py script — is referenced but never provided, so the agent must author the key tooling itself; it is well above 3 because the surrounding guidance is executable and specific rather than pseudocode.

4 / 5

Workflow Clarity

The 7-step 'Inspection Workflow' is clearly sequenced with explicit validation gates: 'Establish the clean scene and asset baseline before judging motion', 'Check model integrity before retargeting blame', 'Report facts before opinions', plus adaptive sampling ('sample more densely around flips, landings, turns') and a report template acting as a checklist. It is not 4 because checkpoints are not merely present — they are explicit ordering principles enforced at every phase with error-recovery guidance in the anti-patterns; the read-only nature of inspection means the destructive-batch cap does not apply.

5 / 5

Progressive Disclosure

The skill is a single self-contained file (no references/, scripts/, or assets/ exist) with well-labeled sections (When to Use, Workflow, Report Shape, Examples, Thresholds, Anti-Patterns, Tooling Notes), so navigation is easy. It is not 5 because at ~156 lines the worked Examples and Report Shape template are natural candidates for one-level-deep reference files that would slim the main file, and no external references are signaled at all; it is well above 3 because the structure is consistent and nothing is buried.

4 / 5

Total

17

/

20

Passed

Description

87%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 strong, focused description: it explicitly states both what the skill does and when to use it, with concrete domain-specific trigger terms and a useful discriminator condition. Its only weakness is that the capability list is expressed through one action verb and misses a few natural synonyms (foot sliding, mirrored, avatar, .blend).

DimensionReasoningScore

Specificity

Quotes like 'inspecting Blender characters, rigs, poses, animation retargeting, ground contact, facing direction, or model-vs-motion alignment' enumerate several concrete, domain-specific capabilities with a discriminator condition ('where screenshots alone are not enough'). It stays at 4 rather than 5 because the capability set hangs on a single action verb ('inspecting') rather than listing multiple distinct concrete actions, and at 3 because the coverage is far more specific and comprehensive than 'names domain and 1-2 concrete actions'.

4 / 5

Completeness

The 'what' is explicit (inspection of Blender characters/rigs/poses/retargeting/ground contact/facing/model-vs-motion alignment) and the 'when' is an explicit 'Use this skill when...' clause with concrete trigger phrases plus a scope condition. This matches the score-5 anchor (both what and when clearly and explicitly answered with concrete triggers); it is not 4 because the 'when' is not merely implied or generic — it names the exact situations and the screenshot-insufficiency condition.

5 / 5

Trigger Term Quality

Natural terms a user would say are well covered: 'Blender', 'characters', 'rigs', 'poses', 'animation retargeting', 'ground contact', 'facing direction', 'screenshots'. It falls short of 5 because common variations and extensions are missing — e.g. 'foot sliding', 'mirrored', 'avatar', '.blend', 'skating' — while clearly exceeding 3's 'some relevant keywords but missing common variations'.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (Blender animation/motion-state inspection with structured-facts-vs-screenshot framing) with distinct trigger terms unlikely to fire for unrelated skills. It is not 4 because there is no meaningful overlap risk with closely related skills — the domain and discriminator ('where screenshots alone are not enough') are tightly scoped.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

affaan-m/ECC

Path

skills/blender-motion-state-inspection/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.