CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-guidelines-anthropic

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

24

Quality

14%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills-claude/skills/brand-guidelines-anthropic/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

7%Scale 1-3

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

This skill is essentially a brand style guide reference card with no actionable implementation guidance. It lists colors, fonts, and general behaviors but provides zero executable code or concrete steps for applying these styles. The content is also highly redundant, with font fallback information and text styling details repeated across multiple sections.

Suggestions

Add executable python-pptx code examples showing how to apply brand colors and fonts to slides (e.g., setting a shape's fill color, applying Poppins to a heading run).

Define a clear workflow: 1) Open/create presentation, 2) Apply brand colors to backgrounds, 3) Apply typography to text elements, 4) Validate output visually or programmatically.

Consolidate redundant sections—merge 'Smart Font Application', 'Text Styling', and 'Font Management' into a single concise section with a code example.

Remove generic boilerplate ('When to Use' and 'Limitations' sections) and replace with specific constraints relevant to brand styling (e.g., 'Do not modify logos or trademarked assets').

DimensionReasoningScore

Conciseness

Significant verbosity and redundancy throughout. The font management section repeats fallback information three times across different sections. The 'Smart Font Application' and 'Text Styling' sections are nearly identical. The 'When to Use' and 'Limitations' sections are generic boilerplate that add no value. Claude already knows what RGB colors are and how python-pptx works.

1 / 3

Actionability

No executable code, no concrete commands, no examples of how to actually apply these brand styles. The skill describes brand values (colors, fonts) but never shows how to use them—no python-pptx code snippets, no function calls, no workflow for applying styles to a presentation. It reads as a reference document rather than actionable instructions.

1 / 3

Workflow Clarity

There is no workflow defined at all. No sequenced steps for applying brand styling to a document or presentation. No validation checkpoints to verify colors or fonts were applied correctly. The skill simply lists properties without explaining how to use them in any process.

1 / 3

Progressive Disclosure

The content is organized into logical sections with clear headings, which provides some structure. However, there are no references to external files or bundle resources, and content that is redundant across sections could be consolidated. The organization exists but doesn't serve progressive disclosure since there's no layering of complexity.

2 / 3

Total

5

/

12

Passed

Description

22%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague and lacks concrete actions, explicit trigger guidance, and natural user keywords. It uses second-person voice ('use this skill') which is discouraged, and fails to enumerate what the skill actually does beyond 'access resources'. It would benefit significantly from listing specific capabilities and adding a clear 'Use when...' clause.

Suggestions

Add specific concrete actions like 'Applies Anthropic's official brand colors, typography, and logo guidelines to artifacts' instead of the vague 'access resources'.

Add an explicit 'Use when...' clause with trigger terms such as 'brand colors', 'Anthropic branding', 'logo usage', 'typography', 'design standards', 'visual formatting'.

Rewrite in third person voice (e.g., 'Provides Anthropic brand colors and typography...') instead of the current second-person imperative 'use this skill'.

DimensionReasoningScore

Specificity

The description says 'access Anthropic's official brand identity and style resources' which is vague — it doesn't list any concrete actions like applying colors, typography, generating branded assets, etc.

1 / 3

Completeness

The 'what' is weak (just 'access resources') and the 'when' is essentially absent — 'To access...' is a purpose statement, not an explicit trigger clause like 'Use when...'. The description fails to clearly answer both questions.

1 / 3

Trigger Term Quality

Contains some relevant keywords like 'brand identity', 'style resources', and 'Anthropic' that users might mention, but misses common variations like 'brand colors', 'logo', 'typography', 'design guidelines', 'brand standards'.

2 / 3

Distinctiveness Conflict Risk

The mention of 'Anthropic's official brand identity' provides some specificity that narrows the niche, but 'style resources' is broad enough to potentially overlap with general design or styling skills.

2 / 3

Total

6

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-skills
Reviewed

Table of Contents

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.