antigravity-design-expert
Core UI/UX engineering skill for building highly interactive, spatial, weightless, and glassmorphism-based web interfaces using GSAP and 3D CSS.
29
22%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-design-expert/SKILL.mdQuality
Discovery
22%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 relies heavily on buzzwords and adjectives ('spatial', 'weightless', 'highly interactive') without specifying concrete actions the skill performs. It lacks a 'Use when...' clause entirely, making it difficult for Claude to know when to select this skill. The niche technology terms (GSAP, glassmorphism) provide some distinctiveness but are not enough to compensate for the lack of actionable detail.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks for glass-effect UI, frosted glass cards, GSAP animations, 3D transforms, or parallax scrolling effects.'
Replace vague adjectives with concrete actions, e.g., 'Creates glassmorphism cards and panels, animates page transitions with GSAP, builds 3D perspective layouts with CSS transforms.'
Include natural user-facing keywords like 'glass effect', 'frosted glass', 'animations', 'hover effects', 'CSS transitions', and file/framework references users might mention.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract adjectives ('highly interactive', 'spatial', 'weightless', 'glassmorphism-based') but does not list any concrete actions. There are no verbs describing what the skill actually does (e.g., 'creates glass-effect cards', 'animates page transitions'). | 1 / 3 |
Completeness | The description partially addresses 'what' (building glassmorphism-based web interfaces) but is vague about concrete capabilities, and there is no 'when' clause or explicit trigger guidance at all. The missing 'Use when...' clause caps this at 2, and the weak 'what' brings it to 1. | 1 / 3 |
Trigger Term Quality | It includes some relevant technical keywords like 'GSAP', '3D CSS', 'glassmorphism', and 'UI/UX' that a user might mention. However, it misses common natural variations like 'glass effect', 'frosted glass', 'animations', 'transitions', 'parallax', or 'hover effects'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'glassmorphism', 'GSAP', and '3D CSS' provides some distinctiveness, but 'UI/UX engineering' and 'web interfaces' are broad enough to overlap with general frontend or CSS skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a design manifesto or persona prompt than an actionable technical skill. It explains concepts Claude already understands (glassmorphism, parallax, GSAP) without providing executable code examples, concrete component templates, or step-by-step workflows. The strongest aspect is its clear organizational structure, but the content needs to shift from describing principles to providing copy-paste ready implementations.
Suggestions
Add at least 2-3 executable React component examples demonstrating key patterns (e.g., a floating glassmorphism card with GSAP entrance animation, an isometric grid layout) instead of just describing the CSS properties.
Remove the 'Role Overview' section entirely and trim explanations of well-known concepts (glassmorphism, parallax, GSAP) to just the specific parameter values and patterns unique to this design system.
Add a step-by-step workflow for building an Antigravity component: e.g., 1) Set up perspective container, 2) Apply glassmorphism base styles, 3) Add GSAP ScrollTrigger animation, 4) Verify prefers-reduced-motion handling, 5) Test GPU performance with DevTools.
Extract detailed animation recipes and component templates into separate referenced files (e.g., ANIMATIONS.md, COMPONENTS.md) to keep SKILL.md as a concise overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains many concepts Claude already knows well (what glassmorphism is, what GSAP does, what React Three Fiber is, basic CSS properties). The 'Role Overview' section is pure fluff that wastes tokens telling Claude what it is. Many CSS values and concepts are over-explained rather than being presented as concise reference material. | 1 / 3 |
Actionability | The skill provides some concrete CSS values (specific box-shadow, backdrop-filter, transform values) and specific timing guidelines (0.3s ease-out, 0.1s stagger), but lacks any executable code examples or copy-paste ready component snippets. For a skill about building UI components, the absence of even a single React component example or GSAP animation snippet is a significant gap. | 2 / 3 |
Workflow Clarity | There is no workflow or sequenced process described. The skill reads as a collection of design principles and constraints but never explains how to actually build something step-by-step. For a skill involving complex 3D CSS and animation setup, there should be a clear sequence for constructing components with validation checkpoints (e.g., checking reduced-motion, testing performance). | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers and emoji markers, which aids scanning. However, it's a monolithic document with no references to external files for detailed examples, component libraries, or advanced patterns. The inline content could benefit from splitting detailed animation recipes or component templates into separate referenced files. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
fe8351e
- 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.