brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

2.77x

Quality

66%

Does it follow best practices?

Impact

100%

2.77x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/brand-guidelines/SKILL.md

The canonical home for this skill is brand-guidelines in anthropics/skills

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 skill body is well-structured and concise but lacks actionable, executable guidance: it describes styling behavior in prose without providing any code examples or commands, despite naming python-pptx. Adding concrete snippets and a brief apply-and-verify sequence would substantially raise actionability and workflow clarity.

Suggestions

Add a copy-paste-ready python-pptx code snippet showing how to set brand colors (RGBColor) and apply Poppins/Lora fonts, so the skill is executable rather than descriptive.

Provide a short sequenced workflow (open artifact -> apply colors -> apply fonts -> save) with a verification step confirming the output matches the brand palette.

Deduplicate the font/color information that currently repeats across the Features and Technical Details sections to tighten the body further.

Dimension	Reasoning	Score
Conciseness	The body is efficiently organized into focused sections without explaining concepts Claude already knows, though font and color details are repeated across Features and Technical Details and could be trimmed.	4 / 5
Actionability	Despite being a code-oriented skill that references python-pptx's RGBColor, the body provides no executable code or commands — only high-level descriptions of what the styling does, leaving the specific steps to execute missing.	2 / 5
Workflow Clarity	As a simple styling skill the single action is broadly clear, but there is no concrete sequence of how to apply the styling and no verification step to confirm an artifact was styled correctly.	3 / 5
Progressive Disclosure	Content is well organized into clear sections (Colors, Typography, Features, Technical Details) with no nested references; no bundle files exist, so structure is assessed on the body alone, which is good but slightly above the under-50-line simple-skill threshold.	4 / 5
	Total	13 / 20 Passed

Description

78%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 is strong and is in fact a listed good example: it clearly states the capability and provides explicit 'Use when' triggers with natural keywords. Its main weakness is breadth ('any sort of artifact') and a lack of enumerated concrete actions, which caps specificity at 3.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ('Applies Anthropic's official brand colors and typography') but does not enumerate multiple specific actions, and 'any sort of artifact' keeps coverage broad rather than comprehensive.	3 / 5
Completeness	Explicitly answers both what it does ('Applies Anthropic's official brand colors and typography...') and when to use it ('Use it when brand colors or style guidelines... apply'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes several natural trigger phrases users would say ('brand colors or style guidelines, visual formatting, company design standards'), with only minor synonyms like 'branding' missing.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche (Anthropic brand styling) with distinct triggers, though 'any sort of artifact that may benefit from having Anthropic's look-and-feel' leaves minor overlap risk with general formatting skills.	4 / 5
	Total	16 / 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: davepoon/buildwithclaude
Path: plugins/all-skills/skills/brand-guidelines/SKILL.md
Commit: a9fa86d

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.