CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

82

2.77x
Quality

Does it follow best practices?

Impact

100%

2.77x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A compact, well-organized reference for brand styling, but it is held back by repeated font guidance, the absence of any executable code example, and no validation step for a document-modifying operation.

Suggestions

Consolidate the Poppins/Lora and Arial/Georgia fallback details into a single section to remove the repetition across Typography, Smart Font Application, Text Styling, and Font Management.

Add a short executable python-pptx example (e.g., setting RGBColor on a shape/run) so the guidance is copy-paste ready rather than only descriptive.

Include a brief validation step for the styling operation, such as re-opening the artifact to confirm fonts and colors applied correctly before returning it.

DimensionReasoningScore

Conciseness

The Poppins/Lora and Arial/Georgia fallback information is repeated across Typography, Smart Font Application, Text Styling, and Font Management, and phrases like "maintains color fidelity across different systems" add little; it is mostly efficient but could be tightened.

2 / 3

Actionability

Concrete specifics are present (hex values, font names, the 24pt threshold, "python-pptx's RGBColor class") but no executable code or worked example shows how to apply them, leaving the guidance incomplete.

2 / 3

Workflow Clarity

The body lists features rather than a sequenced process for styling an artifact, and a modifying/batch operation has no validate-or-verify step, which caps workflow clarity at 2.

2 / 3

Progressive Disclosure

The content is self-contained and well-organized into clearly labeled sections (Overview, Brand Guidelines, Features, Technical Details) with no nested or deep external references, and no bundle files are needed.

3 / 3

Total

9

/

12

Passed

Description

90%

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 uses third-person voice, states a clear niche, and includes an explicit "Use when" trigger with natural keywords. Its only limitation is that it names just two actions rather than a comprehensive list.

DimensionReasoningScore

Specificity

It names the domain and two concrete actions ("Applies ... brand colors and typography") but does not list a comprehensive set of actions, falling short of the anchor-3 pattern of multiple distinct concrete actions.

2 / 3

Completeness

It explicitly answers what it does (applies brand colors and typography to artifacts) and when to use it via an explicit "Use it when ..." trigger clause.

3 / 3

Trigger Term Quality

The "Use it when" clause surfaces natural terms users would say — "brand colors", "style guidelines", "visual formatting", "company design standards" — giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The Anthropic-brand niche with distinct brand-styling triggers makes it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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
davepoon/buildwithclaude
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.