CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-guidelines

When the user wants to apply, document, or enforce brand guidelines for any product or company. Also use when the user mentions 'brand guidelines,' 'brand colors,' 'typography,' 'logo usage,' 'brand voice,' 'visual identity,' 'tone of voice,' 'brand standards,' 'style guide,' 'brand consistency,' or 'company design standards.' Covers color systems, typography, logo rules, imagery guidelines, and tone matrix for any brand — including Anthropic's official identity.

66

Quality

80%

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 ./.gemini/skills/brand-guidelines/SKILL.md

The canonical home for this skill is brand-guidelines in alirezarezvani/claude-skills

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 is well-structured and concise with a clear workflow and validation checklist, but its progressive-disclosure design is undermined by a broken reference: the cited references/brand-identity-and-framework.md file is absent, which also hollows out the skill's core actionable brand-identity content.

Suggestions

Add the missing references/brand-identity-and-framework.md file (or remove the pointer and inline the essential Anthropic color codes, typography specs, and logo rules) so the deferred content is actually retrievable.

Tighten the 'Communication' section by dropping the editorializing ('it's a trust signal', 'erodes recognition') and keeping only the concrete guidance about naming exact color codes, font weights, and pixel measurements.

Make the audit checklist actionable by linking each item to where the approved value lives (e.g., 'Colors match approved palette → see color system in references/brand-identity-and-framework.md') so a contractor can verify rather than just check a box.

DimensionReasoningScore

Conciseness

The body is well-organized with tight checklists, a compact artifacts table, and short sections, and it avoids explaining concepts Claude already knows; minor over-explanation remains in the 'Communication' paragraph ('it's a trust signal... erodes recognition') and the 'You are an expert' opener, keeping it just below the lean level-5 anchor.

4 / 5

Actionability

Concrete guidance exists via the Quick Audit Checklist and Output Artifacts table, but the core actionable brand data (Anthropic colors, typography, logo rules) is deferred to 'references/brand-identity-and-framework.md', a file that is not present in the bundle, so the most executable content is unreachable — matching the 'some concrete guidance but incomplete' anchor.

3 / 5

Workflow Clarity

'How to Use This Skill' lays out a clear four-step sequence and the Quick Audit Checklist serves as an explicit validation checkpoint ('Always check for consistency before creativity'); no destructive/batch operation applies, so the missing-feedback-loop cap does not bind, leaving only minor validation gaps versus the level-5 anchor.

4 / 5

Progressive Disclosure

The body correctly uses a one-level-deep, clearly signaled reference ('→ See references/brand-identity-and-framework.md for details'), but that referenced file does not exist in the bundle, so navigation to the deferred content fails — the disclosure structure is sound but its target is missing, fitting between the level-3 and level-4 anchors.

3 / 5

Total

14

/

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, well-structured description that clearly answers both 'what' and 'when' with a comprehensive set of natural trigger phrases and broad domain coverage. The only soft spot is mild overlap with sibling marketing/design skills and slightly abstract action verbs.

DimensionReasoningScore

Specificity

Names three concrete verbs ('apply, document, or enforce brand guidelines') and enumerates comprehensive coverage ('color systems, typography, logo rules, imagery guidelines, and tone matrix'), but the verbs are more abstract than operations like 'extract/fill/merge', leaving a minor gap versus the level-5 anchor.

4 / 5

Completeness

It explicitly states what the skill covers ('Covers color systems, typography, logo rules...') and provides an explicit 'Use when...' clause with concrete trigger phrases, satisfying both halves of the level-5 anchor.

5 / 5

Trigger Term Quality

The 'Also use when the user mentions' clause lists eleven natural, synonym-rich trigger phrases ('brand guidelines,' 'brand colors,' 'typography,' 'logo usage,' 'brand voice,' 'visual identity,' 'tone of voice,' 'brand standards,' 'style guide,' 'brand consistency,' 'company design standards'), matching the comprehensive coverage anchor.

5 / 5

Distinctiveness Conflict Risk

The brand-specific triggers carve a clear niche with minimal wrong-skill risk, but the Related Skills section reveals real overlap with closely related marketing/design skills (copywriting, canvas-design, social-content), matching 'mostly distinct; minor overlap risk' rather than the minimal-conflict level-5 anchor.

4 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/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.