CtrlK
BlogDocsLog inGet started
Tessl Logo

pacman

Retro arcade-inspired design with pixel fonts, dotted borders, playful high-contrast colors, and 8-bit game aesthetics.

65

Quality

78%

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/pacman/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 well-organized, actionable authoring guide with concrete tokens, an explicit output structure, and a sequenced workflow plus QA gates; its main weakness is redundant coverage of component-level rules across three overlapping sections.

Suggestions

Merge the overlapping component-guidance content in "Guideline Authoring Workflow", "Required Output Structure", and "Component Rule Expectations" into one authoritative section to remove triplicated coverage of states, anatomy, accessibility, and responsive behavior.

Tighten the abstract "Rules: Do/Don't" items (e.g., "preserve visual hierarchy", "avoid ambiguous labels") by anchoring each to a token, threshold, or example as the "Quality Gates" section itself recommends.

DimensionReasoningScore

Conciseness

The body is mostly tight bullet prose with no concept padding, but component-rule guidance is repeated across "Guideline Authoring Workflow", "Required Output Structure", and "Component Rule Expectations" (states, anatomy, accessibility, responsive behavior each reappear), so it could be consolidated.

2 / 3

Actionability

Concrete tokens (hex colors, named fonts, 8pt spacing), an explicit required-state list (default, hover, focus-visible, active, disabled, loading, error), and a defined output structure give specific, executable guidance appropriate for an instruction-only skill.

3 / 3

Workflow Clarity

The 6-step "Guideline Authoring Workflow" is clearly sequenced and pairs with a QA-checklist final step and a "Quality Gates" checklist, supplying validation checkpoints; it is not the level below because checkpoints are explicit rather than implicit.

3 / 3

Progressive Disclosure

The skill is a self-contained single file with no external references needed and is organized into clearly labeled sections, which qualifies for a top score under the simple-skill guidance despite being slightly over 50 lines.

3 / 3

Total

11

/

12

Passed

Description

72%

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 paints a vivid, distinctive visual niche but is a noun-phrase style statement with no actions and no explicit usage trigger, leaving a reader unsure when to invoke the skill.

Suggestions

Add an explicit "Use when..." clause naming triggering situations (e.g., building retro game UIs, arcade-themed dashboards, or pixel-art landing pages).

Lead with a concrete action verb (e.g., "Applies a retro arcade-inspired design system...") so the capability is stated, not just the aesthetic.

Include common trigger variations like "game UI", "retro game", or "Pac-Man-style" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain and concrete visual elements ("pixel fonts, dotted borders, playful high-contrast colors, and 8-bit game aesthetics"), but contains no action verbs describing what the skill does, so it falls short of listing multiple concrete capabilities.

2 / 3

Completeness

It conveys what the skill produces (a retro arcade design system) but lacks any "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Natural user-facing terms are well covered ("arcade-inspired", "pixel fonts", "8-bit game aesthetics", "high-contrast colors"), matching the kinds of phrases a user would actually say when requesting a retro game look.

3 / 3

Distinctiveness Conflict Risk

The arcade/8-bit/pixel aesthetic is a clear niche with distinct triggers unlikely to collide with generic design skills, and it is not the level below because it is far more specific than "Works with document files"-style overlap cases.

3 / 3

Total

10

/

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.