brand-guidelines-community
To access Anthropic's official brand identity and style resources, use this skill.
38
23%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/brand-guidelines-community/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is too vague about what the skill actually does — it mentions 'accessing' brand resources but doesn't specify concrete actions like applying brand colors, typography, or formatting. It uses second-person voice ('use this skill') which is penalized, and lacks an explicit 'Use when...' clause with natural trigger terms. The Anthropic brand focus provides some distinctiveness but the description needs significantly more detail.
Suggestions
Replace vague 'access brand identity and style resources' with specific actions like 'Applies Anthropic's official brand colors, typography, and logo guidelines to artifacts and documents'.
Add an explicit 'Use when...' clause with trigger terms like 'brand colors', 'Anthropic style', 'visual formatting', 'company design standards', 'brand guidelines'.
Rewrite in third person voice (e.g., 'Applies Anthropic brand styling...') instead of second person ('use this skill').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'access Anthropic's official brand identity and style resources' but does not list any concrete actions like applying colors, typography, formatting artifacts, etc. It's vague about what the skill actually does. | 1 / 3 |
Completeness | The 'when' is partially addressed with 'To access Anthropic's official brand identity and style resources', but there is no explicit 'Use when...' clause with trigger scenarios. The 'what' is weak — it only says 'access resources' without specifying what actions are performed. | 2 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'brand identity', 'style resources', and 'Anthropic', which users might naturally mention. However, it misses common variations like 'brand colors', 'typography', 'design standards', 'logo', or 'visual formatting'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Anthropic's official brand identity' provides some distinctiveness, but 'style resources' is vague enough to potentially overlap with general styling or design skills. It lacks the specificity to clearly carve out a unique niche. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
7%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 document rather than an actionable skill. It lists colors, fonts, and general descriptions of styling behavior but provides zero executable code or concrete steps for Claude to follow when applying brand styling. The content is also highly redundant, with font and color information repeated across multiple sections.
Suggestions
Add executable python-pptx code examples showing how to apply brand colors and fonts to slides (e.g., setting fill colors, applying font families to text runs).
Define a clear workflow: e.g., 1) Open presentation, 2) Apply brand colors to backgrounds, 3) Apply typography to text elements, 4) Validate output visually or programmatically.
Consolidate the repeated font/color information into a single reference section and remove redundant descriptions (Smart Font Application, Text Styling, and Font Management all say the same things).
Remove generic boilerplate sections ('When to Use', 'Limitations') and replace with specific constraints relevant to brand styling (e.g., 'Do not modify chart data colors' or 'Preserve existing image positioning').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity and redundancy throughout. The typography section repeats the same font information three times (Typography, Smart Font Application, Text Styling). Font Management section restates fallback behavior already covered. The 'When to Use' and 'Limitations' sections are generic boilerplate that add no value. Much of this content explains things Claude already knows (what RGB colors are, how fallbacks work). | 1 / 3 |
Actionability | No executable code, no concrete commands, no examples of how to actually apply these brand styles. It describes colors and fonts but never shows how to use them (e.g., no python-pptx code snippet for applying brand colors to a slide). It mentions 'python-pptx's RGBColor class' but provides no actual code. This is a reference sheet, not actionable guidance. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all. No steps for applying brand styling to a document or presentation. No sequence of operations, no validation checkpoints. The skill describes what the brand looks like but never explains how to apply it programmatically. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headings, which provides some structure. However, there are no references to external files or bundle resources, and the content is somewhat monolithic with repeated information across sections. For a skill with no bundle files, the organization is adequate but not optimal. | 2 / 3 |
Total | 5 / 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
- sickn33/antigravity-awesome-skills
- Commit
9d0b37c
- 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.