brand-guidelines-community

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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

The body is well-structured and supplies real brand reference values, but it is held back by redundant Features/Technical Details sections, generic When-to-Use/Limitations boilerplate, and a complete absence of executable code or a concrete application procedure. Consolidating the duplication and adding a worked python-pptx example would raise actionability and conciseness.

Suggestions

Merge the redundant "Features" and "Technical Details" sections so each font/color rule appears once.

Add an executable python-pptx code snippet demonstrating how to apply a brand hex color and the Poppins/Lora fonts to a slide.

Replace the generic "When to Use" and "Limitations" boilerplate with skill-specific guidance (e.g., which artifact types are supported, fallback behavior when fonts are absent).

Dimension	Reasoning	Score
Conciseness	The body carries genuinely useful reference data (hex codes, font names, the 24pt threshold), but the "Features" and "Technical Details" sections redundantly restate the same font/color rules, and the generic "When to Use" / "Limitations" boilerplate adds no skill-specific value. Not a 3 due to redundancy and filler; not a 1 because the brand reference values earn their place.	2 / 3
Actionability	Concrete values are present (hex codes, Poppins/Lora fonts, the python-pptx RGBColor mention), but there is no executable code example showing how to apply them — the skill describes rather than instructs. Not a 1 because the reference data is concrete; not a 3 because nothing is copy-paste ready and key implementation details are missing.	2 / 3
Workflow Clarity	As a simple reference skill it has no multi-step sequence, but the single action (apply brand styling to an artifact) is not made unambiguous: there is no procedure, no worked example, and no validation checkpoint. Under the simple-skills note it would need an unambiguous single action to reach 3, so it sits at 2.	2 / 3
Progressive Disclosure	The content is under 50 lines, requires no external references (none of references/scripts/assets exist), and is organized into clear headed sections (Overview, Brand Guidelines, Features, Technical Details, When to Use, Limitations). Per the simple-skills scoring note, well-organized sections with no need for external files score 3.	3 / 3
	Total	9 / 12 Passed

Description

50%

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 domain but relies on a single vague verb ("access") and lacks an explicit "Use when..." trigger clause, capping completeness. Trigger-term coverage is present but narrow. Adding concrete actions and explicit use-conditions would lift it across all dimensions.

Suggestions

Replace the vague verb "access" with concrete actions, e.g. "Applies Anthropic's official brand colors and typography to artifacts".

Add an explicit "Use when..." clause naming user-facing scenarios (brand styling, visual formatting, company design standards).

Broaden trigger terms to include common phrasings like "branding", "brand colors", "typography", and "visual formatting".

Dimension	Reasoning	Score
Specificity	The description names the domain ("Anthropic's official brand identity and style resources") but offers only the single vague action "access", with no concrete operations like applying colors or typography. It is above a 1 because a clear domain is named, but below a 3 because it lists no multiple specific concrete actions.	2 / 3
Completeness	It states what the skill is for ("access Anthropic's official brand identity and style resources"), but there is no explicit "Use when..." trigger clause; the "To access X, use this skill" form only implies the when. Per the judging guideline, a missing explicit trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Phrases like "brand identity", "style resources", and "Anthropic's official" are natural terms, but coverage is thin and misses common variations a user would say ("branding", "brand colors", "typography", "visual formatting"). Not a 3 because the keyword set is narrow; not a 1 because the terms present are natural rather than jargon.	2 / 3
Distinctiveness Conflict Risk	"Anthropic's official brand identity and style resources" carves out a recognizable niche, but the vague "access" action and limited triggers mean it could still overlap with general styling or design skills. Not a 3 because the triggers are not distinctly differentiated; not a 1 because the Anthropic-brand scoping is reasonably specific.	2 / 3
	Total	8 / 12 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
Commit: 615669b

Reviewed: 2 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.