CtrlK
BlogDocsLog inGet started
Tessl Logo

makepad-animation

CRITICAL: Use for Makepad animation system. Triggers on: makepad animation, makepad animator, makepad hover, makepad state, makepad transition, "from: { all: Forward", makepad pressed, makepad 动画, makepad 状态, makepad 过渡, makepad 悬停效果

50

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/makepad-animation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Scale 1-5

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

This is a solid animation reference skill with good concrete examples covering the main use cases (hover, pressed, focus, disabled states) and both DSL and Rust API patterns. Its main weaknesses are moderate verbosity from repetitive code patterns and an exhaustive easing list that could be in a reference file, plus unverifiable external file references. The actionability is strong with executable code examples.

Suggestions

Move the exhaustive easing functions list and animatable properties catalog to the referenced `animation-system.md` file, keeping only 2-3 common examples inline to improve conciseness.

Consolidate the four nearly-identical state animation examples (hover, pressed, focus, disabled) into one annotated example showing multiple states, with a brief note on how to adapt for different state types.

Provide the referenced bundle files (`./references/animation-system.md` and `_base/` patterns) or remove the references if they don't exist, to ensure progressive disclosure actually works.

DimensionReasoningScore

Conciseness

The skill is moderately efficient but includes some redundancy — the easing functions list is exhaustive when Claude likely knows standard easing names, and the animatable properties section states obvious things. The code examples are somewhat repetitive (hover, pressed, focus, disabled all follow the same pattern). The 'Documentation Completeness Check' section with Chinese text adds operational overhead.

3 / 5

Actionability

Provides concrete, executable code examples in both DSL and Rust API forms. The examples cover common animation states with copy-paste ready patterns. Minor gap: no complete working example showing a full widget with animation from scratch (imports, struct definition, etc.), and the Rust API example lacks context about where it lives in a full component.

4 / 5

Workflow Clarity

The 'When Writing Code' section provides clear guidelines for choosing animation types. The Rust API section shows a clear event-handling workflow. However, there's no explicit validation or debugging workflow — e.g., what happens when an animation doesn't work, how to verify animations are applied correctly, or common pitfalls. Since animations aren't destructive operations, the missing validation doesn't cap the score.

4 / 5

Progressive Disclosure

References to `./references/animation-system.md` and `_base/` directory patterns are mentioned but no bundle files are provided, making it impossible to verify these exist. The SKILL.md itself inlines a substantial amount of reference material (full easing enum list, all timeline types, animatable properties) that could be in a reference file, while the referenced files may duplicate this content.

3 / 5

Total

14

/

20

Passed

Description

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

The description functions primarily as a trigger-term list rather than a proper skill description. While it excels at providing explicit trigger phrases (including multilingual ones), it completely fails to describe what the skill actually does—what concrete actions or outputs it provides. Adding a clear 'what' statement with specific capabilities would significantly improve it.

Suggestions

Add concrete capability descriptions such as 'Implements hover effects, pressed states, and animated transitions using Makepad's animator system. Configures state definitions, easing curves, and property animations.'

Restructure to lead with a 'what it does' statement before the trigger terms, e.g., 'Configures and implements animations in Makepad including state transitions, hover effects, and pressed states. Use when...'

DimensionReasoningScore

Specificity

The description names the domain (Makepad animation system) but provides no concrete actions. It doesn't describe what the skill actually does—no verbs like 'creates', 'configures', 'implements'. It only lists trigger terms without explaining capabilities.

2 / 5

Completeness

The 'when' is explicitly addressed with trigger terms, but the 'what' is almost entirely missing—there's no description of what the skill actually does beyond 'Makepad animation system'. It says 'Use for Makepad animation system' which is extremely vague on the capability side.

2 / 5

Trigger Term Quality

Good coverage of natural trigger terms including 'makepad animation', 'makepad animator', 'makepad hover', 'makepad state', 'makepad transition', 'makepad pressed', and even Chinese-language equivalents. However, it lacks some natural phrases like 'animate widget', 'fade in/out', or 'easing' that users might say.

4 / 5

Distinctiveness Conflict Risk

The Makepad animation system is a fairly specific niche, and the trigger terms are distinctive enough to avoid conflicts with general animation or CSS transition skills. Minor overlap risk with other Makepad-related skills if they exist, but the animation focus narrows it well.

4 / 5

Total

12

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.