CtrlK
BlogDocsLog inGet started
Tessl Logo

high-end-visual-design

Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.

58

Quality

66%

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 ./plugins/community/agent-skill-principal-ui-ux-architect-motion-choreographer-awwwards-tier-mqu4mbbj/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 an impressively concrete, directive guide with copy-paste Tailwind classes, a clear execution sequence, and a pre-output validation checklist. It loses points mainly for lacking an explicit fix-retry feedback loop and for the persona flourishes that add mild verbosity.

Suggestions

Add an explicit 'if the checklist fails, fix and re-verify before output' feedback loop in Section 8 to lift workflow clarity.

Trim theatrical persona phrases ('obsessive micro-interactions', 'cinematic spatial rhythm') to tighten conciseness without losing the design intent.

If deeper material exists (e.g. full component markup), move it into a one-level-deep references file and link it from the relevant section to formalize progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and directive with concrete Tailwind classes throughout, assuming Claude's competence; the main padding is the slightly theatrical persona language ('haptic depth', 'cinematic spatial rhythm') that could be trimmed, but it is largely earned signal.

4 / 5

Actionability

It provides highly concrete, copy-paste-ready Tailwind/CSS snippets (e.g. rounded-[2rem], ring-1 ring-black/5, ease-[cubic-bezier(0.32,0.72,0,1)]) and named libraries (Phosphor Light, Framer Motion), with only minor gaps such as omitted full component markup.

4 / 5

Workflow Clarity

Section 7 gives a clear 5-step execution sequence and Section 8 provides a pre-output checklist acting as a validation checkpoint, but there is no explicit feedback/fix-retry loop for when the checklist fails, so it stops just short of 5.

4 / 5

Progressive Disclosure

Content is well-organized into clearly labeled numbered sections with no nested reference chains; the only bundle file (references/) is a provenance/source copy rather than navigable detail material, so structure is strong but there is no deliberate one-level-deep reference pattern to reach 5.

4 / 5

Total

16

/

20

Passed

Description

58%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 specific and distinctive about high-end visual design, but omits any explicit trigger ('Use when...') guidance, which caps completeness. Trigger-term coverage is also only moderate because the natural phrases a user would say are largely absent.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when building marketing sites, landing pages, or portfolios that need an agency-tier aesthetic.'

Incorporate natural trigger terms users actually say (landing page, UI design, redesign, portfolio, hero section) alongside 'website' and 'design'.

Keep the concrete design facets but consider framing at least one as a concrete action verb pair to lift specificity toward 5.

DimensionReasoningScore

Specificity

Names concrete design specifics (fonts, spacing, shadows, card structures, animations) rather than vague actions, but lists design facets rather than discrete executable actions, leaving minor coverage gaps.

4 / 5

Completeness

It clearly states what the skill does (defines fonts, spacing, shadows, structures, animations and blocks cheap defaults) but has no explicit 'Use when...' clause telling Claude when to invoke it, capping completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

It contains domain keywords ('high-end agency', 'expensive', 'website', 'design') but lacks the natural phrases and synonyms a user would actually say (e.g. 'landing page', 'UI design', 'portfolio', 'redesign').

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct (premium/agency-tier visual design with explicit anti-pattern blocking) and unlikely to fire for unrelated skills, though it could overlap with other general web-design skills.

4 / 5

Total

14

/

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
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.