CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-identity

Design or evaluate a brand visual identity system covering logo, color, typography, imagery direction, iconography, and motion principles. Use this skill whenever the user wants to design a logo, build a visual identity, define brand colors, choose brand typography, develop iconography, plan brand imagery, or evaluate an existing identity for cohesion. Triggers on logo design, brand identity, visual identity, brand mark, wordmark, monogram, color palette, brand colors, brand typography, type system, iconography, brand imagery, motion design, brand system, identity system. Also triggers when the user has a brand direction approved and now needs the visual artifacts that express it.

63

Quality

75%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/brand-identity/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

This is a well-organized, comprehensive brand identity skill that covers all major visual identity elements with clear structure and useful failure patterns. Its main weaknesses are verbosity (it reads more like a design textbook chapter than a lean skill file) and limited actionability (checklists of considerations rather than concrete, executable guidance with examples of completed outputs). The progressive disclosure could be improved by moving detailed element specifications into reference files and keeping the SKILL.md as a tighter overview.

Suggestions

Add a concrete example of a completed element (e.g., a sample color system with actual hex values, contrast ratios, and usage rules) to make the skill more actionable and show Claude what 'done' looks like.

Move the detailed per-element breakdowns (logo system components, color system components, etc.) into the referenced spec template file, keeping only summary guidance and key principles in the main SKILL.md.

Add explicit validation criteria to the workflow stress-test step — e.g., 'Check: logo legible at 16px? All text pairings pass WCAG AA? Type renders with fallback stack? Motion respects prefers-reduced-motion?'

Trim explanatory content Claude already knows (what WCAG AA is, what color blindness prevalence is, what variable fonts are) to just the actionable rule or constraint.

DimensionReasoningScore

Conciseness

The skill is well-structured and mostly efficient, but includes some content Claude already knows (e.g., explaining what WCAG AA contrast ratios are, what color blindness is, what variable fonts are). Some sections like the imagery/illustration direction read more like a checklist template than actionable guidance, which is fine, but the overall document is quite long (~200+ lines) and could be tightened.

2 / 3

Actionability

The skill provides structured checklists and frameworks rather than executable code or commands, which is appropriate for a design-oriented skill. However, guidance remains at the level of 'what to think about' rather than 'exactly what to do' — there are no concrete examples of a completed color system, no sample logo system documentation, and no specific tools or commands. The framework is useful but stops short of fully actionable.

2 / 3

Workflow Clarity

The 6-step workflow is clearly sequenced and logical, with a stress-test step (step 4) serving as a validation checkpoint. However, the validation is implicit ('Where does it break? Iterate.') rather than explicit with concrete criteria. For a process involving potentially costly identity changes, the feedback loops could be more rigorous — e.g., specific accessibility validation steps, specific sign-off criteria.

2 / 3

Progressive Disclosure

The skill references two files in a `references/` directory and links to other skills (brand-ideation, brand-style-guide, brand-voice, design-standards), which is good navigation. However, no bundle files are provided, so the referenced files don't actually exist. The main document itself is quite long and some sections (like the detailed per-element breakdowns) could be split into reference files, with the SKILL.md serving as a leaner overview.

2 / 3

Total

8

/

12

Passed

Description

100%

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

This is an excellent skill description that clearly defines what the skill does, when to use it, and provides comprehensive trigger terms. It uses proper third-person voice, lists concrete capabilities, and includes both explicit trigger guidance and contextual usage scenarios. The description is thorough without being unnecessarily verbose.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and domains: 'Design or evaluate a brand visual identity system covering logo, color, typography, imagery direction, iconography, and motion principles.' This clearly enumerates the specific areas covered.

3 / 3

Completeness

Clearly answers both 'what' (design or evaluate a brand visual identity system covering specific areas) and 'when' (explicit 'Use this skill whenever...' clause plus a detailed 'Triggers on...' list and an additional contextual trigger about having brand direction approved).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'logo design, brand identity, visual identity, brand mark, wordmark, monogram, color palette, brand colors, brand typography, type system, iconography, brand imagery, motion design, brand system, identity system.' These are terms users would naturally use when requesting this type of work.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche in brand visual identity design. The specific trigger terms like 'wordmark, monogram, brand mark, type system, iconography' are unlikely to conflict with other skills. The description carves out a well-defined domain.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
rampstackco/claude-skills
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.