brand-guidelines-anthropic

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

Quality

47%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/brand-guidelines-anthropic/SKILL.md

Quality

Content

46%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 a well-sectioned, self-contained reference sheet of Anthropic brand colors and typography, but it stops at description: it gives no executable code or concrete application workflow, repeats the font-fallback information multiple times, and offers only a circular 'When to Use' note.

Suggestions

Add a copy-paste-ready code example showing how to apply the palette via python-pptx RGBColor (and/or CSS), since the body currently only names the class without demonstrating it.

Deduplicate the font-fallback information so it appears once, and collapse the redundant Features/Technical Details sections into the Brand Guidelines.

Replace the circular 'When to Use' line with a concrete trigger listing the artifact types and scenarios where this styling applies.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference data (hex colors, font names), but the font-fallback point is repeated across Typography, Smart Font Application, and Technical Details, and the Features section largely restates the Brand Guidelines, so it could be tightened.	3 / 5
Actionability	It provides concrete reference values (color hex codes, font names) and names python-pptx's RGBColor class, but gives no executable code, commands, or concrete steps for actually applying the styling to an artifact.	2 / 5
Workflow Clarity	The single intended action (apply brand colors/fonts) is reasonably clear from the reference data, but there is no sequenced workflow or validation checkpoint, and the 'When to Use' section is circular ('applicable to execute the workflow or actions described in the overview').	3 / 5
Progressive Disclosure	The skill is self-contained with clearly labeled sections and no nested external references (and no bundle files exist to link to), though the overlap between Features, Technical Details, and Brand Guidelines shows minor organization gaps.	4 / 5
	Total	12 / 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, distinct niche (Anthropic brand styling) but relies on a single generic verb ('access') and a weak, circular trigger rather than concrete actions and an explicit 'Use when...' clause. Second-person phrasing also reduces its specificity.

Suggestions

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

Add an explicit trigger clause: 'Use when the user wants Anthropic brand styling, brand colors, typography, or company visual design standards.'

Rewrite in third person and fold natural trigger terms (brand colors, typography, visual formatting) into the description itself rather than relying on a separate keywords line.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Anthropic's official brand identity and style resources') but only offers the generic action 'access', and the second-person 'use this skill' phrasing further weakens it rather than listing concrete capabilities.	2 / 5
Completeness	The 'what' is reasonably clear (access brand identity and style resources), but the 'when' is only weakly implied via the circular 'To access X, use this skill' rather than an explicit 'Use when...' trigger clause, which caps completeness at 3.	3 / 5
Trigger Term Quality	It includes relevant natural terms like 'brand identity' and 'style resources', but misses common variations users might say (e.g. 'brand colors', 'typography', 'company design standards') that appear only in the body keywords, not the description.	3 / 5
Distinctiveness Conflict Risk	The Anthropic-specific branding niche is fairly distinct with limited overlap risk, though it could still collide with generic styling or design-standard skills.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/brand-guidelines-anthropic/SKILL.md
Commit: 57c135b

Reviewed: 1 day 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.