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.
52
56%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/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 when to use it. It benefits from explicit trigger guidance and a well-defined niche around Anthropic brand styling. The only minor weakness is that the capability description could be slightly more specific about what concrete actions it performs beyond applying colors and typography.
| 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 listing specific colors, specifying file types it can style, or detailing exact formatting operations. | 2 / 3 |
Completeness | Clearly answers both 'what' (applies Anthropic's official 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'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'brand colors', 'style guidelines', 'visual formatting', 'company design standards', 'Anthropic', 'look-and-feel', and 'typography'. These cover a good range of how users might phrase requests for brand styling. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically scoped to Anthropic's brand identity, which is a clear niche. The mention of 'Anthropic's official brand colors' makes it very unlikely to conflict with generic styling or other company brand 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 functions as a brand reference card listing Anthropic's colors and fonts, but it lacks actionable guidance on how to actually apply the styling to artifacts. Key information is repeated across multiple sections without adding value, and there are no executable code examples, CSS snippets, or step-by-step workflows. The skill would benefit significantly from concrete, copy-paste-ready implementation examples.
Suggestions
Add executable code examples showing how to apply brand colors and fonts — e.g., a CSS snippet for HTML artifacts, a python-pptx code block for presentations, or similar concrete implementations.
Consolidate the repeated font/typography information from 'Typography', 'Smart Font Application', 'Text Styling', and 'Font Management' into a single authoritative section.
Add a workflow section with clear steps: e.g., 1) Identify artifact type, 2) Apply color tokens using [specific method], 3) Apply typography, 4) Verify output matches brand guidelines.
Remove the vague overview sentence and keywords line — replace with a concise 'When to use' note that adds real decision-making value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | There is noticeable redundancy — font application details are repeated across 'Typography', 'Smart Font Application', 'Text Styling', and 'Font Management' sections. The 'Keywords' line and some explanatory text (e.g., 'To access Anthropic's official brand identity and style resources, use this skill') add little value. However, the core color/typography reference data is reasonably compact. | 2 / 3 |
Actionability | The skill describes brand tokens (hex colors, font names) but provides no executable code, CSS snippets, or concrete commands for applying them. There are no copy-paste-ready examples showing how to actually style an artifact — it reads more like a reference sheet than actionable instructions. | 1 / 3 |
Workflow Clarity | There is no workflow or sequenced process described. The skill never explains how to apply the brand styling to an artifact — no steps, no validation, no before/after. It only lists what the brand elements are, not how to use them. | 1 / 3 |
Progressive Disclosure | The content references an example file (examples/brand-test.html), which is good, but no bundle files are provided to support it. The sections are organized but the repeated information across Typography/Smart Font Application/Text Styling/Font Management suggests content that should be consolidated rather than split 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.
f3707dd
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.