CtrlK
BlogDocsLog inGet started
Tessl Logo

artistic

High-contrast, expressive style with creative typography and bold color choices for visually striking interfaces.

49

Quality

53%

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

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and lean with concrete tokens, scales, and enumerated states, but it lacks a worked example and leaves validation as an implicit gate rather than an in-workflow checkpoint. Adding one concrete authored-guideline example and an explicit validate-fix-retry step would raise the weaker dimensions.

Suggestions

Add one concrete worked example of an authored component guideline showing the required output structure end-to-end.

Wire a 'validate each rule anchors to a token, then fix and re-check' checkpoint explicitly into the authoring workflow rather than leaving it as a separate Quality Gates section.

Consolidate the overlapping Guideline Authoring Workflow, Required Output Structure, and Component Rule Expectations sections to remove redundancy.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no known-concept padding, but the Guideline Authoring Workflow, Required Output Structure, and Component Rule Expectations sections overlap enough that the content could be tightened by consolidation.

2 / 3

Actionability

It provides concrete scaffolding (typography scale, hex color tokens, spacing scale, enumerated component states, 'must'/'should' language), but provides no concrete worked example of an authored guideline or a paired do/don't example despite asking for them.

2 / 3

Workflow Clarity

A clear 6-step numbered authoring workflow with a QA checklist step is present, but validation checkpoints are implicit (Quality Gates live in a separate section) and are not wired into the workflow as an explicit validate-fix-retry loop.

2 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single self-contained file is well-organized into clear headed sections, satisfying the simple-skill note that well-organized sections score 3 without external references.

3 / 3

Total

9

/

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 is specific about the visual aesthetic but contains no actions and no 'Use when' trigger guidance, which caps both completeness and distinctiveness. Adding explicit trigger conditions and one or two concrete actions would lift it into the top tier.

Suggestions

Add a 'Use when...' clause naming natural trigger terms users would say (e.g., 'Use when creating artistic, high-contrast UI themes or bold visual styling').

Include concrete actions the skill performs (e.g., 'applies bold color tokens and creative typography scales to generate striking interface guidelines').

Add natural trigger keywords like 'artistic', 'theme', 'styling', or 'design system' so the skill is distinguishable from generic brand-skills.

DimensionReasoningScore

Specificity

The description names the domain concretely with specific qualities ('high-contrast, expressive style', 'creative typography', 'bold color choices') but lists no concrete actions, fitting 'names domain and some actions' rather than the vague score-1 anchor or the multi-action score-3 anchor.

2 / 3

Completeness

It clearly answers 'what' (a high-contrast expressive style) but provides no 'Use when...' trigger clause; per the guideline a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like 'high-contrast', 'creative typography', and 'bold color choices' are recognizable, but natural trigger words a user would say ('artistic', 'styling', 'theme') are missing, so coverage has relevant keywords but lacks common variations.

2 / 3

Distinctiveness Conflict Risk

The aesthetic niche is fairly specific but lacks distinct trigger terms, so it could still overlap with general design or brand-styling skills.

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.