CtrlK
BlogDocsLog inGet started
Tessl Logo

design

Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.

61

Quality

73%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-structured, highly actionable overview that routes cleanly to real reference files and scripts, but it duplicates reference content inline and omits explicit validation/verification checkpoints in its generation workflows.

Suggestions

Add an explicit verify/re-export checkpoint to the Logo, CIP, and Social Photos workflows (e.g. inspect generated output, fix prompt, regenerate) since these are batch/AI-generative operations.

Move the duplicated banner size/style and icon style tables out of SKILL.md into their referenced files to reduce token redundancy.

Replace a few prose repetitions of platform lists with a single pointer to the relevant reference file.

DimensionReasoningScore

Conciseness

The body is largely efficient with command tables and code blocks, but it repeats size/style tables inline that also live in referenced files and packs multiple large quick-reference tables (banner sizes, styles, icon styles) that add tokens Claude could pull from references.

2 / 3

Actionability

Every section gives concrete, executable, copy-paste-ready python3 commands with real flags (e.g. generate.py --brand ... --style ... --industry ...), plus concrete size tables, matching the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Sequences exist (Banner and Social Photos workflows are numbered), but batch/destructive AI generation and file-export steps lack explicit validate-then-fix feedback loops, and the Logo/CIP sections offer no verification checkpoint after generation.

2 / 3

Progressive Disclosure

Overview SKILL.md routes to real one-level-deep references (references/*.md all exist) and scripts with clear navigation tables; the body is an overview pointing to detailed materials, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

10

/

12

Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A dense, action-packed description with strong specificity and trigger terms, but it omits any explicit 'Use when...' guidance and aggregates many sub-skills, raising conflict risk and capping completeness.

Suggestions

Add an explicit 'Use when ...' clause naming the triggering situations (e.g. 'Use when designing a brand identity, logo, corporate identity program, presentation, banner, icon, or social media image').

Narrow or clarify routing so the description signals when to delegate to the external brand / design-system / ui-styling skills instead of claiming those tasks directly.

Trim the packed lists of style counts and platforms to reduce verbosity and overlap; keep the most natural trigger terms.

DimensionReasoningScore

Specificity

Lists many concrete actions ('design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos') and enumerates specific style counts and platforms, matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

It thoroughly answers 'what does this do' but never includes a 'Use when...' clause or equivalent explicit trigger guidance, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

Covers natural terms users would say ('design logo', 'create CIP', 'build slides', 'design banner', 'brand identity', 'design system') plus platform names (Facebook, Twitter, LinkedIn, Instagram), giving broad natural-keyword coverage.

3 / 3

Distinctiveness Conflict Risk

While the niche is concrete, it bundles seven sub-domains (logo, CIP, slides, banner, icon, social photos, brand/tokens/UI) and overlaps with external skills like brand, design-system, and ui-styling, so it could trigger for the wrong sibling skill.

2 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 12 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
nextlevelbuilder/ui-ux-pro-max-skill
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.