CtrlK
BlogDocsLog inGet started
Tessl Logo

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

6.18x
Quality

48%

Does it follow best practices?

Impact

99%

6.18x

Average score across 10 eval scenarios

SecuritybySnyk

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.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 sheet rather than an actionable skill. It lists color values and font names but provides zero executable code or concrete steps for applying them to any artifact type. There is significant redundancy across sections (font/fallback info repeated three times), and it explains concepts Claude already understands while omitting the actual implementation guidance that would make this useful.

Suggestions

Add concrete, executable code examples showing how to apply brand colors and fonts (e.g., python-pptx snippet for PowerPoint, CSS for HTML, SVG styling) — this is the core gap.

Define a clear workflow: 1) Identify artifact type, 2) Apply colors/fonts using specific code, 3) Validate output — currently there are no steps at all.

Eliminate redundant sections: 'Smart Font Application', 'Text Styling', and 'Font Management' all repeat the same Poppins/Lora/fallback information. Consolidate into one concise reference.

Remove the Keywords line and explanatory text like 'uses RGB color values for precise brand matching' — Claude knows what RGB values are. Focus tokens on actionable implementation details.

DimensionReasoningScore

Conciseness

Significant verbosity and redundancy. The 'Smart Font Application' and 'Text Styling' sections repeat the same information (Poppins for headings, Lora for body). 'Font Management' repeats fallback info stated earlier. Keywords section is unnecessary. Much of this describes concepts Claude already knows (what fallback fonts are, what RGB values do).

1 / 3

Actionability

No executable code, no concrete commands, no copy-paste ready examples. The skill describes brand values (hex colors, font names) but never shows how to actually apply them—no python-pptx code snippets, no CSS examples, no concrete implementation. It describes rather than instructs.

1 / 3

Workflow Clarity

No workflow or sequence of steps is provided. There's no process for how to apply branding to an artifact—no steps like 'load the file, apply colors, apply fonts, validate output.' It's purely a reference document with no procedural guidance.

1 / 3

Progressive Disclosure

The content has some section structure (Colors, Typography, Features, Technical Details), but there are no references to external files and no bundle files exist. Content that is redundant across sections could be better organized. For a skill with no bundle, the organization is passable but not well-optimized.

2 / 3

Total

5

/

12

Passed

Description

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 includes explicit trigger guidance. It is noted as one of the rubric's own 'good examples,' and for good reason — it has clear scope, natural trigger terms, and a distinct niche. The only minor weakness is that the capability description could be slightly more specific about the concrete actions performed beyond 'applies brand colors and typography.'

DimensionReasoningScore

Specificity

Names the domain (Anthropic brand styling) and some actions ('applies brand colors and typography'), but doesn't list multiple specific concrete actions like applying to specific artifact types, generating style sheets, or converting existing designs.

2 / 3

Completeness

Clearly answers both 'what' (applies Anthropic's official brand colors and typography to artifacts) and 'when' (explicit 'Use it when...' clause covering brand colors, style guidelines, visual formatting, or company design standards).

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'. Good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — specifically scoped to Anthropic's brand identity, which is a clear niche. Unlikely to conflict with generic styling or design skills due to the company-specific focus.

3 / 3

Total

11

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
duclm1x1/Dive-Ai
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.