CtrlK
BlogDocsLog inGet started
Tessl Logo

premium

Apple-inspired premium aesthetic with precise spacing, modern typography, and a refined, polished visual language.

63

Quality

75%

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/premium/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 tight, well-structured instruction skill: concrete token values, explicit rules, a sequenced authoring workflow, and validation-oriented quality gates with no wasted tokens. It is highly actionable and well-organized for a single-file skill.

DimensionReasoningScore

Conciseness

The body is lean and directive with no explanation of concepts Claude already knows and no padding; every line (token tables, rules, output structure) earns its place, matching the score-3 anchor.

3 / 3

Actionability

As an instruction-only skill it provides concrete, executable guidance: exact token values, an enumerated required-states list, a fixed output structure, and a must/should constraint vocabulary; per scoring notes the absence of code is not penalized when guidance is this actionable.

3 / 3

Workflow Clarity

The six-step "Guideline Authoring Workflow" is a clear, ordered sequence, and the "Quality Gates" plus mandated QA checklist serve as explicit validation checkpoints; the operation is authoring rather than destructive/batch, so no feedback-loop cap applies.

3 / 3

Progressive Disclosure

It is a single, well-organized file under ~80 lines with no need for external references, and section headers (Mission, Foundations, Workflow, Output Structure, Quality Gates) provide clear navigation, satisfying the simple-skill allowance for a score of 3.

3 / 3

Total

12

/

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 conveys a clear, specific aesthetic identity but omits any trigger guidance and states no concrete actions, leaving the "when" half of completeness unanswered. It reads as a style statement rather than a capability-and-trigger description.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. "Use when applying an Apple-inspired premium look to UI, design tokens, or component guidance."

Replace passive adjectives ("refined, polished visual language") with concrete actions the skill performs, such as "Defines premium typography, spacing, and color tokens and authors component guidelines."

Include natural user-facing keywords ("Apple design", "premium UI", "design system", "component styling") to improve trigger term coverage.

DimensionReasoningScore

Specificity

It names a concrete domain ("Apple-inspired premium aesthetic") and specific qualities ("precise spacing", "modern typography"), but states no concrete actions/capabilities the skill performs, so it sits above the vague score-1 anchor yet below the multi-action score-3 anchor.

2 / 3

Completeness

It answers "what" the skill provides (a premium aesthetic/style) but never states "when" Claude should use it; per the guidelines a missing "Use when..." clause caps completeness at 2.

2 / 3

Trigger Term Quality

It includes some natural terms a user might say ("Apple-inspired", "premium aesthetic", "typography", "spacing") but offers only partial coverage and misses common variations and a "Use when..." phrasing, matching the score-2 anchor.

2 / 3

Distinctiveness Conflict Risk

The "Apple-inspired premium aesthetic" niche is fairly specific among design-style skills, but without explicit trigger guidance it could still overlap with sibling aesthetic skills, fitting the score-2 anchor.

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
bergside/awesome-design-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.