brand-guidelines-community
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 formatt...
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill brand-guidelines-community64
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/skillAgent success when using this skill
Validation 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 well-structured description with explicit 'Use when' guidance and good trigger terms. The main weakness is the somewhat vague capability description - it says what it applies but not the specific actions it can perform. The description appears truncated (ends with '...') which may indicate missing content.
Suggestions
Add specific concrete actions like 'set color palettes, configure typography, style headers and buttons' to improve specificity
Ensure the full description is captured - the truncation ('...') suggests content may be missing
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (brand colors and typography) and a general action (applies), but lacks specific concrete actions like 'set color palettes', 'configure fonts', or 'style headers'. The phrase 'any sort of artifact' is vague. | 2 / 3 |
Completeness | Clearly answers both what (applies Anthropic's brand colors and typography) and when (explicit 'Use it when...' clause with trigger conditions: brand colors, style guidelines, visual formatting, company design standards). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'brand colors', 'style guidelines', 'visual formatting'. These are terms users naturally use when requesting brand-consistent styling. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche - specifically Anthropic's brand identity. The combination of 'Anthropic', 'brand colors', and 'typography' creates a unique trigger profile unlikely to conflict with generic styling 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 more as a brand reference document than an actionable skill. While it clearly defines Anthropic's color palette and typography choices, it completely lacks executable guidance on how to actually apply these styles to artifacts. Claude would know what colors to use but not how to implement them in any specific format (PowerPoint, HTML, SVG, etc.).
Suggestions
Add executable code examples showing how to apply brand colors in common formats (e.g., python-pptx for PowerPoint, CSS for web artifacts, SVG styling)
Include a clear workflow: 1) Identify artifact type, 2) Apply appropriate styling method, 3) Validate brand compliance
Provide concrete before/after examples showing input artifacts and expected branded output
Remove the redundant 'When to Use' section and consolidate 'Features' with 'Technical Details' to reduce verbosity
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary sections like 'When to Use' which adds no value, and the 'Features' section describes behavior Claude could infer from the guidelines themselves. | 2 / 3 |
Actionability | The skill provides no executable code, commands, or concrete examples of how to apply these styles. It describes what should happen but never shows how to do it - no python-pptx code snippets, no CSS examples, no actual implementation guidance. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all. The skill describes brand assets but provides no steps for applying them to artifacts. No sequence, no validation, no process for actually styling documents. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers, but it's a single file with no references to additional resources. The structure is adequate but the 'Features' and 'Technical Details' sections overlap conceptually. | 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.