Name: bencium-impact-designer
Rating: 58.4 (1 reviews)
Author: bencium

bencium-impact-designer

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. Based on Anthropic's Frontend Designer Skill

Quality

68%

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 ./bencium-impact-designer/skills/bencium-impact-designer/SKILL.md

Quality

Content

52%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers strong, actionable design guidance and a clear creative workflow, but it is severely over-long with extensive verbatim repetition and inline reference material that should be split out. The referenced progressive-disclosure files are missing from the bundle entirely.

Suggestions

De-duplicate the recurring rules (banned fonts, no glass-morphism/Apple-mimicry, 'stand out from generic patterns') into a single canonical statement and delete the repeats — this alone would cut hundreds of lines.

Move the bulk color-system, typography-scale, and motion-spec reference material into the already-cited ACCESSIBILITY.md / MOTION-SPEC.md / RESPONSIVE-DESIGN.md files (create them in references/) and keep SKILL.md as a concise overview with one-level-deep links.

Trim primers on concepts Claude already knows (basic CSS color roles, line-height/line-length readability rules, standard WCAG text) to lean, decision-oriented guidance.

Dimension	Reasoning	Score
Conciseness	At ~980 lines the body is noticeably verbose with heavy redundancy — the Inter/Roboto/Space-Grotesk ban, the no-glass-morphism/Apple-mimicry rule, and the 'stand out from generic patterns' passage each recur verbatim or near-verbatim multiple times, and large CSS color/typography primers restate basics Claude already knows.	2 / 5
Actionability	Provides mostly executable guidance — concrete shadcn/Button + Tailwind snippets, responsive clamp() typography, and color-palette examples — though these are interleaved with abstract philosophy ('What would Sagmeister do?', tone-option catalogs, dice-roll variety tables) that lacks code.	4 / 5
Workflow Clarity	A clear sequence exists (Design Workflow: Understand Context → Explore Options → Implement Iteratively → Validate via playwright MCP) with a Design Decision Checklist and 'Questions to Ask First' checkpoint; this is a creative rather than destructive/batch skill so the validation cap does not apply, but checkpoints are loosely defined.	4 / 5
Progressive Disclosure	Structure is minimal for a skill of this size: hundreds of lines of typography/color/motion reference material that belong in separate files are inlined in SKILL.md, and the three cited 'Progressive Disclosure Files' (ACCESSIBILITY.md, MOTION-SPEC.md, RESPONSIVE-DESIGN.md) do not exist in the bundle (no references/ directory).	2 / 5
	Total	12 / 20 Passed

Description

83%Weight 40%Scale 1-5

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 well-crafted: third-person voice, a clear 'what', and an explicit 'Use when...' trigger with natural keywords. It is comprehensive and largely distinctive, with only minor gaps in keyword synonyms and action specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Create distinctive, production-grade frontend interfaces', 'build web components, pages, or applications', 'Generates creative, polished code that avoids generic AI aesthetics' — with only minor gaps in coverage of specific output types.	4 / 5
Completeness	Explicitly answers both 'what' ('Create distinctive, production-grade frontend interfaces ... Generates creative, polished code') and 'when' ('Use this skill when the user asks to build web components, pages, or applications') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes a natural trigger clause ('Use this skill when the user asks to build web components, pages, or applications') with good keyword coverage, though it omits common synonyms like 'UI', 'frontend', 'design', or 'interface'.	4 / 5
Distinctiveness Conflict Risk	The anti-generic-frontend-aesthetic niche ('avoids generic AI aesthetics', 'distinctive, production-grade frontend interfaces') is mostly distinct from general coding skills, with only minor overlap risk against ordinary frontend build skills.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (989 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: bencium/bencium-marketplace
Path: bencium-impact-designer/skills/bencium-impact-designer/SKILL.md
Commit: bda4647

Reviewed: 12 days 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.