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.

71

Quality

87%

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

The canonical home for this skill is brand-identity in rampstackco/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A well-structured, opinionated framework skill: lean sectioned overview, concrete thresholds and checklists, a gated 6-step workflow, and correctly offloaded detail in two real one-level-deep reference files. It sits just below the top anchors on actionability and workflow clarity where guidance is judgment-level and validation checkpoints are implied rather than explicit.

Suggestions

Trim generalities Claude already knows (e.g., 'Type is the second-most-recognizable element of a brand after the logo', 'Imagery direction is often underspecified') to tighten conciseness.

Make workflow validation checkpoints explicit and testable — e.g., concrete pass/fail criteria for the stress-test step ('every mark legible at 16px', 'every text color pairing passes 4.5:1') instead of 'Where does it break? Iterate'.

Add one worked example of applying the framework (e.g., a filled-in mini color-system entry or a do/don't pairing) to raise actionability from judgment-level to executable guidance.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive — specific numbers ("Legible at 16 pixels", "5 to 8 carefully chosen colors", "100ms / 200-300ms / 500ms+") rather than padded explanation. A few lines restate general design knowledge Claude already has ("Type is the second-most-recognizable element of a brand after the logo", "Imagery direction is often underspecified"), keeping it below the lean-and-efficient 5 anchor.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete: per-element component checklists, hard thresholds (4.5:1 contrast, 24x24 icon grid, 8 percent color-blind prevalence), a 6-step workflow, and an explicit output file tree (`identity/logo/`, `identity/colors.md`, ...). Not 5 because several directives are judgment-level rather than executable ("Squint at it", "they must work together") and there are no worked good/bad examples inline — minor gaps remain.

4 / 5

Workflow Clarity

The workflow is a clearly sequenced 6-step process with an entry gate ("Confirm brand direction... If unclear, return to `brand-ideation`"), an explicit feedback loop ("Stress-test... Where does it break? Iterate"), and a final checkpoint ("Get sign-off before broad rollout"). Not 5 because validation checkpoints are stated as principles rather than explicit pass/fail criteria per step, and the destructive/batch cap does not apply since no destructive operations are involved.

4 / 5

Progressive Disclosure

The body is a well-sectioned overview (~195 lines) with two clearly signaled one-level-deep references (both verified to exist: `references/identity-system-spec.md`, `references/contrast-and-accessibility.md`) that appropriately pull the spec template and contrast math out of the main file. References are listed in a dedicated section with descriptions, and the spec templates contain no nested references — matching the clear-overview-with-well-signaled-references anchor.

5 / 5

Total

17

/

20

Passed

Description

96%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.

A strong description: third-person voice, concrete action list, explicit 'Use when' clause, and comprehensive natural trigger terms. The only weakness is a handful of generic trigger terms that overlap with adjacent design skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the full scope: "Design or evaluate a brand visual identity system covering logo, color, typography, imagery direction, iconography, and motion principles" — comprehensive coverage of concrete capabilities. Not 4 because there are no gaps in coverage; every element of the skill's body is named.

5 / 5

Completeness

Explicitly answers both what ("Design or evaluate a brand visual identity system covering...") and when ("Use this skill whenever the user wants to design a logo, build a visual identity, define brand colors...") with concrete trigger phrases. Not 4 because the 'when' clause is fully explicit, not merely implied or generic.

5 / 5

Trigger Term Quality

Extensive natural trigger coverage with synonyms: "logo design, brand identity, visual identity, brand mark, wordmark, monogram, color palette, brand colors, brand typography, type system, iconography, brand imagery, motion design" — these are exactly the phrases a user would say. Not 4 because even uncommon variations (monogram, wordmark, brand system, identity system) are present.

5 / 5

Distinctiveness Conflict Risk

The brand-identity niche is clear with mostly distinct triggers (wordmark, monogram, brand mark), but generic terms like "color palette", "type system", and "motion design" carry minor overlap risk with closely related design-system and dataviz skills. Not 5 because those shared terms could plausibly fire the wrong skill; not 3 because the core triggers are unambiguously brand-specific.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.