aceternity-ui

100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.

1.25x

Quality

62%

Does it follow best practices?

Impact

88%

1.25x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/aceternity-ui/skills/aceternity-ui/SKILL.md

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description that clearly identifies a specific library (Aceternity UI) and its ecosystem (Next.js, Tailwind), includes explicit trigger guidance via 'Use for...', and has strong natural keywords. The main weakness is that the capabilities could be more specific about what actions the skill enables (e.g., installing, configuring, troubleshooting) rather than just listing component categories.

Suggestions

Add more specific action verbs describing what the skill does, e.g., 'Installs, configures, and troubleshoots 100+ animated React components' rather than just listing the component count.

Dimension	Reasoning	Score
Specificity	Names the domain (animated React components, Aceternity UI) and some actions/use cases (hero sections, parallax, 3D effects), but doesn't list specific concrete actions like 'install components', 'configure animations', or 'troubleshoot CLI errors' in detail.	2 / 3
Completeness	Clearly answers both what (100+ animated React components for Next.js with Tailwind) and when ('Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors'). The 'Use for' clause serves as an explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'animated React components', 'Aceternity UI', 'Next.js', 'Tailwind', 'hero sections', 'parallax', '3D effects', 'animation', 'shadcn CLI'. Good coverage of terms a user working with this library would naturally mention.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific library name 'Aceternity UI', the combination of Next.js + Tailwind + animation, and the mention of shadcn CLI integration errors. Unlikely to conflict with generic React or CSS skills.	3 / 3
	Total	11 / 12 Passed

Implementation

35%

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

This skill is significantly over-engineered and verbose for its purpose. It contains extensive component catalog information inline that should be in reference files, explains many concepts Claude already knows (dark mode, responsive design, TypeScript, accessibility basics), and includes a self-congratulatory 'Token Efficiency' section that ironically wastes tokens. The actionable parts (installation, registry config, troubleshooting) are useful but buried in unnecessary content.

Suggestions

Reduce the main SKILL.md to ~100 lines covering only: installation/registry setup, one usage example, common gotchas (missing motion dep, use client directive, cn utility), and references to detailed files. Move all component categories to component-catalog.md.

Remove sections that explain things Claude already knows: dark mode via Tailwind classes, responsive design prefixes, TypeScript interfaces, basic ARIA labels, and the 'Token Efficiency' self-assessment section.

Add explicit validation steps to the installation workflow, e.g., 'Run `bun dev` and verify no errors' after setup, and 'Import and render the component, verify animation works' after component installation.

Consolidate the 15 component category sections into a brief summary table (category | count | example component | install command) and point to component-catalog.md for full details.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 500+ lines. Explains concepts Claude already knows (dark mode, responsive design, TypeScript interfaces, ARIA labels). The 'Token Efficiency' section is self-referential filler. Component category listings with 'When to Use' bullet points are largely obvious. The 'Key Features' list restates what any React component library is.	1 / 3
Actionability	Provides executable code examples for installation and component usage, which is good. However, many sections are descriptive catalogs rather than actionable guidance (e.g., listing 28 background components by name without install commands). The code examples are functional but often trivial/boilerplate that Claude could generate without instruction.	2 / 3
Workflow Clarity	The installation workflow is reasonably sequenced (create project → init shadcn → configure registry → install components), but lacks explicit validation checkpoints. There's no 'verify installation worked' step after setup. The troubleshooting section helps but is disconnected from the workflow rather than integrated as validation steps.	2 / 3
Progressive Disclosure	References quick-start.md and component-catalog.md with a useful table for when to load them. However, the main SKILL.md itself is a monolithic wall containing extensive component catalogs, best practices, and troubleshooting that should largely live in those reference files. The component categories section alone is hundreds of lines that belong in component-catalog.md.	2 / 3
	Total	7 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (720 lines); consider splitting into references/ and linking	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: secondsky/claude-skills
Commit: 88da5ff

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