CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

animations-native

Authors performant React Native / Expo animations and gestures with Reanimated and react-native-gesture-handler on the UI thread; web animations go to `animations`. Triggers on "reanimated", "react native animation", "gesture handler", "swipe gesture", "/animations-native".

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary thin-index skill: ordered decision flow, gated phase workflow, phase-mapped required reading, and a completion checklist, with concrete API names and thresholds throughout. The main weakness is redundancy — Core Principles and the Definition of Done restate the Core Bet and Workflow gates — and there is no inline code example. Note: the referenced rules/*.md and ../animations/ files were not present in the provided bundle (only SKILL.md), so the load-on-demand structure could not be verified against actual files.

Suggestions

State the transform/opacity + UI-thread-shared-value rule once (Core Bet or Core Principles) and cross-reference it from the Definition of Done instead of repeating it in all three sections.

Drop or compress Core Principles 4–6, which restate the Workflow phase gates (scheduleOnRN, springs for physical motion, Reduce Motion substitution) nearly verbatim — keep the gates as the single source of truth.

Add one minimal inline snippet (e.g., a shared value driven by withSpring inside a gesture callback) so the CSS-API-vs-worklet split is executable without loading a rule file.

DimensionReasoningScore

Conciseness

The body is dense and skill-specific with no generic explanations, but the same rules are stated three to four times: Core Principles 1–2 restate the Core Bet, Principles 4–6 restate the Workflow phase gates (scheduleOnRN, springs, Reduce Motion), and the Definition of Done repeats both again. Anchor 3 ("mostly efficient but... could be tightened") fits better than 4, where over-explanation would be only minor.

3 / 5

Actionability

Highly concrete directives throughout: exact API names ("animationName / transitionProperty", "withSpring / withDecay", "useNativeDriver: true", "scheduleOnRN (runOnJS on v3)"), numeric thresholds ("Duration 100–500 ms", "60/120 fps"), and tool guidance (Perf Monitor). Falls short of anchor 5's copy-paste-ready examples — there is no inline code snippet — but as a declared thin index it delegates examples to the rule files, so the gap is minor.

4 / 5

Workflow Clarity

The Workflow table sequences phases A and 0–6, each with an explicit Gate (e.g., "Animated property is transform / opacity... a shared value on the UI thread"; "GestureHandlerRootView present"), the decision flow is ordered with a tie-break rule ("First match wins... pick the lower-numbered one"), the Definition of Done provides a checklist, and the measurement phase includes a diagnostic loop ("a UI-thread drop is the animation, a JS-thread-only drop is unrelated React work").

5 / 5

Progressive Disclosure

It declares itself a thin index ("Detailed rules live in rules/*.md and load on demand"), every reference is one level deep and clearly labeled, and the "Required Reading by Phase" table maps each phase to its file — a near-verbatim match for anchor 5's clear overview with well-signaled one-level-deep references. No bundle files were provided in the review directory, so scoring reflects the reference structure itself.

5 / 5

Total

17

/

20

Passed

Description

87%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 in third-person voice that explicitly answers both what and when, routes web animations away to the sibling skill, and lists natural trigger terms. The only gaps are minor: coverage of the review use case and asset-runtimes (Lottie/Rive) it actually supports, and a few trigger synonyms like "expo animation" or "worklet".

DimensionReasoningScore

Specificity

"Authors performant React Native / Expo animations and gestures with Reanimated and react-native-gesture-handler on the UI thread" names the domain plus concrete actions and specific libraries. It stops short of anchor 5's comprehensive coverage: review tasks, Lottie/Rive asset runtimes, and Reduce Motion handling from the body are absent.

4 / 5

Completeness

Both questions are answered explicitly and concretely: the 'what' ("Authors performant React Native / Expo animations and gestures with Reanimated and react-native-gesture-handler on the UI thread") and the 'when' ("Triggers on 'reanimated', 'react native animation', 'gesture handler', 'swipe gesture', '/animations-native'"), plus an explicit routing rule ("web animations go to `animations`").

5 / 5

Trigger Term Quality

Triggers on "reanimated", "react native animation", "gesture handler", "swipe gesture", "/animations-native" — natural phrases users would actually say, matching anchor 4's good coverage. Not a 5: common variants like "expo animation", "worklet", "moti", or the full package name "react-native-gesture-handler" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (React Native / Expo native-thread animation) with platform-specific triggers, and the "web animations go to `animations`" clause explicitly disambiguates the closest sibling skill — minimal conflict risk, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 34 missing, 7 suspicious

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

skills/design/animations-native/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.