CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-animations

Use when reviewing animation and motion code against a strict craft, performance, accessibility, and interaction-quality bar.

Quality

73%

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/review-animations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 an unusually crisp, opinionated review playbook with concrete thresholds, a clear remedial hierarchy, and explicit verdict criteria — its workflow and actionability are strong. Its one serious defect is that the entire detailed standards catalog it repeatedly cites lives in a STANDARDS.md file that is absent from the bundle, leaving the progressive-disclosure promise broken and exact values unretrievable.

Suggestions

Ship STANDARDS.md alongside SKILL.md (or inline the essential easing/duration/spring tables) — the body defers exact values to it four times, but no such file exists in the bundle.

Inline a few fallback defaults (e.g., a recommended cubic-bezier and per-element duration budgets) so findings can cite specifics even when STANDARDS.md is unavailable.

Trim the redundant second 'Examples' paragraph and the review-method provenance paragraph; both restate scope or background already covered elsewhere.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — it never explains what CSS transitions, keyframes, or Framer Motion are, and nearly every line is a rule or threshold ('UI animations stay under 300ms', 'Keyboard-initiated and 100+/day actions get **no** animation'). Minor trimmable padding remains: the second 'Examples' paragraph restates scope already covered in 'When to Use' and 'Limitations', and the attribution paragraph about the review method's provenance is background flavor, keeping it below the lean anchor at 5.

4 / 5

Actionability

Guidance is highly concrete — specific thresholds ('under 300ms', 'scale(0.9–0.97) + opacity', '30–80ms stagger') and copy-paste fixes in the findings table ('transition: transform 200ms ease-out', 'var(--radix-popover-content-transform-origin)'). It misses 5 because exact values (curves, duration tables, spring configs) are deferred to 'pull the exact one from [STANDARDS.md] rather than approximating', and STANDARDS.md does not exist in the bundle, so the promised precision cannot be retrieved.

4 / 5

Workflow Clarity

This single-purpose skill has an unambiguous sequence: measure every animation against the ten standards, flag escalation triggers on sight, propose fixes via the nine-step remedial hierarchy, then emit Part 1 (findings table) and Part 2 (tiered verdict) with explicit Block/Approve criteria that function as validation checkpoints for the decision. The destructive/batch validation cap does not apply since this is a read-only review skill, and the explicit decision criteria ('Block — any feel-breaking regression…', 'Approve — no feel-breaking regressions…') leave no ambiguity about the single action.

5 / 5

Progressive Disclosure

The in-body structure is good and the reference is clearly signaled and one level deep ('For the full rule catalog (easing curves, duration tables, spring config, gestures, clip-path, performance, a11y), see STANDARDS.md'), but scoring against the actual bundle, STANDARDS.md does not exist — there are no references/, scripts/, or assets/ directories at all. Four references to a missing file make the skill's deferred detail catalog a dead end, which is a fundamental organization failure rather than a mere clarity gap.

2 / 5

Total

15

/

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 has an explicit 'Use when' trigger and a well-scoped, distinct niche, but it is thin on both concrete capabilities and natural trigger vocabulary. Naming the outputs (findings table, fixes, Block/Approve verdict) and common terms like transitions, easing, or Framer Motion would raise it substantially.

Suggestions

Add concrete output commitments to the description, e.g. 'Reviews animation and motion code for craft, performance, accessibility, and interaction quality; produces a findings table with suggested fixes and an explicit Block/Approve verdict.'

Include natural trigger terms users would actually say: 'CSS transitions', 'easing', 'Framer Motion', 'hover effects', 'micro-interactions', 'springs', not just 'animation and motion code'.

State what the skill deliberately does not do (general code review, implementing fixes) to sharpen distinctiveness against general review skills.

DimensionReasoningScore

Specificity

The description names the domain and a single action — 'reviewing animation and motion code' — plus the review dimensions ('craft, performance, accessibility, and interaction-quality bar'), but lists no concrete outputs such as a findings table, suggested fixes, or a Block/Approve verdict. It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; it is not generic enough for 2 and does not list several specific actions for 4.

3 / 5

Completeness

Both parts are present: the what ('reviewing animation and motion code against a strict craft, performance, accessibility, and interaction-quality bar') and an explicit when ('Use when reviewing animation and motion code'). It falls short of 5 because the what does not state concrete outputs (e.g., findings table or verdict), and is above 3 because the trigger is explicit rather than implied.

4 / 5

Trigger Term Quality

It includes 'animation', 'motion', 'review', and 'code', but misses natural phrases users would say such as 'transitions', 'easing', 'Framer Motion', 'hover effects', 'micro-interactions', or 'springs'. This fits 'Some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

The animation/motion-review niche is clearly distinguishable from most skills, with only minor overlap risk against a general code-review skill since the phrase 'reviewing animation and motion code' mentions reviewing code. This matches 'Mostly distinct; minor overlap risk with closely related skills' rather than the clear-niche anchor at 5.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 possibly missing (STANDARDS.md)

Warning

Total

14

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/review-animations/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.