sega

A playful, arcade-inspired interface for games — built on the VT323 pixel typeface, hard-edged 0px corners, chunky pill buttons that physically press into solid offset blocks

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/sega/SKILL.md

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 well-structured, actionable authoring guide with concrete tokens, required states, a numbered workflow, and quality gates, appropriately self-contained with no nested references; its main weakness is mild redundancy across the rules/behavior/gates sections that could be consolidated for token efficiency.

Suggestions

Merge the overlapping guidance in 'Rules: Do/Don't', 'Expected Behavior', 'Quality Gates', and 'Example Constraint Language' to remove repeated accessibility/consistency statements.

Include one short worked example of the Required Output Structure (e.g. a filled-in component rule) so the abstract structure becomes copy-paste ready.

Pair at least one do-rule with a concrete don't-example inline, since the skill instructs authors to do this but provides none itself.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean bullet-lists that assume Claude's competence and avoid explaining basics, but 'Rules: Do/Don't', 'Expected Behavior', 'Quality Gates', and 'Example Constraint Language' overlap on accessibility/consistency guidance and could be consolidated, so it is not fully tight.	2 / 3
Actionability	For an instruction-only skill the guidance is concrete and actionable: exact tokens (#4502FF, spacing 4/8/12/16/24/32), a named typography scale, required states (default, hover, focus-visible, active, disabled, loading, error), and a specific output structure with section names.	3 / 3
Workflow Clarity	The 'Guideline Authoring Workflow' is a clear six-step numbered sequence, reinforced by 'Quality Gates' criteria and ending in a QA-checklist step, providing explicit validation/checkpoint guidance for the authoring process.	3 / 3
Progressive Disclosure	The skill is a single self-contained file with no bundle directories and no dangling references, organized into clear '##' sections (Brand, Style Foundations, Rules, Workflow, Output Structure, Quality Gates), so the well-organized structure earns a top score with no external references needed.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 vivid and distinctive, painting a concrete visual identity in third person, but it functions as a style statement rather than a capability/trigger description: it names no actions and lacks an explicit 'Use when' clause, capping completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating or theming game/arcade UI, pixel-art interfaces, or retro design systems.'

Lead with a verb describing the skill's action (e.g. 'Authors and applies the Sega arcade design-system...') so capabilities are explicit, not just style attributes.

Broaden trigger terms to include natural variations like 'design system', 'UI theme', 'retro', and 'pixel art' for better discoverability.

Dimension	Reasoning	Score
Specificity	The description names a clear domain ('arcade-inspired interface for games') and concrete attributes ('VT323 pixel typeface, hard-edged 0px corners, chunky pill buttons that physically press into solid offset blocks'), but it is a descriptive noun phrase with no verbs/actions describing what the skill does, so it does not reach the 'multiple specific concrete actions' anchor.	2 / 3
Completeness	It clearly conveys what the interface is, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2 with the 'when' only implied.	2 / 3
Trigger Term Quality	It includes relevant natural terms a user might say ('arcade-inspired', 'games', 'VT323 pixel typeface', 'pill buttons'), but misses common variations such as 'design system', 'UI theme', 'retro', or 'pixel art' that a user would plausibly use to invoke this skill.	2 / 3
Distinctiveness Conflict Risk	The highly specific arcade/VT323/pixel/0px-corner framing carves out a clear niche that is unlikely to trigger for the wrong skill or conflict with generic design-system skills.	3 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: bergside/awesome-design-skills
Path: skills/sega/SKILL.md
Commit: f631a09

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.