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.
71
56%
Does it follow best practices?
Impact
100%
2.77xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/brand-guidelines/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly communicates its purpose and includes an explicit 'Use when' clause with good trigger terms. Its main weakness is that the capability description could be more specific about the concrete actions performed beyond 'applies brand colors and typography'. The phrase 'any sort of artifact that may benefit' is somewhat vague but acceptable given the broad applicability of brand styling.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Anthropic brand styling) and some actions ('applies brand colors and typography'), but doesn't list multiple specific concrete actions like 'set heading fonts, apply color palette to charts, format buttons with brand styles'. The phrase 'any sort of artifact that may benefit' is vague. | 2 / 3 |
Completeness | Clearly answers both 'what' (applies Anthropic's brand colors and typography to artifacts) and 'when' (explicitly states 'Use it when brand colors or style guidelines, visual formatting, or company design standards apply'). The 'Use when' clause is explicit. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'brand colors', 'typography', 'Anthropic', 'look-and-feel', 'style guidelines', 'visual formatting', 'company design standards'. These cover a good range of terms a user would naturally use when requesting brand styling. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically scoped to Anthropic's brand identity, which is a clear niche. Unlikely to conflict with generic styling or design skills because it explicitly names 'Anthropic's official brand colors' and 'company design standards'. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like a brand guidelines reference document rather than an actionable skill for Claude. It effectively catalogs Anthropic's colors and typography choices but completely lacks executable code, concrete usage examples, or step-by-step workflows for actually applying the branding to artifacts (e.g., PowerPoint slides, HTML, SVGs). The repeated font fallback information across three sections wastes tokens without adding value.
Suggestions
Add executable code examples showing how to apply brand colors and fonts to at least one artifact type (e.g., a python-pptx snippet that sets slide colors and fonts, or CSS/HTML styling).
Define a clear workflow: e.g., 1) Identify artifact type, 2) Apply color palette, 3) Apply typography, 4) Verify output—with concrete code at each step.
Consolidate the repeated font fallback information into a single section instead of repeating it under Typography, Smart Font Application, and Font Management.
Add a concrete input/output example showing a before-and-after of applying brand styling to an artifact.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | There is some redundancy—font fallback information is repeated across multiple sections (Typography, Smart Font Application, Font Management), and some descriptions like 'Smart color selection based on background' are vague filler. The color palette section is efficient, but overall the content could be tightened significantly. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete commands, and no examples of how to actually apply the brand styling. It describes what the styling does ('Applies Poppins font to headings') but never shows how to do it—no Python snippets, no function calls, no usage patterns. It reads more like a feature description than an actionable skill. | 1 / 3 |
Workflow Clarity | There is no workflow, no sequenced steps, and no process for applying brand styling to an artifact. The content is purely descriptive with no indication of what Claude should do first, how to apply colors/fonts, or how to verify the result. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headings, which is good. However, there are no references to external files, no bundle files, and the repeated font/color information across sections suggests the content structure could be better consolidated. For a skill with no bundle, the organization is adequate but not optimal. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.