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.

Quality

56%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/brand-guidelines-community/SKILL.md

Quality

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 includes explicit trigger guidance. The main weakness is that the capabilities could be more specific about what concrete actions it performs (e.g., specific elements it can style). Overall, it follows the good example pattern from the rubric closely.

Dimension	Reasoning	Score
Specificity	Names the domain (brand colors and typography) and general action (applies to artifacts), but doesn't list specific concrete actions like 'style headers', 'format buttons', or 'apply color palettes to charts'.	2 / 3
Completeness	Clearly answers both what (applies Anthropic's brand colors and typography to artifacts) AND when (explicit 'Use it when...' clause with multiple trigger scenarios including brand colors, style guidelines, visual formatting, design standards).	3 / 3
Trigger Term Quality	Good coverage of natural terms users would say: 'brand colors', 'style guidelines', 'visual formatting', 'company design standards', 'Anthropic's look-and-feel' - these are phrases users would naturally use when requesting brand styling.	3 / 3
Distinctiveness Conflict Risk	Very specific niche - Anthropic's official brand styling. The combination of 'Anthropic's', 'brand colors', 'typography', and 'look-and-feel' creates a distinct trigger profile unlikely to conflict with general styling or other company brand 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 is essentially an empty shell - a table of contents with no substantive content. It fails to provide any actionable guidance, examples, or workflow for applying Anthropic brand styling. The user must navigate to sub-skills for any actual information, but there's no guidance on which sub-skill to use for what purpose.

Suggestions

Add a quick-start section with a concrete example showing how to apply brand colors/typography to a common artifact (e.g., HTML, SVG, or CSS snippet)

Include brief descriptions for each sub-skill link explaining what it covers and when to use it

Add a simple workflow showing the typical sequence: e.g., '1. Check colors.md for palette → 2. Apply typography from typography.md → 3. Verify with color-application.md'

Remove the Keywords section - it serves no purpose for Claude's understanding

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes unnecessary elements like emoji decorations and a 'Keywords' section that adds no value for Claude. The overview sentence is somewhat redundant.	2 / 3
Actionability	The skill provides no concrete guidance, code, examples, or specific instructions. It's purely a table of contents pointing to sub-skills without any actionable content in the main file itself.	1 / 3
Workflow Clarity	There is no workflow described - no sequence of steps, no guidance on when to use which sub-skill, and no indication of how these modules work together to achieve brand styling.	1 / 3
Progressive Disclosure	The skill does reference sub-skills appropriately (one level deep), but the main file provides zero overview content or quick-start guidance. It's essentially just a list of links with no context on what each contains or when to use them.	2 / 3
	Total	6 / 12 Passed

Validation

90%

Warnings & errors only

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: Dokhacgiakhoa/antigravity-ide
Commit: 332e58b

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.