brand-guidelines-anthropic

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

Quality

40%

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-anthropic/SKILL.md

Quality

Content

32%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 content is well-sectioned and correctly captures the brand palette and font rules, but it is padded with redundant restatements and offers no executable code or concrete workflow. It reads as a descriptive catalog rather than actionable guidance.

Suggestions

Collapse the repeated font/fallback facts from Features and Technical Details into a single concise section to remove redundancy.

Add an executable python-pptx snippet (import, RGBColor usage, font assignment) so Claude can apply the styling directly.

Replace the feature catalog with a short numbered workflow for styling an artifact, including a validation/preview checkpoint before finalizing.

Dimension	Reasoning	Score
Conciseness	The same font-application facts (Poppins for headings, Lora for body, Arial/Georgia fallback) are restated across Overview, Features, and Technical Details, creating several padded, redundant sections.	2 / 5
Actionability	It mentions python-pptx's RGBColor class but provides no executable code, imports, or commands — the guidance describes capabilities rather than instructing how to perform them.	2 / 5
Workflow Clarity	There is no sequenced workflow for applying brand styling to an artifact and no validation checkpoints; the body is a feature catalog with generic When-to-Use/Limitations boilerplate instead of ordered steps.	2 / 5
Progressive Disclosure	The single ~75-line file is organized into clear sections (Colors, Typography, Features, Technical Details) with no nested references, and no external bundle files are needed, though minor boilerplate slightly reduces crispness.	4 / 5
	Total	10 / 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 its niche (Anthropic brand styling) but is light on concrete actions and explicit trigger phrases, relying on the generic "use this skill" framing. It is serviceable but not exemplary.

Suggestions

Replace the generic verb "access" with concrete actions such as "Applies Anthropic's brand colors and typography to artifacts."

Add explicit "Use when..." trigger phrases naming natural terms like brand colors, visual formatting, typography, or company design standards.

Mention the artifact types it styles (e.g. .pptx, documents, slides) to sharpen distinctiveness and conflict resistance.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Anthropic's official brand identity and style resources") but lists no concrete actions beyond the generic verb "access" — it never says apply colors, set typography, or style artifacts.	2 / 5
Completeness	It offers a recognizable "what" but the "when" is just the tautological "use this skill" with no concrete trigger phrases, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	It surfaces a few relevant terms (brand, style, resources) but omits the natural phrases users actually say like brand colors, visual formatting, typography, or company design standards, so keyword coverage is partial.	3 / 5
Distinctiveness Conflict Risk	Being scoped specifically to Anthropic's brand identity gives it a clear niche with low overlap risk, though "access brand resources" remains somewhat broad.	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-anthropic/SKILL.md
Commit: 1f67c44

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