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.

57

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

66%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 skill body is well-structured, actionable, and includes a strong pre-flight workflow with verification checkpoints. It is held back by occasional verbose editorializing and the lack of progressive file-based disclosure for a skill this detailed.

Suggestions

Trim editorial padding (e.g., "LLMs are inherently lazy", "catastrophic failure", "BANNED FOREVER") in favor of terse directives that assume Claude's competence.

Move the detailed component arsenal and GSAP paradigm catalog into a referenced reference file (e.g., ARSENAL.md) to improve progressive disclosure and reduce base context weight.

Add an explicit error-recovery feedback loop in the pre-flight section (e.g., 'if bento density check fails, adjust col-span/row-span and re-verify') to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient and directive, but includes padding and editorializing ("LLMs are inherently lazy", "catastrophic failure", "BANNED FOREVER") that could be tightened to assume Claude's competence.

3 / 5

Actionability

Provides concrete, executable guidance such as specific Tailwind classes (`grid-flow-dense`, `max-w-5xl`), GSAP API references, and a copy-paste-ready inline-image span, with only minor gaps (e.g., the Python RNG is simulated rather than a runnable script).

4 / 5

Workflow Clarity

The mandatory <design_plan> pre-flight section sequences a clear multi-step process with explicit verification checkpoints (Hero Math Verification, Bento Density Verification, Label Sweep), with minor gaps since there is no error-recovery feedback loop.

4 / 5

Progressive Disclosure

Content is well-organized into eight clearly headed sections with a self-contained overview structure and no nested external references, though some sections (e.g., the component arsenal) could be split into reference files for a skill of this length.

4 / 5

Total

15

/

20

Passed

Description

65%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 is highly specific about capabilities but lacks an explicit 'Use when...' trigger clause, capping completeness at 3. Trigger terms lean toward technical jargon over natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke the skill, e.g., 'Use when building award-level marketing landing pages, hero sections, or animated UI with GSAP'.

Include natural user-facing trigger phrases and synonyms (e.g., 'landing page', 'hero section', 'scroll animation', 'web animation') alongside the technical jargon.

Consider trimming the lengthy enumeration of enforced rules into a tighter capability summary to improve scannability.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("Enforces Python-driven true randomization", "strict AIDA page structure", "gapless bento grids", "strict GSAP ScrollTriggers") with comprehensive coverage of what the skill enforces.

5 / 5

Completeness

The 'what' is clearly and richly described, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Terms like "GSAP", "bento grids", "ScrollTriggers", and "AIDA" are domain jargon rather than the natural phrases a user would say when needing this skill, and common synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

The niche (award-level UX/UI with GSAP motion) is mostly distinct with minor overlap risk against general frontend/design skills, anchored by specific triggers like GSAP ScrollTriggers and bento grids.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Leonxlnx/taste-skill
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.