Name: banner-design
Rating: 60 (1 reviews)
Author: nextlevelbuilder

banner-design

Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with optional generated or supplied visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/banner-design/SKILL.md

The canonical home for this skill is banner-design in nextlevelbuilder/ui-ux-pro-max-skill

Quality

Content

75%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 a well-sequenced, concrete five-step banner design workflow with explicit design rules, file conventions, and a properly signaled single reference file. It scores consistently at anchor 4: actionable and efficient, with only minor gaps (no sample HTML/CSS, some implicit checkpoints, and inline tables duplicating reference content).

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no explanation of known concepts; minor over-explanation remains in the 'Available Resources' and 'Security' sections and in quick-reference tables that duplicate content in the bundled reference file, fitting anchor 4 rather than the every-token-earns-its-place anchor 5.	4 / 5
Actionability	Guidance is concrete and executable for an instruction-only skill — exact dimensions, 'text contrast of at least 4.5:1', 'critical content in central 70-80%', filename conventions, and an output path tree — but there is no sample HTML/CSS template and the capture step gives no concrete command, leaving minor gaps consistent with anchor 4.	4 / 5
Workflow Clarity	The five-step workflow is clearly sequenced with an explicit verification step ('Verify the exported pixel dimensions, safe-zone crop, font loading, and image quality'), an error-recovery path for oversized files, and an iterate-until-approved loop; some checkpoints remain implicit (e.g. 'Preview each banner' lacks a pass/fail check), so it matches anchor 4 rather than anchor 5's fully explicit validation and checklists.	4 / 5
Progressive Disclosure	A single one-level-deep reference (references/banner-sizes-and-styles.md, verified to exist) is clearly signaled three times, and the split keeps quick-reference tables inline with bulk detail in the file — matching anchor 4's 'a few key examples inline, bulk in separate file' rather than anchor 5, since the inline size and style tables duplicate reference content.	4 / 5
	Total	16 / 20 Passed

Description

66%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 clearly communicates a banner-design niche with strong platform and style keyword coverage, but it lacks any explicit 'Use when...' trigger guidance and its action list is three synonyms for one capability. Adding a when-to-use clause and distinct action verbs would raise completeness and specificity.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks for a banner, cover, header, hero image, or display ad for any platform' to satisfy the completeness requirement.

Replace the synonymous 'design, create, generate banner' action list with distinct capabilities, e.g. 'generate multiple art-direction options, build banners in HTML/CSS, and export PNGs at exact platform sizes'.

Include common user synonyms like 'cover', 'header', and 'social media post' alongside the platform names to broaden natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates platforms and 14 styles ('Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display'), but the listed actions ('design, create, generate banner') are synonyms of a single capability rather than several distinct concrete actions, matching the 'several specific actions; minor gaps' anchor rather than the comprehensive anchor 5.	4 / 5
Completeness	The 'what' is clear ('Design banners for social media, ads, website heroes, creative assets, and print'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the judging guidelines cap at 3; 'Actions: design, create, generate banner' describes verbs, not activation conditions, so it cannot reach anchor 4.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('banners', 'social media', 'ads', 'website heroes', platform names, style names), but common user phrasings like 'cover', 'header', and 'social media post' are absent, so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5 and is well above the sparse anchors 2-3.	4 / 5
Distinctiveness Conflict Risk	It carves a clear banner-design niche with enumerated platforms and styles, but phrases like 'creative assets' and the broad style list leave minor overlap risk with general design or creative-asset skills, matching anchor 4 rather than the minimal-conflict anchor 5.	4 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: nextlevelbuilder/ui-ux-pro-max-skill
Path: .claude/skills/banner-design/SKILL.md
Commit: 09170ee

Reviewed: 2 hours 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.