CtrlK
BlogDocsLog inGet started
Tessl Logo

vintage

1950s-1990s nostalgia with skeuomorphic touches, grainy textures, retro color palettes, and pixel-style typography.

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/vintage/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 content is a tight, well-organized authoring framework with concrete tokens, an explicit state taxonomy, a sequenced workflow, and a terminal QA checkpoint — it assumes Claude's competence and provides actionable, implementation-focused guidance without padding.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with short declarative directives, and it does not over-explain concepts Claude already knows; a few general process lines are part of the skill's guidance rather than padding, so most tokens earn their place.

3 / 3

Actionability

Guidance is concrete and executable: exact typography/spacing scales, named fonts, hex color tokens, an enumerated required-states list, a 6-step authoring workflow, and a defined output structure — specific directives an author can follow directly.

3 / 3

Workflow Clarity

The Guideline Authoring Workflow is a clearly sequenced 6-step process that ends in an executable QA checklist, and Quality Gates add testable acceptance criteria, giving a clear sequence with an explicit validation checkpoint for this non-destructive single task.

3 / 3

Progressive Disclosure

It is a self-contained, single-file skill with no bundle files and no nested references; content is appropriately kept inline and organized into well-labeled sections, which matches the rubric's allowance for simple skills scoring 3 on well-organized structure alone.

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 vividly characterizes the Vintage aesthetic domain but reads as a style identity rather than a skill-capability statement: it names no actions and provides no 'Use when' trigger, leaving both the skill's function and invocation context implicit.

Suggestions

Lead with an action verb describing what the skill does (e.g. 'Authors implementation-ready Vintage design-system guidelines...') so capabilities are explicit rather than implied.

Add a 'Use when...' clause naming natural triggers a user would say ('retro UI', 'vintage/90s redesign', 'pixel-art style guide') to fully answer when Claude should invoke it.

Include capability breadth (e.g. defining tokens, component anatomy, accessibility acceptance criteria) to lift specificity beyond the aesthetic description.

DimensionReasoningScore

Specificity

The description lists concrete aesthetic domain elements ('skeuomorphic touches, grainy textures, retro color palettes, and pixel-style typography' over '1950s-1990s') but states no capability verbs — what the skill actually does is unstated, so it names the domain with some specificity without being comprehensive about actions.

2 / 3

Completeness

It conveys a partial 'what' (the visual aesthetic) but omits what the skill does and has no 'Use when...' or equivalent when-trigger, so per the rubric a missing explicit trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

Natural terms like 'nostalgia', 'retro', and 'vintage' (in the name) appear, but common variations a user might say ('pixel art', '8-bit', 'old-school', '90s UI') are missing, so coverage is partial rather than complete.

2 / 3

Distinctiveness Conflict Risk

The vintage/retro aesthetic is a recognizable niche, but it could still overlap with sibling design-style skills (e.g. a generic 'retro' or 'pixel art' skill), so it is somewhat specific rather than clearly conflict-free.

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.