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.
64
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 when to use the skill with explicit trigger terms and a well-defined scope. The main weakness is that the capabilities could be more specific - listing concrete actions like applying specific color codes, font families, or styling particular artifact types would strengthen it further.
Suggestions
Add more specific concrete actions such as 'apply color palettes, set typography, configure visual hierarchy' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (brand colors and typography) and a general action (applies), but doesn't list multiple specific concrete actions like 'set color palettes, apply font families, configure spacing guidelines'. | 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 | Includes natural keywords users would say: 'brand colors', 'style guidelines', 'visual formatting', 'company design standards', 'Anthropic's look-and-feel'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche - Anthropic brand styling specifically. The combination of 'Anthropic', 'brand colors', 'typography', and 'look-and-feel' creates a distinct trigger profile 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 guide but fails as an actionable skill. It provides useful color codes and typography specifications but lacks any executable code, concrete examples, or step-by-step instructions for actually applying the branding. Claude would know what colors to use but not how to implement them.
Suggestions
Add executable Python code examples showing how to apply brand colors using python-pptx (e.g., `shape.fill.solid(); shape.fill.fore_color.rgb = RGBColor(217, 119, 87)`)
Include a concrete workflow: 1. Load presentation, 2. Apply styles, 3. Verify output - with actual code for each step
Remove the redundant 'Features' section that restates the Brand Guidelines, or consolidate into a single reference
Add a complete example showing before/after application of branding to a sample element
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy (font fallback information repeated in multiple sections) and the 'Features' section restates information already covered in 'Brand Guidelines'. The keywords list is unnecessary padding. | 2 / 3 |
Actionability | The skill describes what the styling does but provides no executable code, commands, or concrete examples of how to apply these styles. It mentions 'python-pptx's RGBColor class' but gives no actual implementation code. | 1 / 3 |
Workflow Clarity | There is no workflow or process described. The skill lists features and colors but never explains how to actually apply the branding - no steps, no sequence, no validation of results. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headings, but it's all inline with no references to external files for detailed implementation. The structure is reasonable for a reference document but lacks navigation to deeper resources. | 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 | |
- 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.