antigravity-design-expert

Core UI/UX engineering skill for building highly interactive, spatial, weightless, and glassmorphism-based web interfaces using GSAP and 3D CSS.

1.21x

Quality

59%

Does it follow best practices?

Impact

86%

1.21x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-design-expert/SKILL.md

Quality

Content

57%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 a well-organized, self-contained set of concrete design and motion rules with specific CSS values, and needs no external bundle files. Its weaknesses are the absence of any executable code example (despite GSAP/React being the named stack), the padded Role Overview and empty Example sections, and the lack of a sequenced workflow with validation checkpoints.

Suggestions

Replace the Example section's bare user request with a complete, copy-paste-ready snippet — e.g., a minimal glassmorphism card with a GSAP ScrollTrigger entrance and the reduced-motion guard — since GSAP is the named animation stack but no GSAP code appears anywhere.

Cut the Role Overview role-play sentence and tighten adjective-heavy lines ('buttery-smooth', 'world-class') to improve token efficiency.

Add a short sequenced build workflow with checkpoints, e.g.: 1) scaffold component, 2) apply spatial/glass styling, 3) add staggered GSAP entrance, 4) verify prefers-reduced-motion fallback and no continuous box-shadow/filter animation.

Dimension	Reasoning	Score
Conciseness	Most sections are dense, concrete rules (specific box-shadow, blur, and transform values), but "You are a world-class UI/UX Engineer specializing in 'Antigravity Design'" is role-play padding and the Example section quotes a user request with no output, matching anchor 3's 'some unnecessary explanation or could be tightened' rather than anchor 4's minor trimming.	3 / 5
Actionability	Concrete inline values exist ("backdrop-filter: blur(12px)", "rotateX(60deg) rotateZ(-45deg)", stagger "0.1s", "prefers-reduced-motion: reduce", "will-change: transform"), but there is no complete executable code anywhere — the Example section contains only a user request with no GSAP/React output — matching anchor 3's 'missing key details' rather than anchor 4's mostly-executable guidance.	3 / 5
Workflow Clarity	Content is organized by topic (tech stack, design principles, motion rules, constraints) rather than as a sequenced build workflow, and there are no validation checkpoints (e.g., verifying reduced-motion behavior or animation performance), matching anchor 3's 'sequence present but checkpoints missing or implicit' — it is not incoherent like anchor 2, but it falls short of the explicit steps and verification of anchor 4.	3 / 5
Progressive Disclosure	The body is ~50 lines with no bundle files provided and no content that warrants splitting out; sections are clearly headed and scannable ('## Preferred Tech Stack', '## Design Principles', '## Motion & Animation Rules'), which per the simple-skill guideline earns a 5 for well-organized self-contained structure.	5 / 5
	Total	14 / 20 Passed

Description

61%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 identifies a concrete, fairly distinct niche with specific technologies (GSAP, 3D CSS, glassmorphism), but it reads as a domain label rather than a capability list and completely lacks a 'Use when...' trigger clause, which caps completeness. Adding explicit trigger guidance and enumerating the concrete actions (isometric dashboards, floating glass cards, scroll-linked animation) would raise it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for glassmorphism, spatial/3D UI, floating cards, isometric dashboards, GSAP or scroll-driven motion, or immersive landing pages.'

Enumerate 3-4 concrete capabilities instead of adjectives — e.g. 'Build glassmorphism cards, isometric tilted grids, staggered card entrances, and parallax scroll effects using GSAP, ScrollTrigger, and 3D CSS transforms.'

Trim buzzword padding ('highly interactive, spatial, weightless') in favor of natural trigger terms users would actually say (animation, motion, 3D website, landing page).

Dimension	Reasoning	Score
Specificity	The description names the domain and one action verb ("building highly interactive, spatial, weightless, and glassmorphism-based web interfaces using GSAP and 3D CSS") with concrete technologies, but does not enumerate the specific actions it covers (isometric grids, floating elements, scroll-linked animations), matching anchor 3 rather than anchor 4's 'several specific actions'.	3 / 5
Completeness	The description gives a clear 'what' ("Core UI/UX engineering skill for building... web interfaces") but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	"glassmorphism", "GSAP", "3D CSS", and "web interfaces" are terms a user would naturally say when they need this skill, giving good keyword coverage; natural variations like "animation", "motion", "landing page", or "parallax" are missing, so it is not the comprehensive synonym coverage of anchor 5.	4 / 5
Distinctiveness Conflict Risk	"glassmorphism-based web interfaces using GSAP and 3D CSS" carves out a mostly distinct niche with specific technologies, though "highly interactive" web interfaces leaves minor overlap risk with general frontend/UI skills, matching anchor 4 rather than the minimal-conflict clarity of anchor 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/antigravity-design-expert/SKILL.md
Commit: c26b706

Reviewed: 1 hour 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.