CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

71

Quality

89%

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

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, token-efficient overview that delegates detail appropriately to a single one-level-deep reference and provides a concrete audit checklist and intake questions. The main improvement areas are trimming the motivational preamble and tightening the apply-vs-create workflow so the checklist functions as an explicit validation checkpoint.

Suggestions

Trim the 'You are an expert...' role preamble and the trust-signal philosophy sentences in the Communication section; keep only the operational quality bar.

Integrate the Quick Audit Checklist into the workflow as an explicit validation step (e.g., 'run the audit checklist and only proceed when all items pass') instead of presenting it as a standalone tool.

Inline a brief, concrete outline of the framework steps for non-Anthropic brands (the 7 dimensions referenced by the Mini-Doc artifact) so the primary path does not depend entirely on the reference file.

DimensionReasoningScore

Conciseness

The body is largely efficient — every section (audit checklist, task questions, triggers, artifact table) carries actionable content and it avoids explaining concepts Claude already knows. Minor trimmable padding remains: the role preamble ('You are an expert in brand identity and visual design standards...') and the trust-signal philosophy in the Communication section ('Brand consistency is not a design preference — it's a trust signal. Every deviation from guidelines erodes recognition.') earn few tokens.

4 / 5

Actionability

For an instruction-only skill, guidance is mostly concrete and executable: an 8-item audit checklist with specific checks ('Logo has proper clear space,' 'Colors match approved palette'), a 5-question intake, and an artifact table specifying format and content of each output ('Full palette with hex, RGB, CMYK, Pantone, and usage rules'), backed by a reference containing concrete hex/RGB tables. It stops short of 5 because the framework sections for non-Anthropic brands defer heavily to the reference rather than giving inline, specific assessment steps.

4 / 5

Workflow Clarity

The 'How to Use This Skill' section gives a clear sequence (check marketing-context file, identify apply vs. create, select Anthropic identity vs. framework path, check consistency before creativity), and the audit checklist serves as a checkpoint. It is not a 5 because validation checkpoints are implicit (the checklist is offered as a tool, not wired into the workflow as an explicit verify-then-proceed step), and the sequence is dispersed across How to Use, Task-Specific Questions, and Proactive Triggers rather than one coherent flow.

4 / 5

Progressive Disclosure

The body is a well-organized overview that appropriately moves the Anthropic identity detail into references/brand-identity-and-framework.md, which exists in the bundle, is self-contained (262 lines, no nested references), and is clearly signaled one level deep ('→ See references/brand-identity-and-framework.md for details'). Navigation across sections is easy with clear headers.

5 / 5

Total

17

/

20

Passed

Description

95%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 that explicitly answers both what and when, packs in natural trigger synonyms, and clearly delimits the brand-guidelines niche. The only mild weakness is that the 'what' stays at the domain-enumeration level rather than naming more granular capabilities like auditing or system creation.

DimensionReasoningScore

Specificity

The description lists concrete actions ('apply, document, or enforce brand guidelines') and enumerates covered domains ('color systems, typography, logo rules, imagery guidelines, and tone matrix'), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the actions remain at the domain level without finer-grained capabilities (e.g., auditing assets, building a system from scratch).

4 / 5

Completeness

Both what and when are explicit: the when is 'When the user wants to apply, document, or enforce brand guidelines... Also use when the user mentions [concrete trigger phrases]' and the what is 'Covers color systems, typography, logo rules, imagery guidelines, and tone matrix for any brand.' This mirrors the anchor-5 example structure exactly; a 4 would require the when clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

It provides comprehensive natural-language triggers with synonyms users would actually say: 'brand guidelines,' 'brand colors,' 'typography,' 'logo usage,' 'brand voice,' 'visual identity,' 'tone of voice,' 'brand standards,' 'style guide,' 'brand consistency,' 'company design standards.' This matches the top anchor's comprehensive synonym coverage; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (brand identity standards for any product/company, explicitly including Anthropic's official identity) with distinct brand-specific triggers. Broad terms like 'typography' create only minimal overlap risk with general design skills, and the skill body further disambiguates via related-skills boundary statements.

5 / 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

alirezarezvani/claude-skills

Path

marketing-skill/skills/brand-guidelines/SKILL.md

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.