CtrlK
BlogDocsLog inGet started
Tessl Logo

contemporary

Current-era minimalist design with bento grids, dark mode support, and high-performance accessible layouts.

53

Quality

60%

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

Quality

Content

70%

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-structured, reasonably concise instruction-only skill with a clear sequenced authoring workflow and a QA checklist. Its main gaps are minor cross-section redundancy and the absence of a worked example showing the expected generated output.

Suggestions

Consolidate the overlapping guidance in "Rules: Do/Don't", "Quality Gates", and "Example Constraint Language" into a single ruleset to remove redundancy.

Add one short worked example of a generated component guideline (anatomy, states, tokens, accessibility acceptance criteria) to demonstrate the required output structure.

Keep the concrete tokens and acceptance criteria as-is; they are the strongest actionable elements and should anchor any consolidation.

DimensionReasoningScore

Conciseness

The body is mostly lean bullet-point guidance that assumes Claude's competence and does not explain known concepts, but there is notable redundancy across "Rules: Do/Don't", "Quality Gates", and "Example Constraint Language" that could be tightened.

2 / 3

Actionability

Concrete guidance is present (specific tokens like #C800DF, required states, a required output structure, WCAG 2.2 AA, 44px touch targets), but there is no worked example of actual generated output, which would make the guidance fully copy-paste ready.

2 / 3

Workflow Clarity

The "Guideline Authoring Workflow" is a clear six-step numbered sequence that ends with an explicit QA checklist acting as a verification step, matching the clear-sequence-with-checklist anchor.

3 / 3

Progressive Disclosure

The skill is a single self-contained file with well-organized, clearly headed sections and no nested references; with no external references needed it earns the top anchor for well-organized structure.

3 / 3

Total

10

/

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 a concise style descriptor with some concrete feature nouns, but it lacks explicit actions and any when-to-use trigger clause. It reads as a brand tagline rather than activation guidance.

Suggestions

Reframe the description around concrete actions the skill performs (e.g., "Authors contemporary design-system guidelines with bento grids, dark mode, and accessible layouts.").

Add an explicit trigger clause such as "Use when creating or updating modern minimalist design-system guidelines, especially for bento-grid layouts or dark-mode support."

Drop filler phrasing like "Current-era" and "high-performance" in favor of natural terms a user would actually say.

DimensionReasoningScore

Specificity

Names the design domain and concrete features ("bento grids", "dark mode support", "accessible layouts") but describes attributes rather than listing concrete actions the skill performs, so it falls short of the multi-action anchor.

2 / 3

Completeness

It conveys a what (a contemporary design style) but provides no "Use when..." clause or equivalent trigger guidance, so per the guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Some natural terms users would say ("minimalist design", "bento grids", "dark mode") appear, but they are mixed with non-user phrasing ("Current-era", "high-performance accessible layouts") and common variations are missing.

2 / 3

Distinctiveness Conflict Risk

The contemporary-design niche is somewhat specific (bento grids, dark mode) but the description could still overlap with other general design skills, so it is not a fully distinct trigger set.

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.