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

83%

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

Quality

Content

77%

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

A strong, well-structured diagnostic skill with concrete commands, numeric thresholds, and a clear sequenced workflow. Its main gaps are mild verbosity from overlapping overview/workflow sections and a lack of externalized reference files for a 160-line document.

Suggestions

Merge or trim "How It Works" against the "Inspection Workflow" to remove overlap and reduce token load on the conciseness dimension.

Consider moving the two full worked examples and/or the Practical Thresholds into a separate references file linked from the body to improve progressive disclosure.

Add an explicit measure→compare→re-measure checkpoint note in the workflow to make the diagnostic feedback loop more visible.

Dimension	Reasoning	Score
Conciseness	The body is domain-specific and largely avoids explaining concepts Claude already knows, but at ~160 lines it carries some redundancy (e.g., "How It Works" overlaps the later "Inspection Workflow") and could be tightened to earn a 3.	2 / 3
Actionability	It gives a concrete executable command ("blender --background scene.blend --python collect_motion_state.py"), specific comparison instructions ("compare lowest foot or shoe vertices with floor height per frame"), numeric thresholds, and worked example tables with real coordinates, making the guidance copy-paste-ready for an instruction-oriented skill.	3 / 3
Workflow Clarity	A clearly sequenced 7-step Inspection Workflow with sub-bullets, plus a checklist-style Recommended Report Shape and explicit compare-against-expected checkpoints; the operations are read-only diagnostics so the destructive-batch cap does not apply.	3 / 3
Progressive Disclosure	Sections are well-organized with clear headers, but no bundle files exist and the skill is a single monolithic file where worked examples, the report template, and thresholds could plausibly be externalized for progressive disclosure.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 well-crafted, third-person description with an explicit "Use when" trigger and a distinctive niche. Its only weakness is that it stacks many nouns under one verb rather than enumerating several concrete actions.

Dimension	Reasoning	Score
Specificity	The description names a clear domain ("inspecting Blender characters, rigs, poses, animation retargeting, ground contact, facing direction") but relies on a single verb ("inspecting") applied to many nouns rather than listing multiple distinct concrete actions; it is not the vague 1 but does not reach the multi-action 3.	2 / 3
Completeness	It explicitly answers both what ("inspecting Blender characters, rigs, poses...") and when with an explicit trigger clause ("Use this skill when ... where screenshots alone are not enough"), matching the clear what-and-when anchor.	3 / 3
Trigger Term Quality	Phrases like "Blender characters, rigs, poses, animation retargeting, ground contact, facing direction" are natural terms a user working in this area would actually say, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Blender motion/3D-inspection niche is narrow with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: 754b8dd

Reviewed: 2 days 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.