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

81%

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

75%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, domain-competent inspection methodology with a clear sequenced workflow, concrete thresholds, a report template, and worked examples. It stays lean and assumes Blender knowledge; the main improvement would be adding an explicit validate-retry loop and optionally offloading examples/thresholds into reference files.

Suggestions

Add an explicit validation feedback loop (e.g., 'Re-run the exporter and re-check foot contact after any fix; only mark pass when thresholds are met') to push workflow_clarity toward 5.

Consider moving the two worked Examples and/or the Practical Thresholds into a references file (e.g., EXAMPLES.md) and linking from the body to improve progressive_disclosure for this longer-than-50-line skill.

Tighten the bone-name enumeration and the blank report template into denser lists to trim a few tokens and lift conciseness toward the lean anchor.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Blender/3D competence without explaining basics, but a few bullet runs (e.g., the bone-name enumeration and the report template) could be tightened, keeping it just below the lean anchor at 5.	4 / 5
Actionability	It gives concrete actionable guidance — specific semantic bones, frame-sampling points, numeric thresholds (1-2 cm, 5%, 30 degrees), a report template, and a real command ("blender --background scene.blend --python collect_motion_state.py") — with only minor gaps versus the fully copy-paste-ready anchor at 5.	4 / 5
Workflow Clarity	The 7-step Inspection Workflow is clearly sequenced with checkpoints (baseline before judging, integrity check before retargeting blame, facts before opinions), but it lacks an explicit validate-fix-retry feedback loop, which would be needed for a 5.	4 / 5
Progressive Disclosure	The skill is a single, well-organized file with clear section headers and no nested references, but it is well over 50 lines with inline examples and thresholds that could optionally be split into reference files, leaving it just short of the ideally-split anchor at 5.	4 / 5
	Total	16 / 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, domain-specific description that pairs an explicit Use-when trigger with a comprehensive list of Blender motion-inspection targets and a screenshot-limitation qualifier that sharpens its niche. The only minor gap is reliance on a single action verb and the absence of file-extension triggers.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete inspection targets ("characters, rigs, poses, animation retargeting, ground contact, facing direction, or model-vs-motion alignment") but relies on a single action verb ("inspecting"), leaving minor coverage gaps relative to the multi-action anchor at 5.	4 / 5
Completeness	It explicitly answers both what (inspecting the listed Blender motion-state targets) and when ("Use this skill when ... where screenshots alone are not enough") with concrete trigger phrases, matching the explicit what-and-when anchor.	5 / 5
Trigger Term Quality	It surfaces natural terms a Blender user would actually say ("Blender characters", "rigs", "poses", "animation retargeting", "ground contact", "facing direction", "screenshots"), with good synonym coverage but missing file-extension-style triggers like .blend, so it stops just short of the comprehensive anchor at 5.	4 / 5
Distinctiveness Conflict Risk	The Blender-specific motion-inspection niche with the "screenshots alone are not enough" qualifier is clearly distinct from generic 3D or render skills and carries minimal trigger conflict risk.	5 / 5
	Total	18 / 20 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: 06c5e11

Reviewed: 3 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.