CtrlK
BlogDocsLog inGet started
Tessl Logo

neon

Electric neon glow effects with high-contrast color pairings for bold, attention-grabbing interfaces.

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/neon/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 design-system guideline with concrete tokens, explicit rules, a sequenced authoring workflow, and validation checkpoints. It is self-contained with no bundle files, and its organization supports the top anchors across all dimensions.

DimensionReasoningScore

Conciseness

The body is lean and token-efficient — concise bullet lists, token tables, and rule lists with no padding or explanation of concepts Claude already knows; every line earns its place.

3 / 3

Actionability

Concrete tokens (hex values, type/spacing scales, weights), explicit do/don't lists, a required output structure, and constraint language ('must'/'should', 'pair every do-rule with a don't-example') give specific, executable guidance; as an instruction-only skill, the absence of code is not penalized.

3 / 3

Workflow Clarity

A clear sequenced 6-step 'Guideline Authoring Workflow' is backed by 'Quality Gates' and a QA checklist that act as validation checkpoints; not a destructive/batch context, so the cap does not apply.

3 / 3

Progressive Disclosure

No bundle directories (references/scripts/assets) exist, so the skill is a self-contained overview with well-organized sections and no nested references; per scoring_notes, well-organized single-file skills with no external refs score 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 identifies a clear design niche but stops short of listing concrete actions or explicit usage triggers, leaving it at the mid-level across all dimensions. Adding a 'Use when...' clause and naming specific capabilities would lift it toward the top anchors.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when building bold, high-contrast neon-style interfaces or when the user mentions glow effects, neon UI, or vibrant color pairings.'

Replace modifier phrases with concrete actions, e.g. 'Generate neon glow effects and apply high-contrast color pairings to components.'

Include common user-facing variations of the trigger terms ('glow', 'neon UI', 'vibrant colors') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('neon glow effects', 'high-contrast color pairings') and modifiers ('bold, attention-grabbing interfaces') but lists no concrete actions or capabilities; matches 'Names domain and some actions, but not comprehensive' rather than the multi-action score 3.

2 / 3

Completeness

It states what the skill does (neon glow effects) but lacks any 'Use when...' or equivalent trigger for when to use it; per the judging guidelines a missing trigger caps completeness at 2.

2 / 3

Trigger Term Quality

'neon glow effects' and 'high-contrast color pairings' are reasonable natural terms, but common variations a user might say ('glow', 'neon UI', 'vibrant colors') are missing, matching 'Some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

'neon' and 'high-contrast' give it a niche, but 'bold, attention-grabbing interfaces' is generic enough to overlap with general styling/design skills, matching 'Somewhat specific but could still overlap'.

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.