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.
95
56%
Does it follow best practices?
Impact
99%
6.18xAverage score across 10 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/anthropic-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 serves as a brand reference sheet but fails as an actionable skill — it tells Claude what the brand values are but never shows how to apply them. The repeated font fallback information across multiple sections wastes tokens, and the complete absence of executable code or step-by-step workflow means Claude would have to figure out the implementation entirely on its own. The color hex values and font choices are useful reference data, but the skill needs concrete implementation examples to be effective.
Suggestions
Add executable code examples showing how to apply brand colors and fonts (e.g., a python-pptx snippet setting slide background to #faf9f5 and heading font to Poppins)
Define a clear workflow: e.g., 1. Identify artifact type, 2. Apply background colors, 3. Style headings, 4. Style body text, 5. Apply accent colors to shapes, 6. Verify output
Remove redundant sections — consolidate font fallback info into one place and merge 'Features' content into the guidelines or a single implementation section
Remove the keywords line — it serves no purpose for Claude's understanding and wastes tokens
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | There's some redundancy — font fallback behavior is mentioned in at least three places (Typography, Smart Font Application, Font Management), and the 'Features' section largely restates what's already in 'Brand Guidelines'. The keywords line adds no value for Claude. However, the core color/typography reference data is reasonably compact. | 2 / 3 |
Actionability | The skill describes brand values (colors, fonts) but provides no executable code, no concrete commands, and no examples of how to actually apply these styles. There's no code snippet showing how to use python-pptx's RGBColor, how to set fonts on slides, or any copy-paste-ready implementation. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | There is no workflow, sequence of steps, or process described. The skill is purely declarative — it lists brand assets but never explains how to apply them to an artifact. There are no validation steps or any indication of what order operations should happen in. | 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 for deeper detail, and the redundant sections (Features restating Guidelines, Font Management restating Typography) suggest the content could be better structured. It's not a wall of text but isn't optimally organized either. | 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.
- Repository
- boisenoise/skills-collections
- Commit
431bfad
- 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.