CtrlK
BlogDocsLog inGet started
Tessl Logo

gpt-taste

Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/gpt-tasteskill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill shines on workflow clarity thanks to its mandatory pre-flight design_plan checklist, but it is held back by padded rhetoric, GSAP motion given as description rather than executable code, and a monolithic structure with no file-based progressive disclosure.

Suggestions

Provide a minimal executable GSAP/ScrollTrigger code skeleton (e.g. a `useGSAP` hook with a pinning + scrub setup) instead of prose-only motion directions.

Move the component arsenal (Section 6) and GSAP paradigms (Section 5) into `references/` files referenced one level deep, keeping SKILL.md a concise overview.

Trim emphatic filler ('catastrophic failure', 'BANNED FOREVER', repeated 'MUST/NEVER') to reduce tokens without losing the rules.

DimensionReasoningScore

Conciseness

The body gives domain-specific rules rather than re-explaining basics Claude knows, but it is padded with emphatic rhetoric ('catastrophic failure', 'BANNED FOREVER', 'strictly forbidden') and meta-commentary on LLM laziness that could be tightened.

2 / 3

Actionability

Concrete Tailwind classes (`grid-flow-dense`, `max-w-6xl`, `clamp(3rem, 5vw, 5.5rem)`) and one full JSX inline-image snippet are present, but the GSAP motion guidance ('Pin a section title... ScrollTrigger pin: true') is described rather than given as executable code, leaving it short of copy-paste ready.

2 / 3

Workflow Clarity

Section 8 mandates a clear pre-flight sequence — RNG execution, AIDA check, hero-math verification, bento-density verification, label sweep — with explicit validation checkpoints before any UI code is emitted.

3 / 3

Progressive Disclosure

No bundle files exist and the ~100-line body is monolithic; internal numbered sections are well organized, but content like the component arsenal and GSAP paradigms could be split into referenced files rather than living inline.

2 / 3

Total

9

/

12

Passed

Description

67%

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 specific and occupies a distinct niche, but it omits any explicit 'when to use' trigger guidance, leaving completeness and trigger-term quality at the middle level. Adding a natural 'Use when...' clause would lift the weaker dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for a premium, high-variance landing page, GSAP/scroll-motion UI, or award-level frontend design'.

Surface the natural trigger terms already in the `triggers` field (e.g. 'gpt taste', 'gsap motion landing', 'premium codex UI') within the description so users' phrasing matches.

Trim the opening role-fluff 'Elite UX/UI & Advanced GSAP Motion Engineer.' to keep the lead focused on concrete capabilities.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Python-driven true randomization for layout variance', 'strict AIDA page structure', 'gapless bento grids', 'GSAP ScrollTriggers (pinning, stacking, scrubbing)', 'inline micro-images' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

It clearly answers 'what' the skill does, but 'when' to use it is entirely missing — there is no explicit trigger guidance, which caps completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Contains some relevant keywords ('UX/UI', 'GSAP', 'landing page', 'bento grids') but no natural 'Use when...' phrasing and is missing common variations a user would actually say, so it stops at the partial-coverage anchor.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — award-level GSAP motion landing pages with AIDA structure and bento grids — using distinctive vocabulary that is unlikely to fire for unrelated skills.

3 / 3

Total

10

/

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
nexu-io/open-design
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.