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 ./examples/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 has excellent trigger term coverage and distinctiveness due to its specific focus on Anthropic branding. The only minor weakness is that the 'what' portion could list more concrete actions beyond 'applies brand colors and typography' to reach top marks on specificity.
| 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 which artifact types, or detailing typography rules. | 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. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically scoped to Anthropic's brand identity, which is a clear niche unlikely to conflict with other skills. The mention of 'Anthropic's official brand colors' makes it unmistakably unique. | 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 as a brand reference card rather than an actionable skill. It effectively catalogs Anthropic's brand colors and typography but completely lacks executable code, concrete usage examples, or step-by-step workflows for actually applying these styles to artifacts. The information is also somewhat redundant, with font fallback details repeated across three different sections.
Suggestions
Add executable Python code examples showing how to apply brand colors and fonts to common artifact types (e.g., python-pptx for presentations, matplotlib for charts), since the skill mentions python-pptx's RGBColor class but never shows it in use.
Define a clear workflow: e.g., 1) Identify artifact type, 2) Apply color palette, 3) Apply typography, 4) Verify output—with concrete code at each step.
Consolidate the repeated font/fallback information into a single section instead of spreading it across Typography, Smart Font Application, and Font Management.
Remove the keywords line and descriptive filler ('To access Anthropic's official brand identity...') and replace with a concrete quick-start example showing brand styling applied to a real artifact.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | There is some redundancy—font fallback information is repeated across multiple sections (Typography, Smart Font Application, Font Management), and some descriptions like 'Smart Font Application' restate what's already in the Typography section. The keyword list is unnecessary filler. However, the color values and core information are presented reasonably efficiently. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete commands, and no examples of how to actually apply these brand styles. It describes what the styling does ('Applies Poppins font to headings') but never shows how to do it—no Python code, no function calls, no usage examples. It's a reference sheet, not an actionable skill. | 1 / 3 |
Workflow Clarity | There is no workflow, no sequenced steps, and no process for applying brand styling to an artifact. The content is purely descriptive—it lists colors and fonts but never explains the steps Claude should take to apply them to a presentation, document, or other artifact. | 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 (no bundle files exist), and the repeated font/fallback information across sections suggests the content could be better consolidated. For a skill with no bundle, the structure is adequate but not optimal. | 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
- douglasvought/wiggle-skills
- Commit
b27906e
- 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.