CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fixing-motion-performance

Fix animation performance issues. Use for motion audits or refactors.

Quality

75%

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 ./.agents/skills/04-develop/01-ui-skills-dot-com/fixing-motion-performance/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The body is a dense, well-structured ruleset that assumes Claude's competence and stays actionable: concrete thresholds, named mechanisms, a priority ordering for reviews, and an explicit verification step with real commands. It consistently sits at the strong-but-not-perfect level across all dimensions, with only minor redundancy and a few directives that would benefit from concrete examples.

DimensionReasoningScore

Conciseness

The body is a lean bullet ruleset with no explanations of concepts Claude already knows; only minor trimmable fat remains ("Source: ui-skills.com.", the repeated tagline, and the migration rule stated both in the intro and in section 9).

4 / 5

Actionability

Concrete, specific rules throughout ("keep blur animation small (<=8px)", "prefer Scroll or View Timelines", "use IntersectionObserver for visibility and pausing") plus executable commands (pnpm lint/test/build/verify); as an instruction-only skill the absence of code is not penalized, though a few directives like "prefer FLIP-style transitions" lack a concrete example.

4 / 5

Workflow Clarity

A coherent review workflow is present — violation report format (quote, why, fix), enforce-critical-first ordering, justification requirement for non-default choices, and an explicit verify step ending in GO/NO-GO with evidence — but it is not a strictly numbered sequence and has no error-recovery loop, so it falls short of the explicit-checkpoint anchor 5.

4 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md (~125 lines) is well-organized with a priority table, glossary, nine clearly-headed rule categories, and review/verify sections, with all content reasonably placed inline — only a minor gap in that the detailed category rules could later be split into a reference file.

4 / 5

Total

16

/

20

Passed

Description

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

The description is concise, honest, and clearly niche, explicitly covering both what and when. Its weaknesses are thin action coverage and trigger vocabulary that misses the natural terms (jank, stutter, slow/FPS) users would most likely say when they need this skill.

Suggestions

Add one or two more concrete actions to the what-clause, e.g. "Fix animation performance issues: audit janky motion, choose compositor-friendly techniques (transform/opacity), and refactor scroll-linked effects."

Broaden trigger terms with natural user phrasings: "Use when the user reports janky, slow, or stuttering animations, asks for a motion audit, or wants to refactor transitions or scroll-linked effects."

Mention the stacks the rules apply to (CSS, WAAPI, Motion, GSAP, rAF) in the description so it triggers when those technologies are named.

DimensionReasoningScore

Specificity

"Fix animation performance issues" names the domain and one concrete action, with "motion audits or refactors" adding only slight breadth — not the several specific actions anchor 4 requires.

3 / 5

Completeness

"Fix animation performance issues" answers what and "Use for motion audits or refactors" answers when, but the when-clause is thin and could be more explicit — the both-present-but-could-be-more-specific anchor. Not 5 because it lacks concrete trigger phrases; not 3 because the when is explicitly stated rather than merely implied.

4 / 5

Trigger Term Quality

"animation performance", "motion audits", and "refactors" are relevant keywords, but common natural phrases users would say ("janky", "slow animations", "stutter", "FPS", "scroll lag") are missing, matching the some-keywords-but-missing-variations anchor.

3 / 5

Distinctiveness Conflict Risk

Animation performance repair is a clear niche with mostly distinct triggers; only minor overlap risk with closely related general performance-profiling or animation-authoring skills.

4 / 5

Total

14

/

20

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

Validation for skill structure

No warnings or errors.

Repository

marchatton/agent-skills

Path

.agents/skills/04-develop/01-ui-skills-dot-com/fixing-motion-performance/SKILL.md

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.