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

75%

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

100%

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 strong skill description that clearly identifies the specific library (Aceternity UI), technology stack (Next.js, Tailwind, React), concrete use cases (hero sections, parallax, 3D effects), and even troubleshooting scenarios (shadcn CLI integration errors). The 'Use for...' clause provides explicit trigger guidance. The description is concise yet comprehensive.

Dimension	Reasoning	Score
Specificity	Lists specific concrete elements: '100+ animated React components', 'Aceternity UI', 'Next.js with Tailwind', 'hero sections, parallax, 3D effects', and 'shadcn CLI integration errors' - multiple specific capabilities clearly stated.	3 / 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') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes natural terms users would say: 'animated React components', 'Aceternity UI', 'Next.js', 'Tailwind', 'hero sections', 'parallax', '3D effects', 'animation', 'shadcn CLI' - good coverage of both library names and feature types.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with specific library name 'Aceternity UI', technology stack 'Next.js with Tailwind', and unique use cases like 'shadcn CLI integration errors' - unlikely to conflict with generic React or animation skills.	3 / 3
	Total	12 / 12 Passed

Implementation

50%

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

This skill provides excellent actionable guidance with complete, executable code examples and proper installation commands. However, it severely violates conciseness principles by including extensive component documentation that belongs in reference files, explaining basic concepts Claude knows, and padding with unnecessary sections like 'Token Efficiency' and 'License'. The content would be far more effective at 150-200 lines with component details moved to the referenced catalog.

Suggestions

Move the 15 component category sections (lines ~150-450) to component-catalog.md and keep only a brief summary table in the main skill

Remove explanatory content Claude already knows: what Tailwind/TypeScript/React are, what dark mode is, basic responsive design concepts

Delete the 'Token Efficiency' section - it's meta-commentary that adds tokens while claiming to save them

Add validation checkpoints to installation workflow: 'Run `bun dev` and verify no errors before proceeding'

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 600+ lines. Explains concepts Claude already knows (what Tailwind is, what TypeScript is, basic React patterns). The 'Token Efficiency' section ironically adds tokens while claiming to save them. Component categories section is exhaustive when a reference file would suffice.	1 / 3
Actionability	Provides fully executable code examples throughout - installation commands, component usage, configuration files. All code is copy-paste ready with proper imports and complete implementations.	3 / 3
Workflow Clarity	Installation steps are sequenced but lack validation checkpoints. No explicit verification steps after setup (e.g., 'run dev server to confirm installation'). Troubleshooting is reactive rather than integrated into the workflow.	2 / 3
Progressive Disclosure	References quick-start.md and component-catalog.md appropriately, but the main file contains excessive inline content that should be in those reference files. The 15 component category sections with examples belong in the catalog, not the overview.	2 / 3
	Total	8 / 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: 90d6bd7

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