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.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-organized, actionable framework with a clear sequenced workflow and properly signaled one-level references. Its main weakness is conciseness: the ~200-line body carries editorial framing and inline detail that could be tightened or pushed into references.

Suggestions

Tighten editorial framing sentences (e.g., 'A color system is more than a palette. It is the rules for how color carries meaning.' and 'Type is the second-most-recognizable element of a brand after the logo.') to pure directives, or move them into the reference files.

Move the full per-element component/principle lists for one or two of the five elements into references/identity-system-spec.md, keeping SKILL.md as a tighter overview that points to the detail.

Consider a brief 'Quick reference' summary of the five elements and their key thresholds near the top so the most-used specifics are reachable without scanning the full body.

DimensionReasoningScore

Conciseness

The body is concrete and free of Claude-known concept padding, but at ~200 lines it includes editorial framing ('A color system is more than a palette. It is the rules...') and inline per-element detail that could be tightened or moved to references, fitting the mostly-efficient-but-could-be-tighter anchor rather than the maximally lean 3.

2 / 3

Actionability

Highly actionable guidance: specific components to define, per-color documentation fields (hex/RGB/HSL/CMYK, WCAG ratios, pairings), concrete thresholds (16px, 4.5:1, 5-8 colors, 60fps), and a defined output file structure; per the code-vs-instruction note, the absence of code is not penalized.

3 / 3

Workflow Clarity

Six sequenced steps with an explicit stress-test feedback checkpoint ('Apply the system to 3 to 5 mock applications... Where does it break? Iterate') and a sign-off gate, matching the clear-sequence-with-explicit-validation anchor rather than the checkpoint-missing 2.

3 / 3

Progressive Disclosure

Two real, well-signaled one-level-deep references (identity-system-spec.md, contrast-and-accessibility.md) linked from the body, with the detailed spec template externalized and the body organized into clear navigable sections, matching the clear-overview-with-signaled-references anchor.

3 / 3

Total

11

/

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.

A strong, third-person description that states concrete capabilities, supplies extensive natural trigger terms, and explicitly covers both what the skill does and when to use it. Distinctiveness is reinforced by the brand-ideation boundary.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('design a logo, build a visual identity, define brand colors, choose brand typography, develop iconography, plan brand imagery, or evaluate an existing identity'), matching the comprehensive-actions anchor rather than the partial domain-only anchor at 2.

3 / 3

Completeness

Explicitly answers both what ('Design or evaluate a brand visual identity system...') and when ('Use this skill whenever the user wants to...', 'Triggers on...', 'Also triggers when...'), satisfying the both-what-and-when anchor; it is not the 2 anchor where 'when' is only implied.

3 / 3

Trigger Term Quality

Broad natural-language triggers ('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') covering the terms users would actually say, beyond the some-keywords anchor at 2.

3 / 3

Distinctiveness Conflict Risk

Clear niche (visual identity artifacts post-direction-approval) with distinct triggers and an explicit boundary against brand-ideation, making wrong-skill conflicts unlikely; uses third-person voice with no voice penalty.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.