sprite-animation

A pixel / sprite-style animated explainer slide — full-bleed cream stage, bold display year, animated pixel-art mascot (e.g. Hanafuda card, mushroom, or 8-bit console), kinetic Japanese display type, ticking timeline ribbon. Reads like a single frame of an educational motion video — looping CSS keyframes, no JS, ready to be screen-recorded into a vertical video. Use when the brief asks for a "sprite animation", "pixel-art video", "8-bit explainer", "history of X explainer", "kinetic typography history", "Nintendo-style", "精灵图动画", "像素动画", or "复古动画".

Quality

94%

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

93%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.

The content is an excellent example of a compact generative skill: lean, unambiguous, and loaded with exact specifications (colors, dimensions, timings, years, output contract) plus a closing self-check. The only gap is the absence of an explicit fix-and-recheck loop after the self-check step.

Dimension	Reasoning	Score
Conciseness	The body is lean and imperative with zero padding — every step contributes spec value Claude does not already know (exact hex color, sprite dimensions, animation timing, palette constraint), and no concepts are re-explained.	5 / 5
Actionability	Guidance is fully executable for a generative task: exact stage color '#f5efe2', a '96×128 pixel-art card', 'bobbing animation (±4px, 1.6s)', 'shape-rendering: crispEdges', concrete tick years (1889 · 1907 · 1949 · 1977 · 1985 · 2006 · 2017), 'data-od-id' placement, and a literal output-contract template. This matches the instruction-only ideal of concrete, specific guidance.	5 / 5
Workflow Clarity	The 8-step sequence is clearly ordered and ends with an explicit self-check checklist (cohesion, 3+ animations, restrained palette, no external assets), but there is no error-recovery feedback loop; it sits between the 'most checkpoints present' and 'explicit validation with feedback loops' anchors.	4 / 5
Progressive Disclosure	The body is ~60 lines, well-sectioned (intro, Workflow, Output contract), and needs no external reference files — the only referenced file (DESIGN.md) is platform-injected at runtime rather than a bundle path, so the single-file organization is appropriate.	5 / 5
	Total	19 / 20 Passed

Description

95%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 description: it concretely describes the deliverable, its technical constraints (CSS-only looping animation, single HTML frame), and when to invoke it, with comprehensive bilingual trigger coverage. The only weakness is that capabilities are presented as descriptive elements rather than explicit actions.

Dimension	Reasoning	Score
Specificity	The description lists several concrete, specific elements ('full-bleed cream stage', 'animated pixel-art mascot (e.g. Hanafuda card, mushroom, or 8-bit console)', 'ticking timeline ribbon', 'looping CSS keyframes, no JS, ready to be screen-recorded into a vertical video') but frames them as descriptive noun phrases rather than the multiple concrete actions anchor 5 calls for.	4 / 5
Completeness	It explicitly answers both questions: a detailed 'what' (the exact composition of the animated explainer slide and its technical constraints) and a concrete 'when' ('Use when the brief asks for a...') with literal trigger phrases, matching the anchor-5 example pattern.	5 / 5
Trigger Term Quality	The 'Use when' clause covers comprehensive natural terms with synonyms — 'sprite animation', 'pixel-art video', '8-bit explainer', 'kinetic typography history', 'Nintendo-style' — and adds bilingual variants ('精灵图动画', '像素动画', '复古动画'), matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	The pixel-art / sprite-animation / retro-explainer niche is clear and the triggers ('8-bit explainer', 'Nintendo-style', '精灵图动画') are distinctive enough that it would not fire for unrelated animation or video skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/sprite-animation/SKILL.md
Commit: 1b47e60

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.