animate

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.

1.42x

Quality

72%

Does it follow best practices?

Impact

91%

1.42x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./archived/legacy-companion/.agents/skills/animate/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

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

A well-sequenced, highly actionable skill with strong validation checkpoints and concrete code, but it is a monolithic single file and the long category catalogs inflate token use. Splitting catalogs into reference files would improve both conciseness and disclosure.

Suggestions

Move the detailed animation category catalogs (Entrance, Micro-interactions, State Transitions, Navigation, Delight) into a bundled reference file, keeping only the strategy and decision guidance inline in SKILL.md.

Tighten the catalog lists to the high-impact cases per category rather than enumerating every variant, reducing token cost.

Replace the non-executable bullet lists inside ```css and ```javascript fences with either real code or plain markdown to avoid implying runnable examples where there are none.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concepts Claude already knows, but the exhaustive category catalogs (every micro-interaction and state-transition type) pad the body and could be tightened without losing value.	2 / 3
Actionability	Provides copy-paste-ready CSS easing variables, a duration-by-purpose table, and an executable prefers-reduced-motion media query, with concrete numeric guidance throughout.	3 / 3
Workflow Clarity	Clear sequence (Prepare → Assess → Plan → Implement → Technical → Verify) with explicit STOP/AskUserQuestion checkpoints, 'Do NOT proceed until…' gates, and a verification checklist for feedback loops.	3 / 3
Progressive Disclosure	The ~180-line body is a single monolithic file with no bundle files or references; the detailed animation catalogs that could live in separate references are all inline.	2 / 3
	Total	10 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 names concrete capabilities and carves out a clear niche, but omits any explicit 'Use when…' trigger guidance and offers limited keyword variation. Adding a trigger clause and natural synonyms would round it out.

Suggestions

Append a 'Use when…' clause with explicit triggers, e.g. 'Use when adding animations, micro-interactions, or motion to a feature, or when the user mentions transitions, hover effects, or page-load animation.'

Broaden natural keyword coverage with synonyms users actually say (e.g. 'transitions', 'hover effects', 'page-load choreography', 'motion design').

Dimension	Reasoning	Score
Specificity	Lists multiple concrete action types — 'purposeful animations, micro-interactions, and motion effects' — naming several specific enhancement categories rather than vague language.	3 / 3
Completeness	Clearly states what the skill does but provides no 'Use when…' clause or equivalent explicit guidance on when Claude should invoke it, capping completeness at 2.	2 / 3
Trigger Term Quality	'animations, micro-interactions, and motion effects' are somewhat natural but lack common variations and synonyms a user would actually say, with no explicit trigger clause.	2 / 3
Distinctiveness Conflict Risk	The animation/motion niche is clearly delimited and unlikely to trigger for unrelated skills, despite light adjacency to a general frontend-design skill.	3 / 3
	Total	10 / 12 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: The-Vibe-Company/companion
Path: archived/legacy-companion/.agents/skills/animate/SKILL.md
Commit: 90804d3

Reviewed: 18 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.