CtrlK
BlogDocsLog inGet started
Tessl Logo

vibrant

Lively, colorful design with bold playful typography, warm accents, and dynamic visual energy.

55

Quality

62%

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

Quality

Content

85%

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, lean instruction skill with concrete tokens, an explicit authoring workflow, and a QA checklist. Its main gap is the lack of a worked example showing the expected guideline output.

Suggestions

Add one concise worked example (a sample component guideline with anatomy, states, and token usage) so the 'Required Output Structure' is unambiguous and copy-paste ready.

Flesh out or remove the near-empty '## Brand' / 'Vibrant style' line, which currently adds little actionable value.

DimensionReasoningScore

Conciseness

The body is lean throughout: tight bulleted foundations, exact token values, and no padding explaining what design systems or accessibility are, matching 'lean and efficient; every token earns its place'.

3 / 3

Actionability

It provides concrete, specific guidance (exact hex tokens, typography/spacing scales, a defined state list, required output structure, QA checklist), but includes no worked example of an actual generated guideline, so it falls short of the copy-paste-ready anchor at level 3.

2 / 3

Workflow Clarity

The 'Guideline Authoring Workflow' gives a clear 6-step sequence and closes with a QA checklist (step 6) and 'Quality Gates' that act as validation checkpoints; this is a non-destructive authoring task so the absence of a validate-fix-retry loop is not penalized.

3 / 3

Progressive Disclosure

The skill is self-contained with no bundle files and is organized into clearly labeled sections; per the rubric's simple-skill guidance, well-organized sections with no need for external references score 3.

3 / 3

Total

11

/

12

Passed

Description

40%

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 an evocative but action-free aesthetic statement rather than a functional description of what the skill does or when to invoke it. It lacks any concrete capability verbs and any 'Use when' trigger guidance.

Suggestions

Rewrite the description as concrete actions in third person, e.g. 'Authors implementation-ready design-system guidelines (tokens, component states, accessibility criteria) for a lively, colorful visual style.'

Add an explicit 'Use when...' trigger clause listing natural terms users would say, such as 'Use when creating or auditing design-system guidelines, color/typography tokens, or component rules for a vibrant, playful brand.'

Replace buzzword fluff ('dynamic visual energy', 'warm accents') with concrete triggers like specific token names, color hexes, or font families that distinguish this skill from other design skills.

DimensionReasoningScore

Specificity

The description is purely an aesthetic characterization ('Lively, colorful design with bold playful typography, warm accents, and dynamic visual energy') with no concrete actions the skill performs, matching the 'no actions; abstract language' anchor.

1 / 3

Completeness

It gives a weak sense of what the skill is about (the design aesthetic) but provides no 'Use when...' or equivalent explicit trigger guidance, so per the rubric completeness is capped at 2; not level 1 because some 'what' is present, not level 3 because 'when' is entirely missing.

2 / 3

Trigger Term Quality

It includes some relevant terms a user might say ('colorful design', 'typography') but pairs them with fluff ('dynamic visual energy', 'warm accents') and lacks common trigger variations; it is closer to 'some relevant keywords but missing common variations' than to level 3.

2 / 3

Distinctiveness Conflict Risk

The phrase 'bold playful typography, warm accents' narrows the niche somewhat, but the overall design-buzzword phrasing is generic enough to overlap with other design skills, matching the 'somewhat specific but could still overlap' anchor.

2 / 3

Total

7

/

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.