brand-guidelines-anthropic

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-organized and self-contained with accurate brand specs, but it repeats the font rules across sections, leans on boilerplate 'When to Use'/'Limitations' text, and lacks any executable code or concrete procedure. It reads more as a feature description than actionable guidance.

Suggestions

Collapse the repeated font-application details (Typography, Smart Font Application, Text Styling, Font Management) into one authoritative section to remove redundancy.

Add at least one copy-paste code snippet (e.g. RGBColor(0xd9,0x77,0x57) and a python-pptx font assignment) so the styling is executable rather than merely described.

Replace the generic 'When to Use'/'Limitations' boilerplate with concise, skill-specific guidance, or remove it if the frontmatter description already covers triggering.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight bullet lists of hex values and font names, but the font-application rules are repeated across Typography, Smart Font Application, Text Styling, and Font Management, and the 'When to Use'/'Limitations' sections add boilerplate, matching anchor 2.	2 / 3
Actionability	It provides concrete specs (exact hex codes, font names, one mention of python-pptx's RGBColor) but no executable code, commands, or copy-paste examples of how to actually apply them, so the guidance describes rather than instructs — anchor 2.	2 / 3
Workflow Clarity	It inventories features rather than giving a sequenced procedure for applying the styling; the single task is identifiable but the actual steps remain implicit with no checkpoints, so it sits at anchor 2 rather than the simple-skill 3.	2 / 3
Progressive Disclosure	The skill is a single self-contained file with no (and no need for) external references, organized into clear headed sections, matching the rubric's allowance that well-organized single-file skills can score 3.	3 / 3
	Total	9 / 12 Passed

Description

47%

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, distinct niche but is thin on action specificity and trigger coverage, and relies on a weak second-person directive instead of an explicit 'Use when' clause. It is above the vague baseline but well short of the best examples.

Suggestions

Replace the second-person 'use this skill' with a third-person verb and concrete actions, e.g. 'Applies Anthropic's official brand colors and typography to artifacts...'

Add an explicit 'Use when the user mentions brand colors, visual formatting, typography, or company design standards' trigger clause.

Fold one or two high-value natural trigger terms (brand colors, visual formatting) into the description itself rather than only the keywords list.

Dimension	Reasoning	Score
Specificity	The description names the domain ('brand identity and style resources') and a single action ('access') but lists no multiple concrete actions, putting the base at anchor 2; the second-person directive 'use this skill' triggers the rubric's -1 voice penalty, dropping it to 1.	1 / 3
Completeness	It states the 'what' (access brand/style resources) but the 'when' is only weakly implied via the generic 'use this skill' rather than an explicit 'Use when...' clause, so per the rubric it is capped at 2.	2 / 3
Trigger Term Quality	It includes some natural terms users might say ('brand identity', 'style resources') but lacks common variations like 'brand colors', 'visual formatting', or 'design standards' that appear only in the body, matching anchor 2.	2 / 3
Distinctiveness Conflict Risk	The niche is specific ('Anthropic's official brand identity') and unlikely to overlap with unrelated skills, matching anchor 3's clear-niche description.	3 / 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: 9fc5f98

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