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 ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/brand-guidelines-community/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 clearly communicates its purpose and includes explicit trigger guidance. Its main weakness is that the capability description could be more specific about concrete actions (e.g., applying specific hex colors, styling HTML/CSS artifacts, formatting presentations). It is notably one of the reference 'good examples' in the rubric, and rightfully so.
| 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, or detailing 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. | 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 like a brand guidelines reference document rather than an actionable skill for Claude. It lists colors, fonts, and feature descriptions but provides zero executable code, no usage examples, and no workflow for actually applying the branding to artifacts. The most useful part—the hex color values and font names—is buried among redundant descriptions of font fallback behavior repeated three times.
Suggestions
Add concrete, executable code examples showing how to apply brand colors and fonts to a PowerPoint slide (or other artifact type) using python-pptx, including at least one complete copy-paste-ready snippet.
Define a clear workflow: e.g., 1) Load artifact, 2) Apply heading fonts, 3) Apply body fonts, 4) Apply accent colors to shapes, 5) Verify output—with validation steps.
Remove redundant font fallback descriptions that appear in three separate sections and consolidate into a single concise note.
Add a concrete before/after example or at minimum show a function call pattern that Claude can directly use when applying the brand styling.
| 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 color selection based on background' are vague filler. The color palette section is efficient, but overall the content could be tightened significantly. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete commands, and no examples of how to actually apply the brand styling. It describes what the styling does ('Applies Poppins font to headings') but never shows how to do it—no Python snippets, no function calls, no usage patterns. It reads more like a feature description than 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 declarative—listing colors and font names—without any guidance on the order of operations or validation of results. | 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, and content that could be split (e.g., detailed technical implementation) is mixed with the overview. For a skill with no bundle, the structure is adequate but the lack of any referenced resources or examples limits it. | 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
- duclm1x1/Dive-Ai
- Commit
20ba150
- 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.