BC motion-design
Apply motion craft to an active task: refine a brief, beat map, visual continuity, typography, pacing, and timeline implementation. Use when planning or improving motion graphics; the host task owns artifact creation, output format, and export.
Promises to refine motion design workflow: sharpen the brief, map beats, maintain visual continuity, handle typography, pacing, and timeline. Use when planning or polishing animation—host owns artifact creation and export.
Two files, no scripts. Checks found no critical issues: grade B, quality 75%, process 61%. Works across all major platforms from Claude to DeepSeek. The catch: it's mostly a thinking framework, not an automation tool. You'll need to decide which parameters to adjust and how to apply them yourself. If you want structured help with animation planning rather than hands-off execution, install it.
Apply motion craft to an active task: refine a brief, beat map, visual continuity, typography, pacing, and timeline implementation.
As a process C 61/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5696 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "od"
Process rating: all ten parameters 61/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Execution cost. Instruction body is 5696 tokens
- 100Steps. 23 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 244: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 23 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.