brand-guidelines-community

To access Anthropic's official brand identity and style resources, use this skill.

Quality

23%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

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 only mentions 'accessing' resources without specifying concrete actions like applying brand colors, typography, or generating branded artifacts. It also uses second-person voice ('use this skill') which violates the third-person guideline, and lacks explicit trigger terms users would naturally use when needing brand-related help.

Suggestions

Replace the vague 'access brand identity and style resources' with specific actions like 'Applies Anthropic's official brand colors, typography, and logo guidelines to artifacts'.

Add an explicit 'Use when...' clause with natural trigger terms such as 'brand colors', 'Anthropic style', 'logo usage', 'typography', 'design standards', 'brand guidelines'.

Rewrite in third person voice (e.g., 'Provides Anthropic brand colors and typography...') instead of the current second-person imperative ('use this skill').

Dimension	Reasoning	Score
Specificity	The description says 'access Anthropic's official brand identity and style resources' which is vague — it doesn't list any concrete actions like applying colors, typography, generating branded assets, etc.	1 / 3
Completeness	The 'when' is partially addressed with 'To access Anthropic's official brand identity and style resources, use this skill', but the 'what' is extremely weak — it only says 'access resources' without specifying what actions the skill performs. The trigger guidance is implicit rather than explicit with a 'Use when...' clause.	2 / 3
Trigger Term Quality	Contains some relevant keywords like 'brand identity', 'style resources', and 'Anthropic', but misses common variations users might say such as 'brand colors', 'logo', 'typography', 'design guidelines', 'brand standards', or 'look-and-feel'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Anthropic's official brand identity' provides some distinctiveness, but 'style resources' is broad enough to potentially overlap with general design or styling skills.	2 / 3
	Total	7 / 12 Passed

Implementation

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 thoroughly lists brand colors, fonts, and features but completely lacks executable code, concrete steps, or a workflow for actually applying these styles. The content is also highly repetitive, with font and fallback information stated multiple times across sections.

Suggestions

Add executable python-pptx code examples showing how to apply brand colors and fonts to a presentation (e.g., setting heading font to Poppins, applying accent colors to shapes).

Define a clear workflow: 1) Open/create PPTX, 2) Apply brand styles with specific code, 3) Validate output, 4) Save — with explicit validation checkpoints.

Consolidate the repeated font/fallback information into a single concise reference table instead of restating it across Typography, Smart Font Application, Text Styling, and Font Management sections.

Remove generic boilerplate sections ('When to Use', 'Limitations') and replace with specific constraints relevant to this skill (e.g., supported file formats, known python-pptx limitations).

Dimension	Reasoning	Score
Conciseness	Significant verbosity and redundancy throughout. The Typography section repeats the same font information three times (in Typography, Smart Font Application, and Text Styling sections). Font Management repeats fallback information twice. The 'When to Use' and 'Limitations' sections are generic boilerplate that add no value. Much of this content describes concepts 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 what the styling does ('Applies Poppins font to headings') but never shows how to do it. Mentions python-pptx's RGBColor class but provides no code snippet. This is a reference document, not an actionable skill.	1 / 3
Workflow Clarity	There is no workflow, sequence of steps, or process described at all. The skill describes brand properties and features but never explains how to apply them. For a styling/post-processing skill, there should be clear steps: open file, apply styles, validate output, save. None of this exists.	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, no bundle files to support the skill, and content that could be split (e.g., detailed color/font specs into a reference file) is all inline. The organization is reasonable but not optimal.	2 / 3
	Total	5 / 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: sickn33/antigravity-awesome-skills
Commit: fb2efea

Reviewed: about 14 hours 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.