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.

Quality

62%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/aceternity-ui/skills/aceternity-ui/SKILL.md

Quality

Content

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 far too verbose for its purpose, containing ~500+ lines of content that largely duplicates what should be in reference files. The component catalog, best practices (dark mode, responsive design, TypeScript), and accessibility guidance are all things Claude already knows or that belong in separate reference documents. The genuinely valuable content—registry configuration, CLI commands, troubleshooting common Aceternity-specific errors—is buried in noise.

Suggestions

Reduce the main SKILL.md to ~100 lines covering only: registry configuration JSON, CLI install commands, the 'use client' + motion dependency gotchas, and the reference file loading table. Move all component categories to component-catalog.md.

Remove sections that explain concepts Claude already knows: dark mode classes, responsive Tailwind prefixes, TypeScript interfaces, ARIA labels, and basic accessibility patterns.

Delete the 'Token Efficiency' section entirely—it wastes tokens explaining token savings and adds no actionable guidance.

Add a validation checkpoint after `shadcn init` (e.g., 'Verify components.json was created before proceeding') to improve workflow clarity for the multi-step installation process.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 500+ lines. Explains concepts Claude already knows (dark mode via Tailwind classes, responsive design with Tailwind prefixes, TypeScript prop types, what ARIA labels are). The component categories section is a massive catalog listing 100+ components with 'When to Use' bullet lists that add little value. The 'Token Efficiency' section ironically wastes tokens explaining how many tokens it saves. Much of this content belongs in reference files, not the main SKILL.md.	1 / 3
Actionability	Provides executable code examples for installation and component usage, which is good. However, many examples are basic boilerplate that Claude could generate without guidance (e.g., dark mode classes, responsive prefixes, TypeScript interfaces). The registry configuration JSON and CLI commands are genuinely useful and actionable, but the component usage examples are mostly trivial imports with minimal props.	2 / 3
Workflow Clarity	The installation workflow is reasonably sequenced (create project → init shadcn → configure registry → install components), and troubleshooting covers common errors. However, there are no explicit validation checkpoints between steps (e.g., verify shadcn init succeeded before configuring registry). The manual installation fallback path is mentioned but the transition criteria ('if the registry method doesn't work') is vague.	2 / 3
Progressive Disclosure	The skill references `references/quick-start.md` and `references/component-catalog.md` with a helpful loading table, which is good progressive disclosure design. However, the main SKILL.md itself contains enormous amounts of content that should be in those reference files (the entire component categories section with 15 categories is essentially a component catalog duplicated inline). The bundle has no files provided, so we can't verify the references exist, but the SKILL.md fails to be a lean overview.	2 / 3
	Total	7 / 12 Passed

Description

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 description that clearly identifies its niche (Aceternity UI animated components) and provides explicit trigger guidance. The trigger terms are well-chosen and cover natural user language. The main weakness is that it describes what the skill contains rather than what concrete actions it enables (e.g., installing, configuring, troubleshooting).

Suggestions

Reframe from a feature list to concrete actions, e.g., 'Installs and configures Aceternity UI animated React components, troubleshoots shadcn CLI integration errors, and customizes hero sections, parallax, and 3D effects in Next.js with Tailwind.'

Dimension	Reasoning	Score
Specificity	Names the domain (animated React components, Aceternity UI) and mentions some specific use cases (hero sections, parallax, 3D effects), but doesn't list concrete actions like 'install components', 'configure animations', or 'troubleshoot CLI errors' — it's more of a feature list than an action list.	2 / 3
Completeness	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 trigger terms users would say: 'animated React components', 'Aceternity UI', 'Next.js', 'Tailwind', 'hero sections', 'parallax', '3D effects', 'animation', 'shadcn CLI'. Good coverage of terms a developer would naturally use when seeking this skill.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to Aceternity UI specifically, with distinct triggers like 'Aceternity', 'shadcn CLI integration errors', '3D effects', and 'parallax'. Unlikely to conflict with generic React or Tailwind skills due to the specific library and animation focus.	3 / 3
	Total	11 / 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 (730 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: 5e92b71

Reviewed: about 2 months 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.