CtrlK
BlogDocsLog inGet started
Tessl Logo

tetris

Classic block-game inspired design with playful colors, bold display fonts, and compact, high-energy layouts.

58

Quality

67%

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

Quality

Content

85%

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 tight, well-structured instruction-only skill with concrete tokens, an explicit workflow, and a QA checkpoint. Its main gap is the absence of worked component examples to make guidance fully copy-paste ready.

Suggestions

Add one or two worked component-rule examples (e.g., a sample button anatomy with default/hover/focus-visible/active states mapped to tokens) to lift actionability toward anchor 3.

Trim the exhaustive font-weight enumeration ("100, 200, ... 900") to the weights actually used, removing token-cost padding.

Consider moving the full token table and component-state matrix into a references file so SKILL.md stays a lean overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

The body is lean, list-driven, and assumes competence with no concept-explanation filler; the only minor wart (enumerated font weights) is data rather than prose padding, fitting anchor 3.

3 / 3

Actionability

Concrete guidance exists (hex tokens, named fonts, explicit state list, 6-step workflow, required output structure) but no worked examples or copy-paste-ready samples, fitting anchor 2's "concrete but incomplete" rather than anchor 3.

2 / 3

Workflow Clarity

A clear 6-step Guideline Authoring Workflow with explicit sequencing and a QA checklist / Quality Gates checkpoint; guidance authoring is not a fragile batch/destructive operation requiring a validate-retry loop, matching anchor 3.

3 / 3

Progressive Disclosure

Single self-contained file (~75 lines) with no bundle files and clean, well-labeled sections; no nested references or monolithic wall, so well-organized sections satisfy anchor 3 for a no-bundle skill.

3 / 3

Total

11

/

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 conveys a recognizable visual niche but reads as a style statement rather than a capability/trigger description. It lacks an explicit "Use when..." clause and natural trigger keywords.

Suggestions

Add a "Use when..." clause naming concrete triggers (e.g., "Use when building a Tetris-themed or retro-arcade UI, or when the user wants playful, high-contrast game aesthetics").

Reframe as concrete capabilities/actions rather than style traits (e.g., "Applies a Tetris-inspired design system—tokens, typography, and component guidance—to UI artifacts").

Include natural user-facing terms ("retro game", "arcade", "Tetris theme", "playful UI") to improve trigger coverage.

DimensionReasoningScore

Specificity

Names concrete style attributes ("playful colors, bold display fonts, and compact, high-energy layouts") but describes traits rather than multiple specific actions, fitting anchor 2.

2 / 3

Completeness

States what the design looks like but includes no "Use when..." trigger clause; per guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

"block-game", "playful colors", "bold display fonts" are somewhat natural but lack common user variations like "Tetris theme" or "retro game UI", fitting anchor 2 rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The "block-game inspired" framing is distinctive, yet generic styling language (colors, fonts, layouts) could overlap with other design skills, matching anchor 2.

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.