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
75%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/brand-identity/SKILL.mdQuality
Discovery
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 a strong skill description that clearly articulates what the skill does (design/evaluate brand visual identity across six specific domains), when to use it (explicit trigger clause with extensive keyword list), and includes contextual triggers for workflow sequencing. It uses proper third-person voice and provides comprehensive natural language trigger terms that users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Design or evaluate a brand visual identity system covering logo, color, typography, imagery direction, iconography, and motion principles.' This enumerates six distinct capability areas. | 3 / 3 |
Completeness | Clearly answers both 'what' (design or evaluate a brand visual identity system covering multiple 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 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 | Occupies a clear niche around brand visual identity systems with highly specific triggers like 'wordmark', 'monogram', 'brand mark', 'type system', and 'motion principles' that are unlikely to conflict with other skills. The contextual trigger about having 'brand direction approved' further narrows the scope. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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 comprehensive brand identity framework that covers all five visual identity elements with clear structure and useful failure patterns. Its main weaknesses are verbosity (explaining concepts Claude likely knows), lack of concrete examples showing what good output looks like, and a monolithic structure that would benefit from splitting detailed element specs into referenced files. The workflow is logical but lacks explicit validation feedback loops within the design steps.
Suggestions
Add a concrete example of at least one completed element (e.g., a sample color system with hex codes, contrast ratios, and usage rules) so Claude knows what the expected output quality looks like.
Trim explanatory content Claude already knows (WCAG definitions, what color blindness is, what variable fonts are) to just the actionable rules and constraints.
Move the detailed per-element specifications into referenced files (e.g., references/logo-system.md, references/color-system.md) and keep SKILL.md as a concise overview with the workflow and cross-references.
Add explicit feedback loops in the workflow for common failure points — e.g., 'After defining colors, run contrast checks; if any primary pairing fails AA, revise before proceeding to typography.'
| Dimension | Reasoning | Score |
|---|---|---|
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 instruction, which is fine, but the overall document is quite long (~200+ lines) with explanatory padding that could be trimmed. | 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 'what to do' — there are no concrete examples of a completed color system, no sample typography spec, no example logo system documentation. The output format section names files but doesn't show what their contents should look like. | 2 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced and logical, with a stress-test step (step 4) that serves as a validation checkpoint. However, there are no explicit feedback loops or error recovery steps within the element-by-element design phase — for instance, no guidance on what to do when contrast testing fails or when licensing checks reveal problems. The failure patterns section partially compensates but is separate from the workflow. | 2 / 3 |
Progressive Disclosure | The skill references two files in `references/` and links to related 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 content is also quite long and monolithic — the detailed per-element specifications (logo system components, color system components, etc.) could be split into referenced files, keeping SKILL.md as a leaner overview. | 2 / 3 |
Total | 8 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- rampstackco/claude-skills
- Commit
8e70d03
- 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.