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.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill brand-guidelines71
Quality
56%
Does it follow best practices?
Impact
100%
2.77xAverage score across 3 eval scenarios
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 well-crafted description that excels at completeness and distinctiveness by clearly stating both purpose and trigger conditions while carving out a specific niche for Anthropic brand styling. The main weakness is moderate specificity - it could benefit from listing more concrete actions beyond the general 'applies colors and typography'. Overall, this is a strong description that would perform well in skill selection.
| 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 phrases users would naturally use when requesting brand styling. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche - specifically Anthropic brand styling. The combination of 'Anthropic's official brand' with specific triggers like 'brand colors', '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 functions as a brand reference sheet rather than an actionable skill. While it clearly documents Anthropic's colors and typography, it completely lacks executable guidance on how to apply these styles to artifacts. The skill tells Claude what the brand looks like but not how to implement it.
Suggestions
Add executable code examples showing how to apply brand colors and fonts using python-pptx (e.g., setting slide background color, applying font to text frames)
Include a clear workflow: 1) Identify artifact type, 2) Apply appropriate styling, 3) Validate output appearance
Provide concrete before/after examples showing input artifacts and expected branded output
Consolidate redundant font information into a single section to improve conciseness
| 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 brand guidelines are but provides no concrete code, commands, or executable examples for how to actually apply these styles. It mentions python-pptx but doesn't show how to use it. | 1 / 3 |
Workflow Clarity | There is no workflow or process described. The skill lists brand assets but doesn't explain how to apply them to artifacts, what steps to follow, or how to validate the results. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headings, but there's no reference to external files for detailed implementation. The structure is reasonable for a reference document but could better separate quick-reference colors from implementation details. | 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 | |
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.