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.
95
56%
Does it follow best practices?
Impact
99%
5.82xAverage score across 10 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./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 well-crafted description that excels at completeness and distinctiveness, with strong trigger terms that users would naturally use. The main weakness is in specificity - it describes the general capability but doesn't enumerate the concrete actions it can perform (e.g., specific styling operations or artifact types it handles).
Suggestions
Add specific concrete actions like 'style headers, apply color palettes to charts, format code blocks with brand typography' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (brand colors and typography) and general action (applies to artifacts), but doesn't list specific concrete actions like 'format headers', 'apply color palette to charts', or 'style text elements'. | 2 / 3 |
Completeness | Clearly answers both what ('Applies Anthropic's official brand colors and typography to artifacts') and when ('Use it when brand colors or style guidelines, visual formatting, or company design standards apply') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'brand colors', 'style guidelines', 'visual formatting', 'company design standards', 'Anthropic's look-and-feel'. These are terms users would naturally use when requesting brand styling. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Anthropic brand styling. The combination of 'Anthropic's official brand' with specific triggers like 'brand colors' and 'style guidelines' makes it unlikely to conflict with general formatting or other company-specific skills. | 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 provides a good reference for Anthropic's brand colors and typography but fails as an actionable skill. It describes brand elements without providing any executable code, commands, or step-by-step instructions for Claude to actually apply the styling. The content reads like a style guide rather than a skill that teaches Claude how to perform a task.
Suggestions
Add executable code examples showing how to apply brand colors and fonts (e.g., python-pptx code for PowerPoint, CSS for web artifacts, or other relevant implementations)
Include a clear workflow: 1) Identify artifact type, 2) Apply appropriate styling method, 3) Verify brand compliance
Consolidate redundant font information into a single section and remove the duplicate descriptions across Typography, Features, and Technical Details
Add concrete input/output examples showing before and after applying brand styling to different artifact types
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy (font information repeated in Typography, Smart Font Application, Text Styling, and Font Management sections). The 'Features' section partially duplicates the 'Brand Guidelines' section. | 2 / 3 |
Actionability | The skill describes what the styling does but provides no executable code, commands, or concrete examples of how to apply the brand styling. It reads more like documentation than actionable instructions Claude can follow. | 1 / 3 |
Workflow Clarity | There is no workflow or sequence of steps provided. The skill doesn't explain how to actually apply the brand styling - it only describes the brand elements and what the styling does conceptually. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headings, but it's somewhat monolithic with no references to external files for detailed implementation. The structure is reasonable but content that could be condensed is spread across multiple similar sections. | 2 / 3 |
Total | 6 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
2790447
Table of Contents
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.