CtrlK
BlogDocsLog inGet started
Tessl Logo

applying-brand-guidelines

This skill applies consistent corporate branding and styling to all generated documents including colors, fonts, layouts, and messaging

49

Quality

53%

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

The canonical home for this skill is applying-brand-guidelines in anthropics/claude-cookbooks

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 content is a well-organized, concrete brand specification that is highly actionable on values, but it is weakened by missing validation feedback loops in the workflow, broken script references, and some basic explanations Claude does not need. Tightening these would move it from midrange to strong.

Suggestions

Wire validate_brand.py into the workflow as an explicit checkpoint with a feedback loop, e.g. 'Run validate_brand.py; if it reports issues, fix them and re-validate before finalizing.'

Add concrete invocation examples for the referenced scripts (e.g. `python scripts/apply_brand.py input.docx`), or remove the Scripts section if the files are not bundled.

Trim explanations of concepts Claude already knows (tone-of-voice definitions, comma/currency/percentage formatting rules) to keep the content lean.

DimensionReasoningScore

Conciseness

The bulk is genuinely brand-specific specs (hex codes, font sizes, templates) that earn their place, but sections like 'Tone of Voice' definitions and number-formatting rules explain concepts Claude already knows and could be tightened, fitting 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

It provides highly concrete, specific values (exact hex/RGB, pt sizes, inch margins, pixel dimensions) that are directly actionable, with only a minor gap that the referenced scripts lack invocation examples, fitting 'mostly executable guidance with minor gaps'.

4 / 5

Workflow Clarity

A clear six-step 'Application Instructions' sequence and a 'Before Finalizing' checklist exist, but there is no explicit validation feedback loop, and the destructive/batch nature of modifying documents caps workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

The body is well-sectioned with a clear hierarchy, but the 'Scripts' section references apply_brand.py and validate_brand.py that do not exist in ./scripts/, and ~100 lines of detailed reference material are inlined rather than split into separate files, fitting 'some structure but references not cleanly delivered'.

3 / 5

Total

13

/

20

Passed

Description

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

The description clearly conveys the skill's purpose (applying corporate branding across documents) and lists concrete aspects, but it lacks any explicit usage trigger and relies on a single action verb. Adding a 'Use when...' clause and more natural trigger synonyms would lift it above the midrange.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating or formatting documents that must match corporate brand standards, brand colors, or company style guidelines.'

Replace the single 'applies' verb with multiple concrete actions (e.g. 'applies brand colors, fonts, and templates; validates documents against brand standards').

Include natural trigger synonyms users actually say, such as 'brand guidelines', 'brand standards', 'templates', and 'style guide'.

DimensionReasoningScore

Specificity

The description names the domain ('corporate branding and styling') and concrete aspects ('colors, fonts, layouts, and messaging'), but offers only a single action verb ('applies') rather than multiple distinct actions, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

It clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3 ('clear what but when missing or only weakly implied').

3 / 5

Trigger Term Quality

It includes relevant natural terms like 'corporate branding', 'styling', 'colors', and 'fonts', but misses common variations users say such as 'brand guidelines', 'brand standards', 'templates', or specific file types, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

'Corporate branding and styling' is a recognizable niche, but applying styling to 'all generated documents' overlaps with general document-formatting and presentation skills, fitting 'somewhat specific but could still overlap'.

3 / 5

Total

12

/

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
anthropics/anthropic-cookbook
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.