CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brandkit

Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts.

55

Quality

69%

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/brandkit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 unusually concrete art-direction guidance (specific panel systems, palettes, modes, and a prompt template) that an instruction-only skill needs, with a discernible workflow and explicit intake decision logic. Its weaknesses are redundancy-driven length, everything inlined in one large file with no reference splitting, and the absence of a worked end-to-end prompt example.

Suggestions

Move the VISUAL MODES catalog and LOGO CONCEPT METHODS into separate reference files (e.g. references/visual-modes.md, references/logo-methods.md), keeping SKILL.md as a lean overview with one-level-deep pointers.

Add a single worked example of a fully filled-in internal prompt for one brand so the PROMPT TEMPLATE is demonstrably executable end to end.

Consolidate the overlapping avoid-lists (ANTI-GENERIC RULES, MOCKUP DIRECTION, IMAGE DIRECTION, TEXT RULES) into one section and trim repeated "premium/premium-feel" framing to cut token cost without losing constraints.

DimensionReasoningScore

Conciseness

The fragment style keeps individual lines lean and most content is skill-specific taste guidance, but the ~840-line body has substantial cross-section redundancy ("premium" recurs throughout; VISUAL MODES, DETAIL LANGUAGE, MOCKUP DIRECTION, and ANTI-GENERIC RULES overlap heavily) and restates general design principles Claude already knows ("simple, memorable, symbolic, scalable").

3 / 5

Actionability

Highly concrete instruction-only guidance: named layout grids with each of the 9 panels specified, specific palettes, named mockup elements, example taglines, and a fill-in internal PROMPT TEMPLATE that serves as the executable artifact. It stops short of fully copy-paste-ready because there is no worked end-to-end example of a completed prompt.

4 / 5

Workflow Clarity

A clear sequence emerges from section order (intake → brand strategy → visual mode → layout → prompt template → generation), with explicit decision logic in BRAND INTAKE, fallback behavior for unsupported canvas sizes ("Report the actual output size; do not promise unsupported pixel dimensions"), and a FINAL OUTPUT STANDARD checklist. Minor gaps: no explicit numbered workflow and no post-generation review step.

4 / 5

Progressive Disclosure

Section headers provide decent in-file structure, but there are no bundle files at all — the eight-mode VISUAL MODES catalog and the LOGO CONCEPT METHODS are prime candidates for separate reference files and are fully inlined in a single ~19KB file, matching the "content that should be separate is inline" anchor.

3 / 5

Total

14

/

20

Passed

Description

61%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 what the skill produces and stays in third person, with good domain keywords. Its main weaknesses are the complete absence of explicit "when to use" trigger guidance and two sentences of quality-flavored padding ("Trained for", "Optimized for") instead of additional concrete actions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a brand kit, brand guidelines board, logo concept board, identity deck, or brand presentation image."

Replace the "Trained for" / "Optimized for" adjective lists with additional concrete actions (e.g. "Builds 3x3 and 2x3 presentation grids, designs symbolic logo marks, and composes mockup panels") to lift specificity.

Include natural synonyms users would say ("logo design", "brand identity", "moodboard", "brand board") to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations"), but the remaining sentences ("Trained for...", "Optimized for...") list quality adjectives rather than additional actions, so coverage is not comprehensive.

3 / 5

Completeness

The "what" is clear (image generation for brand-kit boards and decks), but there is no "Use when..." clause or any equivalent explicit trigger guidance — the "when" is entirely missing, not merely weakly implied.

3 / 5

Trigger Term Quality

Includes natural user terms like "brand-kit", "brand-guidelines", "logo systems", "identity decks", and "brand systems", but misses common variations users would actually say such as "logo design", "brand identity", "moodboard", or "brand board".

4 / 5

Distinctiveness Conflict Risk

"Brand-kit image generation" is a fairly distinct niche unlikely to grab unrelated skills, but the marketing-style framing ("visual-world presentations") leaves minor overlap risk with general image-generation and design skills.

4 / 5

Total

14

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (844 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

Leonxlnx/taste-skill

Path

skills/brandkit/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.