CtrlK
BlogDocsLog inGet started
Tessl Logo

fantasy

Game-inspired fantasy aesthetic with bold, premium visuals, rich color palettes, and immersive thematic elements.

60

Quality

70%

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/fantasy/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 well-organized, concise, instruction-only skill with concrete directives, a clearly sequenced authoring workflow, and explicit QA/validation gates. It respects Claude's competence and earns top marks across all content dimensions.

DimensionReasoningScore

Conciseness

The body is lean and token-efficient—short bullet imperatives and concrete values with no padding or explanations of concepts Claude already knows—matching 'lean and efficient; every token earns its place'.

3 / 3

Actionability

Although it contains no executable code, it provides concrete, specific directives (explicit typography scale, hex token values, enumerated required states, 'must'/'should' constraint language) which the rubric explicitly rewards for instruction-only skills.

3 / 3

Workflow Clarity

The Guideline Authoring Workflow is a clear 6-step sequence ending in an explicit QA-checklist validation step, with testable Quality Gates criteria—matching 'clear sequence with explicit validation steps; checklists for complex processes'.

3 / 3

Progressive Disclosure

With no external bundle files needed, the content is organized into clearly labeled, well-structured sections (Mission, Style Foundations, Rules, Workflow, Quality Gates) with no nested references, meeting the simple-skill allowance for a top score.

3 / 3

Total

12

/

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 establishes a recognizable fantasy/game aesthetic niche but relies on abstract adjectives instead of concrete actions and omits any explicit use-when trigger guidance. It is acceptable but vague and would benefit from naming deliverables and trigger conditions.

Suggestions

Replace abstract adjectives with concrete actions, e.g. 'Generates and applies fantasy/game-themed design-system tokens, component rules, and accessibility guidance.'

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks for game-inspired, fantasy, RPG, or medieval visual styles or design-system guidance.'

Tighten distinctiveness by stating the specific deliverable (design-system guidelines) so it does not overlap with generic brand-skin skills.

DimensionReasoningScore

Specificity

The description uses only abstract aesthetic adjectives ('bold, premium visuals', 'rich color palettes', 'immersive thematic elements') and names no concrete actions or deliverables, matching the 'vague or no actions; abstract language' anchor.

1 / 3

Completeness

It states a 'what' (fantasy aesthetic styling) but provides no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 2 with the 'when' missing/implied.

2 / 3

Trigger Term Quality

It includes relevant keywords like 'fantasy' and 'game-inspired', but these are descriptive rather than natural user triggers and it misses common variations (RPG, medieval, lore), fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The fantasy/game niche is somewhat specific, but the surrounding descriptors ('bold, premium visuals', 'rich color palettes') are generic design-system language that overlaps with many aesthetic/brand skills, fitting 'somewhat specific but could still overlap'.

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.