brand-guidelines-community

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

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/brand-guidelines-community/SKILL.md

Quality

Content

53%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body provides genuinely useful brand specifics (hex palette, font assignments, accent rules) in a well-organized single file, but suffers from notable cross-section redundancy and lacks any executable code or concrete workflow despite naming python-pptx. It reads more as a feature catalog than actionable guidance.

Suggestions

Collapse the overlapping Features, Text Styling, and Font Management sections into one consolidated 'How colors and fonts are applied' section to remove repetition.

Add a short executable example using python-pptx RGBColor (e.g. setting a shape's fill to #d97757) since the skill already names that library.

Replace the generic 'When to Use' boilerplate with concrete triggers (branding, visual formatting, company design standards) that match the skill's purpose.

Dimension	Reasoning	Score
Conciseness	The core data (hex colors, font names) is useful, but the Overview repeats the description verbatim and the Features, Text Styling, and Font Management sections restate the same font-application/fallback points multiple times, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the 2-anchor's heavier padding.	3 / 5
Actionability	It gives concrete values (specific hex codes, Poppins/Lora with 24pt threshold, accent cycling rules) but no executable code or commands despite referencing python-pptx's RGBColor class, fitting 'some concrete guidance but incomplete; missing key details' for an instruction-only skill.	3 / 5
Workflow Clarity	There is no sequenced workflow or validation checkpoints; the body is organized as feature descriptions plus generic 'When to Use'/'Limitations' boilerplate, so the single styling action is only partly unambiguous, fitting the 3-anchor's missing-checkpoints description rather than the simple-skill 5-bar.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and no nested or buried references, and the content is small enough to inline with no external files needed; it falls short of 5 only because the redundant Features/Technical-Details sections are an organization gap.	4 / 5
	Total	13 / 20 Passed

Description

48%Weight 40%Scale 1-5

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 identifies a clear niche (Anthropic brand styling) but is thin: it states only a generic 'access' action and lacks the concrete capability list and rich trigger terms seen in the reference good example for this exact skill type. It answers what and when only weakly.

Suggestions

Lead with concrete actions, e.g. 'Applies Anthropic's official brand colors and typography (Poppins/Lora) to artifacts' instead of the generic 'access... resources'.

Add an explicit 'Use when...' clause with natural trigger terms like 'branding, visual formatting, brand colors, company design standards'.

Include synonyms and concrete nouns users would actually say (branding, visual identity, colors, typography) to lift trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Anthropic's official brand identity and style resources') but the only action verb is the generic 'access', with no concrete capabilities like applying colors or typography listed, matching the 'names domain but actions minimal/generic' anchor rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It states a what ('access brand identity and style resources') and a weak when ('To access... use this skill'), but the what is vague and lacks concrete actions, fitting 'clear-ish what but when weakly implied' more than the 4-anchor which expects concrete actions in the what.	3 / 5
Trigger Term Quality	It includes relevant natural terms ('brand identity', 'style resources') but misses common variations and synonyms (branding, visual formatting, colors, typography) that appear only in the body, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The Anthropic-brand niche is specific and largely distinct from other skills, with only minor overlap risk against general styling skills; it falls short of 5 because the trigger 'access style resources' is less concrete than the anchor's distinct trigger phrasing.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/brand-guidelines-community/SKILL.md
Commit: 1f67c44

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