CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bencium-innovative-ux-designer

Develop an independent visual language and turn the human-chosen direction into a production-ready graphic, brand, campaign, publication, web, or product system. Use when originality and differentiation matter enough to escape generic AI and Big Tech aesthetics. Guides a minimum-evidence start, ten isolated typography-led HTML design directions made only from type, color, and space, visual-first human judgement, explicit commitment, and concrete Round 2 production. Do not use for routine UI fixes, small components, or applying an existing design system.

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 is a well-organized, highly actionable workflow with strong validation gates and clean progressive disclosure into real reference files. Its main weakness is repetition of the typography and color-role rules, which inflates length without adding clarity.

Suggestions

Consolidate the repeated typography-only and color-role definitions (currently restated in 'Create A through J', the reject/rebuild list, and the divergence guidance) into a single canonical statement referenced once.

Add a compact Quick-start summary at the top listing the phase sequence and the four reference files with their read-gates, so the workflow spine is visible before the detailed laws.

Consider one short inline HTML skeleton or capsule template so the executable artifact format is unambiguous without a separate file.

DimensionReasoningScore

Conciseness

The body is densely directive rather than padded with concept explanations, but it restates the typography-only rules and color-role definitions multiple times across 'Create A through J', the reject/rebuild list, and the divergence guidance, so it could be tightened.

3 / 5

Actionability

Provides concrete executable guidance—build A.html through J.html plus index.html using dependency-free HTML/CSS, copy the capsule into ROUND-2-CONTEXT.md, report named proof levels—with only minor gaps since no literal code blocks are shown (acceptable for an instruction-only skill).

4 / 5

Workflow Clarity

A clear sequenced workflow (brief → seal studio → create A–J → present visually → select/lock → Round 2 → production system → completion) with explicit validation checkpoints ('Stop after source-level validation', VERIFICATION.md, proof-level reporting) and feedback loops for batch generation and locking.

5 / 5

Progressive Disclosure

SKILL.md is a well-structured overview with clearly signaled, phase-gated, one-level-deep references to four real files (ISOLATION-PROTOCOL.md, CONCEPT-ROUNDS.md, PRODUCTION-SYSTEM.md, VERIFICATION.md), all of which exist, giving easy navigation.

5 / 5

Total

17

/

20

Passed

Description

92%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 concrete, comprehensive, and well-bounded with explicit use and do-not-use triggers, giving it strong specificity, completeness, and distinctiveness. Trigger-term phrasing leans conceptual rather than mirroring user utterances, capping that dimension just below the top.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across a comprehensive scope—'ten isolated typography-led HTML design directions', 'production-ready graphic, brand, campaign, publication, web, or product system', and 'concrete Round 2 production'—matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both 'what' (develop visual language → production-ready system, ten directions, Round 2 production) and 'when' ('Use when originality and differentiation matter...') plus an explicit exclusion clause ('Do not use for routine UI fixes...').

5 / 5

Trigger Term Quality

Good natural-term coverage ('visual language', 'brand', 'campaign', 'publication', 'product system', 'routine UI fixes') with explicit trigger framing, though phrased more as concepts than the verbatim phrases a user would say, leaving a few synonyms uncovered.

4 / 5

Distinctiveness Conflict Risk

A clear niche (independent typography-led visual language invention under isolation) with distinct triggers and an explicit anti-trigger ('Do not use for routine UI fixes, small components, or applying an existing design system'), giving minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

bencium/bencium-marketplace

Path

bencium-innovative-ux-designer/skills/bencium-innovative-ux-designer/SKILL.md

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.