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 explicit trigger guidance. It is noted as a 'good example' in the rubric itself. The main weakness is that the specificity of concrete actions could be slightly more detailed — 'applies brand colors and typography' is somewhat general, and 'any sort of artifact that may benefit' is vague rather than listing specific artifact types.
| 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 header fonts to X, apply color palette Y, format buttons with Z'. The phrase 'any sort of artifact that may benefit' is vague. | 2 / 3 |
Completeness | Clearly answers both 'what' (applies Anthropic's official brand colors and typography to artifacts) and 'when' (explicit 'Use it when...' clause covering brand colors, style guidelines, visual formatting, or company design standards). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'brand colors', 'style guidelines', 'visual formatting', 'company design standards', 'Anthropic', 'look-and-feel', 'typography'. These are terms users 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. The combination of 'Anthropic', 'brand colors', and 'typography' makes it very unlikely to conflict with other 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 reads more like a brand style guide reference sheet than an actionable skill for Claude. It thoroughly documents Anthropic's colors and typography but completely lacks executable code, concrete steps, or examples showing how to apply these styles to artifacts. The significant redundancy across sections (font fallback info repeated 3 times, styling details restated in multiple places) wastes token budget without adding value.
Suggestions
Add executable Python code examples showing how to apply brand colors and fonts to common artifact types (e.g., python-pptx for slides, HTML/CSS for web artifacts)
Define a clear workflow: 1) Identify artifact type, 2) Apply styles using specific code, 3) Verify output — with concrete commands at each step
Consolidate the repeated font/fallback information into a single section to eliminate redundancy and improve token efficiency
Remove the 'Features' section which merely restates the brand guidelines in a different format, or replace it with actual usage examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | There's noticeable redundancy — font application details are repeated across 'Typography', 'Smart Font Application', 'Text Styling', and 'Technical Details > Font Management'. The fallback information appears three times. The 'Features' section largely restates what's already in 'Brand Guidelines'. | 2 / 3 |
Actionability | No executable code, no concrete commands, and no examples of how to actually apply these styles. It describes what the skill does but never shows how — no Python snippets, no function calls, no copy-paste ready guidance for applying brand colors to artifacts. | 1 / 3 |
Workflow Clarity | There is no workflow or sequence of steps described. The content is purely declarative/descriptive — it lists colors and fonts but never explains the process for applying them to an artifact. No validation or verification steps are mentioned. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, which provides some structure. However, it's somewhat monolithic with repeated information across sections, and there are no references to external files for deeper details or examples. | 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
7cc63f3
- 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.