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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill aceternity-uiOverall
score
74%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 effectively communicates both capabilities and usage triggers. It names 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 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 actions and technologies are named. | 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'). Has explicit 'Use for' trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 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 developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific library name 'Aceternity UI', specific framework combination '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 has excellent actionability with complete, executable code examples and clear installation commands. However, it severely violates conciseness principles by including extensive component documentation that belongs in reference files, explaining concepts Claude already knows, and padding with unnecessary sections like 'Token Efficiency' and 'License'. The skill would be far more effective at ~150 lines with component details moved to the referenced catalog.
Suggestions
Move all 15 component category sections to component-catalog.md and keep only 2-3 representative examples 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 entirely - it's self-contradictory and adds unnecessary tokens
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'). Manual installation fallback is clear but missing error recovery guidance. | 2 / 3 |
Progressive Disclosure | References external files (quick-start.md, component-catalog.md) appropriately, but the main SKILL.md contains too much inline content that should be in those reference files. The 15 component category sections should be in the catalog, not here. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 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 |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 13 / 16 Passed | |
- Reviewed
Table of Contents
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.