create-motion
Generate motion specification annotations from After Effects timeline data. Use when the user mentions "motion", "motion spec", "animation spec", "timeline", or wants to document a component's animation properties.
86
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with clear trigger terms, explicit 'Use when' guidance, and a distinctive niche. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond just 'generate motion specification annotations.' Overall it performs well for skill selection purposes.
Suggestions
Expand the capability description with more specific actions, e.g., 'Generate motion specification annotations from After Effects timeline data, including keyframe timing, easing curves, duration, and property transitions.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('motion specification annotations from After Effects timeline data') and a general action ('generate'), but doesn't list multiple specific concrete actions like extracting keyframes, documenting easing curves, or outputting timing values. | 2 / 3 |
Completeness | Clearly answers both 'what' (generate motion specification annotations from After Effects timeline data) and 'when' (explicit 'Use when...' clause with specific trigger terms and use cases). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'motion', 'motion spec', 'animation spec', 'timeline', 'animation properties', and 'After Effects'. These cover common variations a user would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining After Effects, motion specs, and animation documentation. Unlikely to conflict with other skills due to the specific domain of motion specification annotations from timeline data. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill with a clear multi-step workflow, executable code for every step, and proper validation checkpoints. Its main weakness is length — the inline code blocks make it very long, and the repeated font-loading boilerplate adds unnecessary tokens. The progressive disclosure could be improved by extracting code templates into separate referenced files.
Suggestions
Extract the repeated font-loading boilerplate into a shared helper pattern referenced once, rather than duplicating it in Steps 9, 10, 11, and 13.
Consider moving the large code blocks for each step into separate referenced files (e.g., `motion-step10-ruler.js`) and keeping only the step descriptions and placeholder instructions in the main SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~400+ lines) with extensive code blocks that are largely necessary for the task, but there's some redundancy in font-loading boilerplate repeated across nearly every code block. The MCP adapter table is useful but verbose. The skill assumes Claude's competence in most areas but could be tightened in places like the repeated font-loading pattern. | 2 / 3 |
Actionability | Every step includes fully executable JavaScript code with clear placeholder conventions (__PLACEHOLDER__). The code is copy-paste ready with specific node selectors, return values, and error handling. The MCP adapter table provides concrete operation mappings for both providers. | 3 / 3 |
Workflow Clarity | The 15-step workflow is clearly sequenced with a progress checklist, explicit validation in Step 14 (visual validation with up to 3 fix iterations), and clear error handling throughout (e.g., missing template keys, failed MCP connections, validation failures). The feedback loop for visual validation is well-defined. | 3 / 3 |
Progressive Disclosure | The skill references an external instruction file (agent-motion-instruction.md) for JSON schema and validation rules, which is good progressive disclosure. However, the main SKILL.md itself is monolithic with all code blocks inline rather than being split into referenced files. The extensive code blocks for each step could benefit from being in separate files with the SKILL.md serving as a higher-level overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- redongreen/uSpec
- Commit
b1213ef
- 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.