CtrlK
BlogDocsLog inGet started
Tessl Logo

antigravity-design-expert

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

72

1.50x
Quality

61%

Does it follow best practices?

Impact

92%

1.50x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

72%

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, concrete design-spec skill with copy-ready CSS values and clear rules, requiring no external bundle files. Its main gaps are mild marketing padding and the absence of any sequenced workflow or validation checkpoints.

Suggestions

Trim flavor language ('world-class', 'buttery-smooth', 'premium feel') to improve token efficiency.

If multi-step builds are expected, add a short ordered build/validate workflow (e.g., scaffold components -> apply transforms -> verify prefers-reduced-motion -> performance check) with explicit checkpoints.

Consider one minimal executable component example (e.g., a R3F or GSAP ScrollTrigger snippet) to lift actionability from spec-guidance to fully copy-paste-ready.

DimensionReasoningScore

Conciseness

It is mostly efficient with concrete spec values rather than explaining concepts Claude knows, but retains marketing flavor ('world-class UI/UX Engineer', 'buttery-smooth', 'premium feel') that could be trimmed, so it sits at mostly-efficient rather than fully lean.

2 / 3

Actionability

For an instruction-only design skill it provides concrete, specific, actionable guidance — exact CSS values ('box-shadow: 0 20px 40px rgba(0,0,0,0.05)', 'backdrop-filter: blur(12px)'), transforms ('rotateX(60deg) rotateZ(-45deg)'), and timings ('0.3s ease-out', '0.1s' stagger) — so the absence of a full code block is not penalized per the scoring notes.

3 / 3

Workflow Clarity

The body is organized into clear sections (When to Use, Tech Stack, Principles, Motion Rules, Constraints) but it is a collection of design rules rather than a sequenced multi-step process, and there are no explicit validation checkpoints; there is no destructive/batch operation that would require feedback loops.

2 / 3

Progressive Disclosure

The skill is under 50 lines of content, requires no external references, and is well-organized into clearly headed sections; per the guidelines a sub-50-line self-contained skill with good organization can score 3 on progressive disclosure without bundle files.

3 / 3

Total

10

/

12

Passed

Description

50%

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 states a clear domain and the core tech (GSAP, 3D CSS, glassmorphism) but leans on buzzwordy adjectives and omits any explicit 'Use when' trigger guidance. It answers 'what' well but leaves 'when' only implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building interactive, glassmorphism or 3D/parallax-heavy web UIs with GSAP or React Three Fiber.'

Replace abstract adjectives ('spatial', 'weightless') with concrete capability verbs (e.g., 'tilt dashboards into isometric perspective, build scroll-linked parallax animations').

Include natural user phrasings like 'glassmorphism dashboard', 'GSAP scroll animation', or '3D landing page' to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

It names a concrete domain and actions ('building highly interactive, spatial, weightless, and glassmorphism-based web interfaces using GSAP and 3D CSS') but describes a single building action with adjectives rather than listing multiple distinct concrete actions like the score-3 anchor.

2 / 3

Completeness

It clearly states what the skill does ('building highly interactive... web interfaces'), but the 'when' is only implied and there is no explicit 'Use when...' clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

It includes some relevant natural keywords users would say ('glassmorphism', 'GSAP', '3D CSS'), but mixes in buzzwordy terms ('spatial', 'weightless') and lacks common variations or an explicit 'Use when' trigger phrase, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The GSAP/3D-CSS/glassmorphism combination carves a niche, but the broad 'UI/UX engineering skill for building web interfaces' framing and the absence of explicit triggers mean it could still overlap with general web UI/design skills.

2 / 3

Total

8

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/antigravity-awesome-skills
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.