CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

design-styles

Comprehensive reference for 50 design aesthetics, movements, and visual styles with detailed definitions. Use when creating visuals, illustrations, graphics, or any design work requiring specific aesthetic direction. Each style includes core principles, visual characteristics, color palettes, typography guidance, key elements, emotional qualities, historical context, and AI prompt engineering keywords.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured reference skill body: the index table, prompt formula, and example prompts make it immediately actionable, and references are clearly signaled one level deep. The main deductions are duplicated navigational content (Reference Files section vs. index table), a version-history section of limited runtime value, and referenced bundle files that could not be verified in the provided directory.

Suggestions

Remove the duplication between the 'Complete Style Index' table and the 'Reference Files' section — keep the index table's Reference File column as the single source of truth and retain only the one-line file descriptions (or fold them into the table's category grouping).

Drop or drastically shorten the 'Version History' section — it is time-sensitive metadata of no use at runtime and duplicates the frontmatter's version field.

Ship (or verify) the five references/*.md files in the bundle — the entire workflow depends on 'Read the detailed entry in the corresponding reference file', and they were absent from the evaluated directory.

DimensionReasoningScore

Conciseness

The body is table-dense with no explanation of concepts Claude already knows and no padded prose, but contains trimmable redundancy: the 'Reference Files' section re-lists the style-to-file mapping already fully specified by the index table, and the opening bullet list duplicates the frontmatter description. Efficient with minor instances that could be trimmed — score 4, not 3 (no fluffy prose) and not 5 (genuine duplicated sections exist).

4 / 5

Actionability

Guidance is fully executable: a numbered 5-step workflow (identify mood → find matching styles in the index → read the entry → apply characteristics → use prompt keywords), an explicit prompt-composition formula ([Subject] + [Style keywords from entry] + [Color palette terms] + [Additional modifiers]), and five copy-paste-ready example prompts covering common cases. This matches the score-5 anchor (copy-paste ready, specific examples cover the common cases).

5 / 5

Workflow Clarity

The 'How to Use This Skill' section gives a clear, correctly sequenced lookup workflow, and no validation checkpoints are needed for this read-only reference use. It falls short of 5 because handling a request that spans or blends multiple styles is left implicit beyond the static combinations table, and the two use-case paths (visual design vs. AI image generation) are not cross-linked. Clear sequence with minor gaps — score 4.

4 / 5

Progressive Disclosure

Structure and signaling are excellent: a complete 50-style index mapping every style to one of five reference files, one level deep, with clear markdown links and per-file descriptions — this alone would merit 5. However, the five referenced files (references/classic-movements.md, retro-futurism.md, typography-print.md, digital-cyber.md, pop-culture.md) are not present in the evaluated bundle, so the referenced paths cannot be verified as real files, holding this at 4.

4 / 5

Total

17

/

20

Passed

Description

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

A strong description that explicitly states both what the skill provides and when to use it, with a thorough enumeration of per-style contents. Trigger terms are good but miss common user phrasings (specific style names, 'art style', 'theme'), and the broad 'any design work' trigger slightly raises conflict risk with adjacent design skills.

DimensionReasoningScore

Specificity

The description comprehensively enumerates the concrete contents of each entry — "core principles, visual characteristics, color palettes, typography guidance, key elements, emotional qualities, historical context, and AI prompt engineering keywords" — matching the score-5 anchor (multiple specific concrete items, comprehensive coverage). Score 4's 'minor gaps in coverage' does not fit since nothing in the skill's per-style schema is omitted.

5 / 5

Completeness

Both questions are explicitly answered: what ("Comprehensive reference for 50 design aesthetics, movements, and visual styles with detailed definitions") and when ("Use when creating visuals, illustrations, graphics, or any design work requiring specific aesthetic direction") with concrete trigger phrases. This matches the score-5 anchor; it is not 4 because the 'when' clause is explicit and specific rather than vague.

5 / 5

Trigger Term Quality

Natural triggers are present ("creating visuals, illustrations, graphics, or any design work requiring specific aesthetic direction") plus "design aesthetics", "movements", and "visual styles". Common variations users actually say are missing: specific style names (e.g., Bauhaus, Art Deco, cyberpunk), "art style", "theme", or "vibe" — a few natural terms missing, matching the score-4 anchor rather than the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

The aesthetic-style-reference niche is clear and mostly distinct, but the trigger phrase "any design work requiring specific aesthetic direction" is broad and could overlap with closely related skills (brand guidelines, design systems, dataviz styling) — minor overlap risk, matching the score-4 anchor rather than the minimal-conflict profile of 5.

4 / 5

Total

18

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 5 missing

Warning

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

13

/

16

Passed

Repository

tesslio/design-styles

Path

SKILL.md

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.