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

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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 highly actionable with executable code and a well-sequenced install workflow supported by clear reference files. Its main weakness is conciseness: the inlined full component catalog and meta sections (token savings, resource lists) inflate length and duplicate the bundled references.

Suggestions

Replace the inlined 15-category component listing with a concise summary pointing to references/component-catalog.md, keeping only 1-2 representative examples inline.

Remove or trim the 'Token Efficiency' savings estimates and 'Additional Resources' sections, which add tokens without adding actionable guidance.

Add an explicit validate→fix→retry checkpoint after component installation (e.g., run the dev server and confirm no import errors) to lift workflow_clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The ~680-line body includes padded sections ("Token Efficiency" savings estimates, "Additional Resources", per-category "When to Use" lists) and inlines the full 15-category component breakdown that largely duplicates references/component-catalog.md; it is mostly useful but could be tightened considerably.	3 / 5
Actionability	Provides copy-paste ready TSX examples, concrete install commands for bun/npm/pnpm, a full components.json snippet, a manual-install fallback, and troubleshooting fixes — fully executable across common cases.	5 / 5
Workflow Clarity	Installation is clearly sequenced (create project → shadcn init → configure registry → add component → manual fallback) with supply-chain checkpoints (audit before installing, block post-install scripts), though it lacks an explicit validate→fix→retry loop.	4 / 5
Progressive Disclosure	Good structure with a 'When to Load References' table and two real one-level-deep reference files (quick-start.md, component-catalog.md) clearly signaled; minor gap is the inlined 15-category listing that overlaps the catalog reference.	4 / 5
	Total	16 / 20 Passed

Description

83%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 is strong: it pairs a concrete product framing with an explicit 'Use for...' trigger clause and natural scenario keywords, satisfying both what and when. Minor specificity could be added by naming concrete component actions (install, customize) rather than only scenarios.

Dimension	Reasoning	Score
Specificity	Names the domain ("100+ animated React components (Aceternity UI) for Next.js with Tailwind") and lists several concrete use scenarios ("hero sections, parallax, 3D effects"), comparable to the anchor listing several specific actions with minor gaps; it stops short of enumerating actual component actions like install/customize.	4 / 5
Completeness	Clearly states what (animated React components for Next.js/Tailwind via shadcn) and explicitly gives when ("Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors"), matching the anchor that answers both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say ("hero sections, parallax, 3D effects, animation") plus a debugging trigger ("shadcn CLI integration errors"), with good keyword coverage but missing some common synonyms and the explicit .tsx/React framing.	4 / 5
Distinctiveness Conflict Risk	Scoped to a named library (Aceternity UI) and shadcn CLI flow, giving it a clear niche with minimal overlap risk; it is not maximally distinctive because the animation/React space has related skills.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

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

	Total	14 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/aceternity-ui/skills/aceternity-ui/SKILL.md
Commit: ad16332

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